From: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
Cc: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] cifs: fix the kernel release version in the default security warning message
Date: Fri, 3 Jun 2011 11:26:00 -0500 [thread overview]
Message-ID: <BANLkTik3B5rZbOy6aPCN09dwWhtRDExhjw@mail.gmail.com> (raw)
In-Reply-To: <4DE90669.5020108-l3A5Bk7waGM@public.gmane.org>
On Fri, Jun 3, 2011 at 11:06 AM, Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
> On 06/03/2011 06:41 PM, Jeff Layton wrote:
>> On Fri, 03 Jun 2011 12:06:19 +0530
>> Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
>>
>>>
>>> When ntlm security mechanim is used, the message that warns about the upgrade
>>> to ntlmv2 got the kernel release version wrong (Blame it on Linus :). Fix it.
>>>
>>> Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
>>> ---
>>> fs/cifs/connect.c | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
>>> index 6d88b82..84c7307 100644
>>> --- a/fs/cifs/connect.c
>>> +++ b/fs/cifs/connect.c
>>> @@ -1976,7 +1976,7 @@ cifs_get_smb_ses(struct TCP_Server_Info *server, struct smb_vol *volume_info)
>>> warned_on_ntlm = true;
>>> cERROR(1, "default security mechanism requested. The default "
>>> "security mechanism will be upgraded from ntlm to "
>>> - "ntlmv2 in kernel release 2.6.41");
>>> + "ntlmv2 in kernel release 3.1");
>>> }
>>> ses->overrideSecFlg = volume_info->secFlg;
>>>
>>
>> Looks good. Though I'm not sure whether we should call it 3.1.0?
>> Regardless...
>
> I thought about this. But, as Linus has already said:
>
> "Now, my alpha-maleness sadly does not actually extend to all the
> scripts and Makefile rules, so the kernel is fighting back, and is
> calling itself 3.0.0-rc1. We'll have the usual 6-7 weeks to wrestle it
> into submission, and get scripts etc cleaned up, and the final release
> should be just "3.0". The -stable team can use the third number for
> their versioning."
>
> I think 3.1 should be ok?
Yes.
--
Thanks,
Steve
next prev parent reply other threads:[~2011-06-03 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 6:36 [PATCH] cifs: fix the kernel release version in the default security warning message Suresh Jayaraman
[not found] ` <4DE880E3.8020502-l3A5Bk7waGM@public.gmane.org>
2011-06-03 13:11 ` Jeff Layton
[not found] ` <20110603091119.7596fade-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-06-03 16:06 ` Suresh Jayaraman
[not found] ` <4DE90669.5020108-l3A5Bk7waGM@public.gmane.org>
2011-06-03 16:26 ` Steve French [this message]
2011-06-03 16:37 ` Jeff Layton
[not found] ` <20110603123739.4875a6e5-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-06-03 17:38 ` Scott Lovenberg
[not found] ` <4DE91C33.4040307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-03 17:41 ` Steve French
2011-06-03 15:31 ` Steve French
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=BANLkTik3B5rZbOy6aPCN09dwWhtRDExhjw@mail.gmail.com \
--to=smfrench-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjayaraman-l3A5Bk7waGM@public.gmane.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