From: Jeff Layton <jlayton@redhat.com>
To: Jesper Nilsson <jesper.nilsson@axis.com>
Cc: linux-cifs@vger.kernel.org, sfrench@samba.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFQ PATCH] cifs: Change default security error message
Date: Thu, 29 Nov 2012 13:25:09 -0500 [thread overview]
Message-ID: <20121129132509.211c4977@corrin.poochiereds.net> (raw)
In-Reply-To: <20121129173053.GQ27196@axis.com>
On Thu, 29 Nov 2012 18:30:53 +0100
Jesper Nilsson <jesper.nilsson@axis.com> wrote:
> Hi!
>
> Connecting with a default security mechanism prompts an KERN_ERROR
> output warning to the user that the default mechanism will be changed
> in Linux 3.3.
>
> We're now at 3.7, so we either could remove the warning completely
> (if the default has been changed), or we could bump the number to
> what our current target for the change is.
>
>
> The below patch changes the cERROR (which turns into a printk with KERN_ERROR)
> into a straight printk with KERN_WARNING and changes the text to indicate
> that it was changed in 3.3.
>
> I expect that the patch is incorrect and that we should choose
> another of the alternative solutions above, but I'd like to get
> some input on this.
>
> Not-Signed-off-by: Jesper Nilsson <jesper.nilsson@axis.com>
> ---
> diff --git a/fs/cifs/connect.c b/fs/cifs/connect.c
> index c83f5b65..968456f 100644
> --- a/fs/cifs/connect.c
> +++ b/fs/cifs/connect.c
> @@ -2480,9 +2480,9 @@ cifs_get_smb_ses(struct TCP_Server_Info *server, struct smb_vol *volume_info)
> supported for many years, time to update default security mechanism */
> if ((volume_info->secFlg == 0) && warned_on_ntlm == false) {
> warned_on_ntlm = true;
> - cERROR(1, "default security mechanism requested. The default "
> - "security mechanism will be upgraded from ntlm to "
> - "ntlmv2 in kernel release 3.3");
> + printk(KERN_WARNING "default security mechanism requested. "
> + "The default security mechanism was changed "
> + " from ntlm to ntlmv2 in kernel release 3.3");
> }
> ses->overrideSecFlg = volume_info->secFlg;
>
>
>
> /^JN - Jesper Nilsson
I think this warning has lived long enough and needs to go away. Steve
supposedly has a patch that finally makes this change, but it hasn't
been sent to the list yet... Steve?
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-11-29 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 17:30 Jesper Nilsson
2012-11-29 17:52 ` Steve French
2012-11-29 18:47 ` Jesper Nilsson
2012-12-03 10:36 ` [PATCH] MAINTAINERS: Fix cifs-tree git url Jesper Nilsson
2012-11-29 18:25 ` Jeff Layton [this message]
2012-11-29 18:54 ` [RFQ PATCH] cifs: Change default security error message Steve French
2012-11-29 20:36 ` Jeff Layton
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=20121129132509.211c4977@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=jesper.nilsson@axis.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.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®