All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Christian Brauner <brauner@kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] fs: fix sysctls.c built
Date: Fri, 14 Apr 2023 09:19:07 +0800	[thread overview]
Message-ID: <61c62ae1-4c2b-5768-5044-93e43b6585de@huawei.com> (raw)
In-Reply-To: <ZDhbcRRDlCN9Dk6Y@bombadil.infradead.org>



On 2023/4/14 3:43, Luis Chamberlain wrote:
> On Thu, Apr 13, 2023 at 11:46:24AM -0700, Luis Chamberlain wrote:
>> On Thu, Apr 13, 2023 at 10:06:35AM -0700, Luis Chamberlain wrote:
>>> On Wed, Apr 12, 2023 at 11:19:56AM +0200, Christian Brauner wrote:
>>>> On Tue, Apr 11, 2023 at 12:14:44PM +0800, Kefeng Wang wrote:
>>>>> /proc/sys/fs/overflowuid and overflowgid  will be lost without
>>>>> building this file, kindly ping, any comments, thanks.
>>>>>
>>>>>
...
>>>>
>>>> Given the description in
>>>> ab171b952c6e ("fs: move namespace sysctls and declare fs base directory")
>>>> you probably want to move this earlier.
>>>
>>> I was being *way* too cautious and I was wrong, so I'll take Kefang's patch as
>>> I can verify now that order does not matter and his patch is correct.
>>> I've corrected the documentation and clarified this on sysctl-next and
>>> so reflected on linux-next too with these two patches:
>>>
>>> sysctl: clarify register_sysctl_init() base directory order
>>> https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/commit/?h=sysctl-next-20230413&id=8ae59580f2b0529b6dd1a1cda6b838cfb268cb87
>>>
>>> proc_sysctl: move helper which creates required subdirectories
>>> https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/commit/?h=sysctl-next-20230413&id=f4c09b14073513efd581459520a01c4c88cb24d7
>>>
>>> proc_sysctl: update docs for __register_sysctl_table()
>>> https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/commit/?h=sysctl-next-20230413&id=d59d91edd67ec4cef62f26249510fe08b291ae72
>>>
>>> proc_sysctl: enhance documentation
>>> https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/commit/?h=sysctl-next-20230413&id=eb472aa0678fd03321093bffeb9c7fd7f5035844
>>>
>>> And so something we can do eventually is do away with all the base stuff.
>>> For now it's fine, it's not creating an issue.
>>
>> Come to think of it all the above patches except the one that moves code
>> ("proc_sysctl: move helper which creates required subdirectories") are
>> stable fix candidates prior to Kefeng's patch. I'll also update Kefeng's
>> patch to mention stable down to v5.17 and update the other patches with
>> the respective stable tag as well.

Thanks for your detail explanation.

> 
> OK pushed to sysctl-next and updated the patches above also to refer to
> stable and Cc you guys. Finally, a good reason or value to having Cc on
> the commit log. It just tmeans you (Christian and Kefeng) will be be CC'd
> once this trickles to stable kernel trees too.
> 
>    Luis

      reply	other threads:[~2023-04-14  1:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  8:45 [PATCH] fs: fix sysctls.c built Kefeng Wang
2023-04-11  4:14 ` Kefeng Wang
2023-04-12  9:19   ` Christian Brauner
2023-04-13  1:34     ` Kefeng Wang
2023-04-13  8:35       ` Christian Brauner
2023-04-13  9:45         ` Kefeng Wang
2023-04-13 12:06           ` Christian Brauner
2023-04-13 17:06     ` Luis Chamberlain
2023-04-13 18:46       ` Luis Chamberlain
2023-04-13 19:43         ` Luis Chamberlain
2023-04-14  1:19           ` Kefeng Wang [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=61c62ae1-4c2b-5768-5044-93e43b6585de@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.