joy/android_packages_modules_Connectivity
Watch
1
Fork
You've already forked android_packages_modules_Connectivity
 0
Code Issues Pull requests Projects Releases Wiki Activity

BpfMap.h: disable two ALOGE-s

Browse source 
They really don't add much to the picture.
The information is already in the exception.

Test: TreeHugger
Flag: EXEMPT mainline, logging
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I91b54814af20e02df11b8d035fa0ee1740cf644a
This commit is contained in:
Maciej Żenczykowski 2025-08-28 11:58:43 -07:00
commit 0c239209a7
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
bpf/headers/include/bpf/BpfMap.h
View file

@ -37,6 +37,8 @@ using base::unique_fd;
using std::function;
#ifdef BPF_MAP_MAKE_VISIBLE_FOR_TESTING
#undef BPFMAP_VERBOSE
#define BPFMAP_VERBOSE
#undef BPFMAP_VERBOSE_ABORT
#define BPFMAP_VERBOSE_ABORT
#endif
@ -383,9 +385,11 @@ class BpfMap : public BpfMapRW<Key, Value> {
// We already have the data, not clear what to do on delete failure...
// Let's just log something...
// (but ignore ENOENT in case we're racing against someone else)
#ifdef BPFMAP_VERBOSE
if (res.error().code() != ENOENT)
ALOGE("BpfMap::readAndDeleteValue(): read but failed to delete data %s",
strerror(res.error().code()));
#endif
return v;
}
@ -400,7 +404,9 @@ class BpfMap : public BpfMapRW<Key, Value> {
if (!res.ok()) {
// Someone else could have deleted the key, so ignore ENOENT
if (res.error().code() == ENOENT) continue;
#ifdef BPFMAP_VERBOSE
ALOGE("Failed to delete data %s", strerror(res.error().code()));
#endif
return res.error();
}
}