From: Christian Brauner <brauner@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Christian Brauner <brauner@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Amir Goldstein <amir73il@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] cred: Fix RCU warnings in override/revert_creds
Date: Sun, 2 Mar 2025 13:01:49 +0100 [thread overview]
Message-ID: <20250302-fazit-pillen-3e7500ee5fbf@brauner> (raw)
In-Reply-To: <Z8QGQGW0IaSklKG7@gondor.apana.org.au>
On Sun, 02 Mar 2025 15:18:24 +0800, Herbert Xu wrote:
> Fix RCU warnings in override_creds and revert_creds by turning
> the RCU pointer into a normal pointer using rcu_replace_pointer.
>
> These warnings were previously private to the cred code, but due
> to the move into the header file they are now polluting unrelated
> subsystems.
>
> [...]
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] cred: Fix RCU warnings in override/revert_creds
https://git.kernel.org/vfs/vfs/c/e04918dc5946
prev parent reply other threads:[~2025-03-02 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 7:18 Herbert Xu
2025-03-02 12:01 ` 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=20250302-fazit-pillen-3e7500ee5fbf@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vinicius.gomes@intel.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®