From: Christian Brauner <brauner@kernel.org>
To: mic@digikod.net, Mateusz Guzik <mjguzik@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
eadavis@qq.com, gnoack@google.com, jack@suse.cz,
jannh@google.com, max.kellermann@ionos.com, m@maowtm.org,
syzbot+12479ae15958fc3f54ec@syzkaller.appspotmail.com
Subject: Re: [PATCH 1/2] fs: add iput_not_last()
Date: Tue, 11 Nov 2025 12:46:21 +0100 [thread overview]
Message-ID: <20251111-fluss-vokabel-7be060af7f11@brauner> (raw)
In-Reply-To: <20251105212025.807549-1-mjguzik@gmail.com>
On Wed, 05 Nov 2025 22:20:24 +0100, Mateusz Guzik wrote:
>
Applied to the vfs-6.19.inode branch of the vfs/vfs.git tree.
Patches in the vfs-6.19.inode 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.inode
[1/2] fs: add iput_not_last()
https://git.kernel.org/vfs/vfs/c/a1cece5d8881
[2/2] landlock: fix splats from iput() after it started calling might_sleep()
https://git.kernel.org/vfs/vfs/c/9638e5c3b673
next prev parent reply other threads:[~2025-11-11 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 21:20 [PATCH 1/2] fs: add iput_not_last() Mateusz Guzik
2025-11-05 21:20 ` [PATCH 2/2] landlock: fix splats from iput() after it started calling might_sleep() Mateusz Guzik
2025-11-06 8:45 ` Mickaël Salaün
2025-11-06 9:43 ` [PATCH 1/2] fs: add iput_not_last() Jan Kara
2025-11-11 11:46 ` Christian Brauner [this message]
2025-11-11 11:53 ` Mateusz Guzik
2025-11-12 9:48 ` Christian Brauner
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=20251111-fluss-vokabel-7be060af7f11@brauner \
--to=brauner@kernel.org \
--cc=eadavis@qq.com \
--cc=gnoack@google.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=m@maowtm.org \
--cc=max.kellermann@ionos.com \
--cc=mic@digikod.net \
--cc=mjguzik@gmail.com \
--cc=syzbot+12479ae15958fc3f54ec@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).