From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Christian Brauner <brauner@kernel.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
<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: Thu, 13 Apr 2023 09:34:54 +0800 [thread overview]
Message-ID: <a01a789c-8965-d1dc-cb45-ea9901a9af34@huawei.com> (raw)
In-Reply-To: <20230412-sympathie-haltbar-da2d2183067b@brauner>
On 2023/4/12 17:19, 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.
>>
>>
>> On 2023/3/31 16:45, Kefeng Wang wrote:
>>> 'obj-$(CONFIG_SYSCTL) += sysctls.o' must be moved after "obj-y :=",
>>> or it won't be built as it is overwrited.
...
> Given the description in
> ab171b952c6e ("fs: move namespace sysctls and declare fs base directory")
> you probably want to move this earlier.
Oh, missing that part, but the /proc/sys/fs/overflowuid and overflowgid
are lost after it, is it expected? Luis, could you take a look? thanks.
>
next prev parent reply other threads:[~2023-04-13 1:35 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 [this message]
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
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=a01a789c-8965-d1dc-cb45-ea9901a9af34@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.