From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>, Kuniyuki Iwashima <kuniyu@google.com>
Cc: Christian Brauner <brauner@kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Matthew Bobrowski <repnop@google.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+321168dfa622eda99689@syzkaller.appspotmail.com
Subject: Re: [PATCH] fanotify: Don't call fsnotify_destroy_group() when fsnotify_alloc_group() fails.
Date: Fri, 28 Nov 2025 09:53:21 +0100 [thread overview]
Message-ID: <20251128-umzug-sandgrube-d5b1adfccf02@brauner> (raw)
In-Reply-To: <20251127201618.2115275-1-kuniyu@google.com>
On Thu, 27 Nov 2025 20:16:15 +0000, Kuniyuki Iwashima wrote:
> syzbot reported the splat in __do_sys_fanotify_init(). [0]
>
> The cited commit introduced the fsnotify_group class.
>
> The constructor is fsnotify_alloc_group() and could fail,
> so the error is handled this way:
>
> [...]
Applied to the vfs-6.19.fd_prepare branch of the vfs/vfs.git tree.
Patches in the vfs-6.19.fd_prepare branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.19.fd_prepare
[1/1] fanotify: Don't call fsnotify_destroy_group() when fsnotify_alloc_group() fails.
https://git.kernel.org/vfs/vfs/c/c2f27f6b8c79
next prev parent reply other threads:[~2025-11-28 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 20:16 Kuniyuki Iwashima
2025-11-28 8:53 ` Christian Brauner [this message]
2025-11-28 9:03 ` Christian Brauner
2025-11-28 11:30 ` Jan Kara
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=20251128-umzug-sandgrube-d5b1adfccf02@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=kuniyu@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=repnop@google.com \
--cc=syzbot+321168dfa622eda99689@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
all inboxes | Powered by JetHome®