From: Breno Leitao <leitao@debian.org>
To: syzbot <syzbot+2f6a3b7dc3b442ef515c@syzkaller.appspotmail.com>
Cc: a.hindborg@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] general protection fault in do_getname_kernel
Date: Thu, 6 Aug 2026 02:04:34 -0700 [thread overview]
Message-ID: <anRNVC1S58v5OYbd@gmail.com> (raw)
In-Reply-To: <6a73bcd5.01d0871a.3a0d52.0004.GAE@google.com>
Andreas,
On Wed, Aug 05, 2026 at 03:44:37PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
This looks related to the recent configfs changes — we've had several
similar reports.
The fixes I've seen so far don't look right to me, and are coming from
people that are just using AI to fix it, causing more mess than help.
See the comments for those that I've reviewed.
Do you have something in the works, or should I dig into it?
--breno
prev parent reply other threads:[~2026-08-06 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 22:44 [syzbot] [fs?] general protection fault in do_getname_kernel syzbot
2026-08-06 9:04 ` Breno Leitao [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=anRNVC1S58v5OYbd@gmail.com \
--to=leitao@debian.org \
--cc=a.hindborg@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2f6a3b7dc3b442ef515c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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