mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yusong Gao <a869920004@163.com>
To: brauner@kernel.org
Cc: a869920004@163.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [RESEND PATCH] fs: Fix typo in access_override_creds()
Date: Tue, 31 Oct 2023 02:11:30 +0000	[thread overview]
Message-ID: <20231031021130.855308-1-a869920004@163.com> (raw)
In-Reply-To: <20231030-debatten-nachrangig-f58abcdac530@brauner>

At 2023-10-30 16:32:37, "Christian Brauner" <brauner@kernel.org> wrote:
>On Mon, Oct 30, 2023 at 01:52:35AM +0000, gaoyusong wrote:
>> From: Yusong Gao <a869920004@163.com>
>> 
>> Fix typo in access_override_creds(), modify non-RCY to non-RCU.
>> 
>> Signed-off-by: gaoyusong <a869920004@163.com>
>> ---
>>  fs/open.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/fs/open.c b/fs/open.c
>> index 98f6601fbac6..72eb20a8256a 100644
>> --- a/fs/open.c
>> +++ b/fs/open.c
>> @@ -442,7 +442,7 @@ static const struct cred *access_override_creds(void)
>>  	 * 'get_current_cred()' function), that will clear the
>>  	 * non_rcu field, because now that other user may be
>>  	 * expecting RCU freeing. But normal thread-synchronous
>> -	 * cred accesses will keep things non-RCY.
>> +	 * cred accesses will keep things non-RCU.
>
>I think this might have been intended as a joke aka "non-RCY" as in
>"non-racy" here. I think best would be to change it to something like
>"cred accesses will keep things non-racy and allows to avoid rcu freeing"
>if you care enough.

I see what you mean. Thanks for your reply. I don't think any more
changes are needed when I figure out it.


      reply	other threads:[~2023-10-31  2:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  1:52 gaoyusong
2023-10-30  8:32 ` Christian Brauner
2023-10-31  2:11   ` Yusong Gao [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=20231031021130.855308-1-a869920004@163.com \
    --to=a869920004@163.com \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®