From: Christian Brauner <brauner@kernel.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ext4@vger.kernel.org, linux-nfs@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>,
linux-cifs@vger.kernel.org
Subject: Re: [PATCH 03/13] affs: free affs_sb_info with kfree_rcu()
Date: Mon, 5 Feb 2024 13:26:47 +0100 [thread overview]
Message-ID: <20240205-minus-ambivalent-48a4649275c7@brauner> (raw)
In-Reply-To: <20240204021739.1157830-3-viro@zeniv.linux.org.uk>
On Sun, Feb 04, 2024 at 02:17:29AM +0000, Al Viro wrote:
> one of the flags in it is used by ->d_hash()/->d_compare()
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> ---
Reviewed-by: Christian Brauner <brauner@kernel.org>
next prev parent reply other threads:[~2024-02-05 12:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 2:14 [PATCHES] RCU pathwalk race fixes Al Viro
2024-02-04 2:17 ` [PATCH 01/13] fs/super.c: don't drop ->s_user_ns until we free struct super_block itself Al Viro
2024-02-04 2:17 ` [PATCH 02/13] rcu pathwalk: prevent bogus hard errors from may_lookup() Al Viro
2024-02-05 12:26 ` Christian Brauner
2024-02-04 2:17 ` [PATCH 03/13] affs: free affs_sb_info with kfree_rcu() Al Viro
2024-02-05 12:26 ` Christian Brauner [this message]
2024-02-04 2:17 ` [PATCH 04/13] exfat: move freeing sbi, upcase table and dropping nls into rcu-delayed helper Al Viro
2024-02-05 12:27 ` Christian Brauner
2024-02-04 2:17 ` [PATCH 05/13] hfsplus: switch to rcu-delayed unloading of nls and freeing ->s_fs_info Al Viro
2024-02-05 12:27 ` Christian Brauner
2024-02-04 2:17 ` [PATCH 06/13] afs: fix __afs_break_callback() / afs_drop_open_mmap() race Al Viro
2024-02-05 12:28 ` Christian Brauner
2024-02-04 2:17 ` [PATCH 07/13] nfs: make nfs_set_verifier() safe for use in RCU pathwalk Al Viro
2024-02-05 12:29 ` Christian Brauner
2024-02-04 2:17 ` [PATCH 08/13] nfs: fix UAF on pathwalk running into umount Al Viro
2024-02-05 12:29 ` Christian Brauner
2024-02-04 2:17 ` [PATCH 09/13] procfs: move dropping pde and pid from ->evict_inode() to ->free_inode() Al Viro
2024-02-05 12:30 ` Christian Brauner
2024-02-04 2:17 ` [PATCH 10/13] procfs: make freeing proc_fs_info rcu-delayed Al Viro
2024-02-05 12:31 ` Christian Brauner
2024-02-04 2:17 ` [PATCH 11/13] fuse: fix UAF in rcu pathwalks Al Viro
2024-02-05 12:31 ` Christian Brauner
2024-02-05 13:51 ` Miklos Szeredi
2024-03-04 14:36 ` Amir Goldstein
2024-03-05 12:43 ` Miklos Szeredi
2024-03-06 10:18 ` Amir Goldstein
2024-03-06 10:21 ` Miklos Szeredi
2024-02-04 2:17 ` [PATCH 12/13] cifs_get_link(): bail out in unsafe case Al Viro
2024-02-04 15:45 ` Steve French
2024-02-04 16:25 ` Al Viro
2024-02-04 16:41 ` Al Viro
2024-02-04 2:17 ` [PATCH 13/13] ext4_get_link(): fix breakage in RCU mode Al Viro
2024-02-05 12:24 ` [PATCH 01/13] fs/super.c: don't drop ->s_user_ns until we free struct super_block itself Christian Brauner
2024-02-05 12:36 ` Jeff Layton
2024-02-04 2:27 ` RCU pathwalk audit notes Al Viro
2024-02-05 12:48 ` [PATCHES] RCU pathwalk race fixes Jeff Layton
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=20240205-minus-ambivalent-48a4649275c7@brauner \
--to=brauner@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
--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).