From: Christian Brauner <brauner@kernel.org>
To: syzkaller-bugs@googlegroups.com,
syzbot+a3e82ae343b26b4d2335@syzkaller.appspotmail.com,
Christian Brauner <brauner@kernel.org>
Cc: akpm@linux-foundation.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, viro@zeniv.linux.org.uk,
Alexander Mikhalitsyn <alexander@mihalicyn.com>
Subject: Re: [PATCH] nsfs: use cleanup guard
Date: Tue, 16 Jul 2024 09:28:44 +0200 [thread overview]
Message-ID: <20240716-unsterblich-ausnutzen-7c57cce852e4@brauner> (raw)
In-Reply-To: <20240716-elixier-fliesen-1ab342151a61@brauner>
On Tue, 16 Jul 2024 09:19:11 +0200, Christian Brauner wrote:
> Ensure that rcu read lock is given up before returning.
>
>
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes 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.fixes
[1/1] nsfs: use cleanup guard
https://git.kernel.org/vfs/vfs/c/0052b241e3e5
prev parent reply other threads:[~2024-07-16 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 1:24 [syzbot] [mm?] BUG: sleeping function called from invalid context in vma_alloc_folio_noprof syzbot
2024-07-16 3:51 ` Andrew Morton
2024-07-16 7:19 ` [PATCH] nsfs: use cleanup guard Christian Brauner
2024-07-16 7:28 ` Christian Brauner [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=20240716-unsterblich-ausnutzen-7c57cce852e4@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander@mihalicyn.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+a3e82ae343b26b4d2335@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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