* [PATCH] cifs: fix the kernel release version in the default security warning message
@ 2011-06-03 6:36 Suresh Jayaraman
[not found] ` <4DE880E3.8020502-l3A5Bk7waGM@public.gmane.org>
0 siblings, 1 reply; 8+ messages in thread
From: Suresh Jayaraman @ 2011-06-03 6:36 UTC (permalink / raw)
To: Steve French; +Cc: linux-cifs
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;
--
1.7.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH] cifs: fix the kernel release version in the default security warning message
[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 15:31 ` Steve French
1 sibling, 1 reply; 8+ messages in thread
From: Jeff Layton @ 2011-06-03 13:11 UTC (permalink / raw)
To: Suresh Jayaraman; +Cc: Steve French, linux-cifs
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...
Reviewed-by: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] cifs: fix the kernel release version in the default security warning message
[not found] ` <4DE880E3.8020502-l3A5Bk7waGM@public.gmane.org>
2011-06-03 13:11 ` Jeff Layton
@ 2011-06-03 15:31 ` Steve French
1 sibling, 0 replies; 8+ messages in thread
From: Steve French @ 2011-06-03 15:31 UTC (permalink / raw)
To: Suresh Jayaraman; +Cc: linux-cifs
merged
On Fri, Jun 3, 2011 at 1:36 AM, 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;
>
> --
> 1.7.1
>
--
Thanks,
Steve
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] cifs: fix the kernel release version in the default security warning message
[not found] ` <20110603091119.7596fade-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
@ 2011-06-03 16:06 ` Suresh Jayaraman
[not found] ` <4DE90669.5020108-l3A5Bk7waGM@public.gmane.org>
0 siblings, 1 reply; 8+ messages in thread
From: Suresh Jayaraman @ 2011-06-03 16:06 UTC (permalink / raw)
To: Jeff Layton; +Cc: Steve French, linux-cifs
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?
> Reviewed-by: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-cifs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Suresh Jayaraman
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] cifs: fix the kernel release version in the default security warning message
[not found] ` <4DE90669.5020108-l3A5Bk7waGM@public.gmane.org>
@ 2011-06-03 16:26 ` Steve French
2011-06-03 16:37 ` Jeff Layton
1 sibling, 0 replies; 8+ messages in thread
From: Steve French @ 2011-06-03 16:26 UTC (permalink / raw)
To: Suresh Jayaraman; +Cc: Jeff Layton, linux-cifs
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] cifs: fix the kernel release version in the default security warning message
[not found] ` <4DE90669.5020108-l3A5Bk7waGM@public.gmane.org>
2011-06-03 16:26 ` Steve French
@ 2011-06-03 16:37 ` Jeff Layton
[not found] ` <20110603123739.4875a6e5-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
1 sibling, 1 reply; 8+ messages in thread
From: Jeff Layton @ 2011-06-03 16:37 UTC (permalink / raw)
To: Suresh Jayaraman; +Cc: Steve French, linux-cifs
On Fri, 03 Jun 2011 21:36:01 +0530
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?
>
Pity -- would have been sort of nice to always use a 3 field version
number since the stable kernels will need that, but...not my call.
Either way, patch is fine.
--
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] cifs: fix the kernel release version in the default security warning message
[not found] ` <20110603123739.4875a6e5-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
@ 2011-06-03 17:38 ` Scott Lovenberg
[not found] ` <4DE91C33.4040307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
0 siblings, 1 reply; 8+ messages in thread
From: Scott Lovenberg @ 2011-06-03 17:38 UTC (permalink / raw)
To: Jeff Layton; +Cc: Suresh Jayaraman, Steve French, linux-cifs
On 6/3/2011 12:37 PM, Jeff Layton wrote:
> On Fri, 03 Jun 2011 21:36:01 +0530
> 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?
>>
> Pity -- would have been sort of nice to always use a 3 field version
> number since the stable kernels will need that, but...not my call.
> Either way, patch is fine.
I think 3.0 was being called 3.0.0 officially because some scripts broke
without a "major.minor.revision" scheme. At least for the moment,
according to Linus' commit message.
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=55922c9d1b84b89cb946c777fddccb3247e7df2c
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] cifs: fix the kernel release version in the default security warning message
[not found] ` <4DE91C33.4040307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
@ 2011-06-03 17:41 ` Steve French
0 siblings, 0 replies; 8+ messages in thread
From: Steve French @ 2011-06-03 17:41 UTC (permalink / raw)
To: Scott Lovenberg; +Cc: Jeff Layton, Suresh Jayaraman, linux-cifs
On Fri, Jun 3, 2011 at 12:38 PM, Scott Lovenberg
<scott.lovenberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On 6/3/2011 12:37 PM, Jeff Layton wrote:
>>
>> On Fri, 03 Jun 2011 21:36:01 +0530
>> 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?
>>>
>> Pity -- would have been sort of nice to always use a 3 field version
>> number since the stable kernels will need that, but...not my call.
>> Either way, patch is fine.
>
> I think 3.0 was being called 3.0.0 officially because some scripts broke
> without a "major.minor.revision" scheme. At least for the moment, according
> to Linus' commit message.
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=55922c9d1b84b89cb946c777fddccb3247e7df2c
It won't matter for an informational message fortunately and 3.1 > 3.0.1
--
Thanks,
Steve
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2011-06-03 17:41 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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.