public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@redhat.com>
To: gregkh@linuxfoundation.org
Cc: yuehaibing@huawei.com, stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] SUNRPC: drop pointless static qualifier in" was seriously submitted to be applied to the 4.19-stable tree?
Date: Mon, 19 Nov 2018 12:03:28 -0500	[thread overview]
Message-ID: <20181119170327.GA3814@parsley.fieldses.org> (raw)
In-Reply-To: <154263151989125@kroah.com>

On Mon, Nov 19, 2018 at 01:45:19PM +0100, gregkh@linuxfoundation.org wrote:
> The patch below was submitted to be applied to the 4.19-stable tree.
> 
> I fail to see how this patch meets the stable kernel rules as found at
> Documentation/process/stable-kernel-rules.rst.

I should have rewritten that changelog, Yue Hainbing's makes it just
sound like cleanup.

That variable should definitely be private to each task, the sharing
could cause real bugs.

Admittedly, I don't have actual bug reports, so you could argue this
falls under the 'No "theoretical race condition"' rule, but the
potential consequences are pretty bad and the fix very simple, so I
still think it's a good stable candidate.

--b.

> I could be totally wrong, and if so, please respond to 
> <stable@vger.kernel.org> and let me know why this patch should be
> applied.  Otherwise, it is now dropped from my patch queues, never to be
> seen again.
> 
> thanks,
> 
> greg k-h
> 
> ------------------ original commit in Linus's tree ------------------
> 
> From 025911a5f4e36955498ed50806ad1b02f0f76288 Mon Sep 17 00:00:00 2001
> From: YueHaibing <yuehaibing@huawei.com>
> Date: Thu, 8 Nov 2018 02:04:57 +0000
> Subject: [PATCH] SUNRPC: drop pointless static qualifier in
>  xdr_get_next_encode_buffer()
> 
> There is no need to have the '__be32 *p' variable static since new value
> always be assigned before use it.
> 
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
> 
> diff --git a/net/sunrpc/xdr.c b/net/sunrpc/xdr.c
> index 5cfb9e0a18dc..f302c6eb8779 100644
> --- a/net/sunrpc/xdr.c
> +++ b/net/sunrpc/xdr.c
> @@ -546,7 +546,7 @@ EXPORT_SYMBOL_GPL(xdr_commit_encode);
>  static __be32 *xdr_get_next_encode_buffer(struct xdr_stream *xdr,
>  		size_t nbytes)
>  {
> -	static __be32 *p;
> +	__be32 *p;
>  	int space_left;
>  	int frag1bytes, frag2bytes;
>  
> 

  reply	other threads:[~2018-11-20  3:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 12:45 WTF: patch "[PATCH] SUNRPC: drop pointless static qualifier in" was seriously submitted to be applied to the 4.19-stable tree? gregkh
2018-11-19 17:03 ` J. Bruce Fields [this message]
2018-11-23 19:15   ` Sasha Levin

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=20181119170327.GA3814@parsley.fieldses.org \
    --to=bfields@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=yuehaibing@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