From: Weng Meiling <wengmeiling.weng@huawei.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: <linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Li Zefan <lizefan@huawei.com>
Subject: Re: [PATCH] nfsd:add '\n' when read file supported_krb5_enctypes
Date: Fri, 15 Nov 2013 08:32:27 +0800 [thread overview]
Message-ID: <52856B9B.7000307@huawei.com> (raw)
In-Reply-To: <20131114132517.GA20059@fieldses.org>
On 2013/11/14 21:25, J. Bruce Fields wrote:
> On Thu, Nov 14, 2013 at 08:38:55PM +0800, Weng Meiling wrote:
>> On 2013/11/14 0:09, J. Bruce Fields wrote:
>>> On Fri, Nov 08, 2013 at 03:23:28PM +0800, Weng Meiling wrote:
>>>>
>>>> From: Weng Meiling <wengmeiling.weng@huawei.com>
>>>
>>> I agree completely that a \n at the end would make more sense.
>>>
>>> Have you tested that this nfs-utils is OK with this change?
>>>
>>> I suspect that the only code that reads this file anywhere is
>>>
>>> nfs-utils/utils/gssd/svcgssd_krb5.c:parse_enctypes()
>>>
>>> And on a quick skim of that function.... I *think* it should be fine.
>>> But I'd be happier if you could confirm that you've tested it.
>>>
>>> --b.
>>>
>> After this change, starting the nfs server, other host can use the
>> server's shared files normally :-).
>
> I don't see how that tests parse_enctypes().
>
> --b.
>
yes,this did not test parse_enctypes() specially, I just try to use nfs with this change,
I'll test it later.
Thanks!
Weng Meiling
>>
>> Thanks!
>> Weng Meilling
>>>>
>>>> Signed-off-by: Weng Meiling <wengmeiling.weng@huawei.com>
>>>> ---
>>>> fs/nfsd/nfsctl.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
>>>> index 7f55517..31db42c 100644
>>>> --- a/fs/nfsd/nfsctl.c
>>>> +++ b/fs/nfsd/nfsctl.c
>>>> @@ -188,7 +188,7 @@ static const struct file_operations export_features_operations = {
>>>> #if defined(CONFIG_SUNRPC_GSS) || defined(CONFIG_SUNRPC_GSS_MODULE)
>>>> static int supported_enctypes_show(struct seq_file *m, void *v)
>>>> {
>>>> - seq_printf(m, KRB5_SUPPORTED_ENCTYPES);
>>>> + seq_printf(m, "%s\n", KRB5_SUPPORTED_ENCTYPES);
>>>> return 0;
>>>> }
>>>>
>>>> --
>>>> 1.8.3.1
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
> .
>
prev parent reply other threads:[~2013-11-15 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52786412.5030403@huawei.com>
2013-11-08 7:23 ` [PATCH] nfsd:add '\n' when read file supported_krb5_enctypes Weng Meiling
2013-11-13 16:09 ` J. Bruce Fields
2013-11-14 12:38 ` Weng Meiling
2013-11-14 13:25 ` J. Bruce Fields
2013-11-15 0:32 ` Weng Meiling [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=52856B9B.7000307@huawei.com \
--to=wengmeiling.weng@huawei.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lizefan@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).