From: Luo Gengkun <luogengkun2@huawei.com>
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>, <ast@kernel.org>,
<daniel@iogearbox.net>, <andrii@kernel.org>, <eddyz87@gmail.com>,
<memxor@gmail.com>
Cc: <martin.lau@linux.dev>, <song@kernel.org>,
<yonghong.song@linux.dev>, <jolsa@kernel.org>,
<bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bpf: defer freeing htab internal structs to workqueue to fix sleep-in-atomic
Date: Mon, 8 Jun 2026 09:25:52 +0800 [thread overview]
Message-ID: <f99d0d59-d12b-417d-b02a-2ae73077056d@huawei.com> (raw)
In-Reply-To: <ba77f59c-f932-4792-9d57-69ebe8806857@gmail.com>
On 2026/6/8 3:03, Mykyta Yatsenko wrote:
>
>
> On 6/6/26 3:28 AM, Luo Gengkun wrote:
>> This fix resolves a conflict between two patches:
>> 1. commit 1da6c4d9140c ("bpf: fix use after free in bpf_evict_inode")
>> 2. commit 4f375ade6aa9 ("bpf: Avoid RCU context warning when unpinning
>> htab with internal structs")
>>
>> The problem is that commit 4f375ade6aa9 breaks commit 1da6c4d9140c 's UAF
>> fix, because we need the RCU grace period to keep symlink lookups safe. But
>> keeping the RCU delay means `htab_map_free_internal_structs` runs inside
>> RCU_SOFTIRQ, where calling `cond_resched()` and triggers the "sleeping
>> function called from invalid context" BUG.
>>
>> To solve both issues, we keep the VFS RCU protection intact (by reverting
>> commit 4f375ade6aa9), and defer the actual freeing to workqueue to avoid
>> sleep-in-atomic.
>>
>> Fixes: 1da6c4d9140c ("bpf: fix use after free in bpf_evict_inode")
>> Fixes: 4f375ade6aa9 ("bpf: Avoid RCU context warning when unpinning htab with internal structs")
>> Signed-off-by: Luo Gengkun <luogengkun2@huawei.com>
>> ---
>
> It looks like the problem has been fixed by:
> b93c55b4932d ("bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs")
Thanks, I will test it on my machine.
>
>> kernel/bpf/hashtab.c | 23 ++++++++++++++++++-----
>> kernel/bpf/inode.c | 4 ++--
>> 2 files changed, 20 insertions(+), 7 deletions(-)
>>
>> diff --git a/kernel/bpf/hashtab.c b/kernel/bpf/hashtab.c
>> index 3dd9b4924ae4..6d6f1faeec67 100644
>> --- a/kernel/bpf/hashtab.c
>> +++ b/kernel/bpf/hashtab.c
>> @@ -102,6 +102,7 @@ struct bpf_htab {
>> u32 n_buckets; /* number of hash buckets */
>> u32 elem_size; /* size of each element in bytes */
>> u32 hashrnd;
>> + struct work_struct work;
>> };
>>
>> /* each htab element is struct htab_elem + key + value */
>> @@ -539,6 +540,8 @@ static int htab_map_check_btf(struct bpf_map *map, const struct btf *btf,
>> return htab_set_dtor(htab, htab_mem_dtor);
>> }
>>
>> +static void htab_map_free_internal_structs_deferred(struct work_struct *work);
>> +
>> static struct bpf_map *htab_map_alloc(union bpf_attr *attr)
>> {
>> bool percpu = (attr->map_type == BPF_MAP_TYPE_PERCPU_HASH ||
>> @@ -557,6 +560,7 @@ static struct bpf_map *htab_map_alloc(union bpf_attr *attr)
>> if (!htab)
>> return ERR_PTR(-ENOMEM);
>>
>> + INIT_WORK(&htab->work, htab_map_free_internal_structs_deferred);
>> bpf_map_init_from_attr(&htab->map, attr);
>>
>> if (percpu_lru) {
>> @@ -1606,18 +1610,27 @@ static void htab_free_malloced_internal_structs(struct bpf_htab *htab)
>> rcu_read_unlock();
>> }
>>
>> -static void htab_map_free_internal_structs(struct bpf_map *map)
>> +static void htab_map_free_internal_structs_deferred(struct work_struct *work)
>> {
>> + struct bpf_map *map = container_of(work, struct bpf_map, work);
>> struct bpf_htab *htab = container_of(map, struct bpf_htab, map);
>>
>> - /* We only free internal structs on uref dropping to zero */
>> - if (!bpf_map_has_internal_structs(map))
>> - return;
>> -
>> if (htab_is_prealloc(htab))
>> htab_free_prealloced_internal_structs(htab);
>> else
>> htab_free_malloced_internal_structs(htab);
>> + bpf_map_put(map);
>> +}
>> +
>> +static void htab_map_free_internal_structs(struct bpf_map *map)
>> +{
>> + struct bpf_htab *htab = container_of(map, struct bpf_htab, map);
>> + /* We only free internal structs on uref dropping to zero */
>> + if (!bpf_map_has_internal_structs(map))
>> + return;
>> +
>> + bpf_map_inc(map);
>> + schedule_work(&htab->work);
>> }
>>
>> /* Called when map->refcnt goes to zero, either from workqueue or from syscall */
>> diff --git a/kernel/bpf/inode.c b/kernel/bpf/inode.c
>> index 25c06a011825..b6f295732f6f 100644
>> --- a/kernel/bpf/inode.c
>> +++ b/kernel/bpf/inode.c
>> @@ -762,7 +762,7 @@ static int bpf_show_options(struct seq_file *m, struct dentry *root)
>> return 0;
>> }
>>
>> -static void bpf_destroy_inode(struct inode *inode)
>> +static void bpf_free_inode(struct inode *inode)
>> {
>> enum bpf_type type;
>>
>> @@ -777,7 +777,7 @@ const struct super_operations bpf_super_ops = {
>> .statfs = simple_statfs,
>> .drop_inode = inode_just_drop,
>> .show_options = bpf_show_options,
>> - .destroy_inode = bpf_destroy_inode,
>> + .free_inode = bpf_free_inode,
>> };
>>
>> enum {
>
prev parent reply other threads:[~2026-06-08 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 2:28 Luo Gengkun
2026-06-06 3:25 ` bot+bpf-ci
2026-06-07 19:03 ` Mykyta Yatsenko
2026-06-08 1:25 ` Luo Gengkun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f99d0d59-d12b-417d-b02a-2ae73077056d@huawei.com \
--to=luogengkun2@huawei.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®