From: Chuck Lever III <chuck.lever@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 22 (NFSD_V2_ACL)
Date: Thu, 24 Feb 2022 16:45:52 +0000 [thread overview]
Message-ID: <1253C13F-B917-4AEE-A746-4ABB06150ED4@oracle.com> (raw)
In-Reply-To: <bc529f39-52c7-fd54-b435-d6c62351c526@infradead.org>
> On Feb 24, 2022, at 11:37 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 2/24/22 07:08, Chuck Lever III wrote:
>>
>>
>>> On Feb 24, 2022, at 1:45 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
>>>
>>>
>>>
>>> On 2/23/22 07:58, Chuck Lever III wrote:
>>>>
>>>>> On Feb 23, 2022, at 1:08 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
>>>>>
>>>>> On 2/22/22 17:41, broonie@kernel.org wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Note that today's -next does not include the akpm tree since it's been a
>>>>>> long day and the conflicts seemed more than it was wise for me to
>>>>>> attempt at this point. I'll have another go tomorrow but no guarantees.
>>>>>>
>>>>>> Changes since 20220217:
>>>>>
>>>>> on x86_64:
>>>>>
>>>>> WARNING: unmet direct dependencies detected for NFSD_V2_ACL
>>>>> Depends on [n]: NETWORK_FILESYSTEMS [=y] && NFSD [=n]
>>>>> Selected by [y]:
>>>>> - NFSD_V3_ACL [=y] && NETWORK_FILESYSTEMS [=y]
>>>>
>>>> Thanks, Randy. I think I've got it addressed in my for-next.
>>>
>>> Hi Chuck,
>>>
>>> I'm still seeing this in next-20220223...
>>
>> I tested my fixed version of the commit with the randconfig
>> you attached to yesterday's email. Do you see this in
>> fs/nfsd/Kconfig from next-20220223 ?
>
> Not all of it -- it's missing one line:
>
>> config NFSD_V2_ACL
>> bool
>> depends on NFSD
>>
>> config NFSD_V3_ACL
>> bool "NFS server support for the NFSv3 ACL protocol extension"
>> depends on NFSD <<<<<<<<<<<<<<<<<<<<<< HERE <<<<<<<<<<<<<<<
>> select NFSD_V2_ACL
>> help
>
> When I add that, I no longer see the problem.
That's the fix. I guess next-20220223 hasn't pulled in my latest
for-next yet.
--
Chuck Lever
prev parent reply other threads:[~2022-02-24 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 1:41 linux-next: Tree for Feb 22 broonie
2022-02-23 6:05 ` linux-next: Tree for Feb 22 (NET_DSA_SMSC_LAN9303) Randy Dunlap
2022-02-23 6:08 ` linux-next: Tree for Feb 22 (NFSD_V2_ACL) Randy Dunlap
2022-02-23 15:58 ` Chuck Lever III
2022-02-24 6:45 ` Randy Dunlap
2022-02-24 15:08 ` Chuck Lever III
2022-02-24 16:37 ` Randy Dunlap
2022-02-24 16:45 ` Chuck Lever III [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=1253C13F-B917-4AEE-A746-4ABB06150ED4@oracle.com \
--to=chuck.lever@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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®