On 11/13/2013 11:01 AM, Anna Schumaker wrote:
> On 11/12/2013 02:59 PM, J. Bruce Fields wrote:
>> On Tue, Nov 12, 2013 at 02:54:15PM -0500, Anna Schumaker wrote:
>>> On 11/12/2013 02:45 PM, J. Bruce Fields wrote:
>>>> On Tue, Nov 12, 2013 at 02:04:05PM -0500, Anna Schumaker wrote:
>>>>> These patches implement just the SEEK NFS v4.2 operation. WRITE_PLUS is
>>>>> still under discussion with the IETF after my last series of patches, so I
>>>>> am holding off on resubmitting until after spec discussion dies down.
>>>>>
>>>>> Questions? Comments? Thoughts?
>>>>> Anna
>>>>>
>>>>> Anna Schumaker (3):
>>>>> NFSD: Update error codes
>>>>
>>>> I don't think I got this first patch.
>>>
>>> It's in the "patches" directory I used, but I don't see it in my gmail inbox either. I'll send it out in a minute.
>>>
>>>>
>>>>> NFSD: Create nfs v4.2 decode ops
>>>>> NFSD: Implement SEEK
>>>>
>>>> I'd like to be reassured the protocol is reasonably stable before we
>>>> commit this. I haven't been following the ietf wg discussion closely.
>>>>
>>>> And this should initially be disabled by default. So, probably either:
>>>>
>>>> - Introduce a new NFSD_V4_SEEK option, or
>>>> - Combine this and NFSD_V4_SECURITY_LABEL and this into a single
>>>> NFSD_V4_2 option.
>>>>
>>>> And recommend "N" for now.
>>>>
>>>> Probably the latter I guess, to be consistent with the client. And
>>>> because otherwise we could end up with an awful lot of config options.
>>>
>>> Sure, I can do that easily enough.
>>
>> OK. In that case, you'll probably want to do an additional patch at the
>> beginning just to replace NFSD_V4_SECURITY_LABEL by NFSD_V4_2. Note
>> it's not a pure search-and-replace since the latter covers a little more
>> code.
>
> Would you accept a patch that instead introduces CONFIG_NFSD_V4_2 and then makes the security label depend on that config option?
>
I'm thinking something like this:
diff --git a/fs/nfsd/Kconfig b/fs/nfsd/Kconfig
index dc8f1ef..5d0ca71 100644
--- a/fs/nfsd/Kconfig
+++ b/fs/nfsd/Kconfig
@@ -81,9 +81,18 @@ config NFSD_V4
If unsure, say N.
+config NFSD_V4_2
+ bool "Server support for NFS v4.2"
+ depends on NFSD_V4
+ help
+ This option enables support for minor version 2 of the NFSv4 protocol
+ in the kernel's NFS server.
+
+ If unsure, say N.
+
config NFSD_V4_SECURITY_LABEL
bool "Provide Security Label support for NFSv4 server"
- depends on NFSD_V4 && SECURITY
+ depends on NFSD_V4_2 && SECURITY
help
Say Y here if you want enable fine-grained security label attribute
>>
>> The only thing that worries me a bit is the features may mature at
>> different times. I guess when the time comes we could split it into
>> NFSD_V4_2 and NFSD_V4_2_EXPERIMENTAL and recommend distros and
>> non-developers turn on only the former?
>>
>> --b.
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
