From: Joe Perches <joe@perches.com>
To: Anton Protopopov <a.s.protopopov@gmail.com>,
Steve French <sfrench@samba.org>
Cc: linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cifs: fix erroneous return value
Date: Wed, 10 Feb 2016 09:59:46 -0800 [thread overview]
Message-ID: <1455127186.3333.44.camel@perches.com> (raw)
In-Reply-To: <1455126621-28052-1-git-send-email-a.s.protopopov@gmail.com>
On Wed, 2016-02-10 at 12:50 -0500, Anton Protopopov wrote:
> The setup_ntlmv2_rsp() function may return positive value ENOMEM instead
> of -ENOMEM in case of kmalloc failure.
How have you verified this change is correct?
Have you checked that the callers of this function in
fs/cifs/sess.c do the appropriate things with with a
negative return value?
The return value is now set into a struct member variable
as a positive value,
sess_data->result = rc;
Have you checked all the users of this member variable?
If you have, you should say so in the commit message.
> Signed-off-by: Anton Protopopov <a.s.protopopov@gmail.com>
> ---
> fs/cifs/cifsencrypt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/cifs/cifsencrypt.c b/fs/cifs/cifsencrypt.c
> index afa09fc..e682b36 100644
> --- a/fs/cifs/cifsencrypt.c
> +++ b/fs/cifs/cifsencrypt.c
> @@ -714,7 +714,7 @@ setup_ntlmv2_rsp(struct cifs_ses *ses, const struct nls_table *nls_cp)
>
> ses->auth_key.response = kmalloc(baselen + tilen, GFP_KERNEL);
> if (!ses->auth_key.response) {
> - rc = ENOMEM;
> + rc = -ENOMEM;
> ses->auth_key.len = 0;
> goto setup_ntlmv2_rsp_ret;
> }
next prev parent reply other threads:[~2016-02-10 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 17:50 Anton Protopopov
2016-02-10 17:59 ` Joe Perches [this message]
2016-02-10 18:53 ` Anton Protopopov
2016-02-11 0:25 ` 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=1455127186.3333.44.camel@perches.com \
--to=joe@perches.com \
--cc=a.s.protopopov@gmail.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®