mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yonghong Song <yonghong.song@linux.dev>
To: hongao <hongao@uniontech.com>, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, eddyz87@gmail.com, memxor@gmail.com,
	song@kernel.org, jolsa@kernel.org, kafai.wan@linux.dev,
	linux-kernel@vger.kernel.org,
	syzbot+0962e3a1af6d5e26a52c@syzkaller.appspotmail.com
Subject: Re: [PATCH] bpf: defer bpffs symlink inode freeing until RCU grace period
Date: Mon, 1 Jun 2026 13:42:39 -0700	[thread overview]
Message-ID: <d8ee5e71-aa2c-4131-ac80-7896b1042ae2@linux.dev> (raw)
In-Reply-To: <B36A1A9E983EE6EC+20260530013022.1692378-1-hongao@uniontech.com>



On 5/29/26 6:30 PM, hongao wrote:
> bpffs currently frees inodes directly from ->destroy_inode(). This can
> race with RCU path walk following a bpffs symlink: a lookup reader may
> still hold an unstable inode pointer while unlink frees the inode
> memory, leading to a KASAN use-after-free in
> security_inode_follow_link().
>
> Keep BPF object reference dropping in ->destroy_inode(), where sleeping
> cleanup is allowed, but move symlink target and inode memory freeing to
> ->free_inode() so VFS releases them after an RCU grace period.
>
> Fixes: 4f375ade6aa9 ("bpf: Avoid RCU context warning when unpinning htab with internal structs")
> Reported-by: syzbot+0962e3a1af6d5e26a52c@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=0962e3a1af6d5e26a52c
> Tested-by: syzbot+0962e3a1af6d5e26a52c@syzkaller.appspotmail.com
> Signed-off-by: hongao <hongao@uniontech.com>

Please have tag [PATCH bpf] to indicate it is form bpf tree.
Please have proper name instead of hongao. See examples in bpf repo.
Other than the above, the patch LGTM.

Acked-by: Yonghong Song <yonghong.song@linux.dev>

> ---
>   kernel/bpf/inode.c | 9 +++++++--
>   1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/bpf/inode.c b/kernel/bpf/inode.c
> index 25c06a011825..a1e9660f9237 100644
> --- a/kernel/bpf/inode.c
> +++ b/kernel/bpf/inode.c
> @@ -766,10 +766,14 @@ static void bpf_destroy_inode(struct inode *inode)
>   {
>   	enum bpf_type type;
>   
> -	if (S_ISLNK(inode->i_mode))
> -		kfree(inode->i_link);
>   	if (!bpf_inode_type(inode, &type))
>   		bpf_any_put(inode->i_private, type);
> +}
> +
> +static void bpf_free_inode(struct inode *inode)
> +{
> +	if (S_ISLNK(inode->i_mode))
> +		kfree(inode->i_link);
>   	free_inode_nonrcu(inode);
>   }
>   
> @@ -778,6 +782,7 @@ const struct super_operations bpf_super_ops = {
>   	.drop_inode	= inode_just_drop,
>   	.show_options	= bpf_show_options,
>   	.destroy_inode	= bpf_destroy_inode,
> +	.free_inode	= bpf_free_inode,
>   };
>   
>   enum {


      reply	other threads:[~2026-06-01 20:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30  1:30 hongao
2026-06-01 20:42 ` Yonghong Song [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=d8ee5e71-aa2c-4131-ac80-7896b1042ae2@linux.dev \
    --to=yonghong.song@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=hongao@uniontech.com \
    --cc=jolsa@kernel.org \
    --cc=kafai.wan@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=song@kernel.org \
    --cc=syzbot+0962e3a1af6d5e26a52c@syzkaller.appspotmail.com \
    /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

Powered by JetHome