From: syzbot <syzbot+76a6f18e3af82e84f264@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] Re: [syzbot] [afs?] general protection fault in afs_atcell_get_link
Date: Tue, 18 Mar 2025 02:10:43 -0700 [thread overview]
Message-ID: <67d93893.050a0220.2ca2c6.0165.GAE@google.com> (raw)
In-Reply-To: <67d92a74.050a0220.2ca2c6.014f.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [afs?] general protection fault in afs_atcell_get_link
Author: enjuk@amazon.com
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: b35233e7bfa0 Merge tag 'for-6.14/dm-fixes-2' of git://git...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1232704c580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=317038cbd53153e8
> dashboard link: https://syzkaller.appspot.com/bug?extid=76a6f18e3af82e84f264
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17d3fc78580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169fb874580000
#syz test
diff --git a/fs/afs/dynroot.c b/fs/afs/dynroot.c
index 9732a1e17db3..3ea5e388ee16 100644
--- a/fs/afs/dynroot.c
+++ b/fs/afs/dynroot.c
@@ -213,6 +213,9 @@ static const char *afs_atcell_get_link(struct dentry *dentry, struct inode *inod
if (!dentry) {
/* We're in RCU-pathwalk. */
cell = rcu_dereference(net->ws_cell);
+ if (!cell)
+ return ERR_PTR(-ENOENT);
+
if (dotted)
name = cell->name - 1;
else
next prev parent reply other threads:[~2025-03-18 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 8:10 [syzbot] [afs?] general protection fault in afs_atcell_get_link syzbot
2025-03-18 9:10 ` syzbot [this message]
2025-03-18 9:17 ` Edward Adam Davis
2025-03-18 9:51 ` syzbot
2025-03-18 9:26 ` [PATCH] afs: Fix a null-ptr-deref " Edward Adam Davis
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=67d93893.050a0220.2ca2c6.0165.GAE@google.com \
--to=syzbot+76a6f18e3af82e84f264@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.