From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "yuehaibing@huawei.com" <yuehaibing@huawei.com>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH net-next] SUNRPC: drop pointless static qualifier in xdr_get_next_encode_buffer()
Date: Thu, 8 Nov 2018 12:26:33 -0500 [thread overview]
Message-ID: <20181108172633.GD4947@fieldses.org> (raw)
In-Reply-To: <d23105929adb66c626d382525adef77265585404.camel@hammerspace.com>
On Thu, Nov 08, 2018 at 03:13:25AM +0000, Trond Myklebust wrote:
> On Thu, 2018-11-08 at 02:04 +0000, YueHaibing wrote:
> > There is no need to have the '__be32 *p' variable static since new
> > value
> > always be assigned before use it.
Applying for 4.20 and stable, thanks!
> >
> > Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> > ---
> > net/sunrpc/xdr.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/net/sunrpc/xdr.c b/net/sunrpc/xdr.c
> > index 2bbb8d3..d80b156 100644
> > --- a/net/sunrpc/xdr.c
> > +++ b/net/sunrpc/xdr.c
> > @@ -546,7 +546,7 @@ void xdr_commit_encode(struct xdr_stream *xdr)
> > 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;
> >
>
> Ouch, that's a really nasty bug that could definitely cause corruption
> if you have 2 threads simultaneously calling this function! This really
> deserves to be a stable patch.
Agreed. Looks like I introduced that in 3.16, over 5 years ago, so I'm
a little surprised not to have seen a bug report that this would
explain. Maybe it's just that the critical section is only a few lines
of arithemtic at the end of the function. Also it only gets called when
an xdr reply other than a read reaches the end of a page. So you'd need
a lot of concurrent READDIRs of large directories or something. Still,
I'd think it would be possible.....
> Thank you, YueHaibing!
>
> Bruce, do you want to shepherd this one in?
Yes, I've got 3 bugfixes queued up now, I should send them along later
today or tomorrow.
--b.
prev parent reply other threads:[~2018-11-08 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 2:04 [PATCH net-next] SUNRPC: drop pointless static qualifier in xdr_get_next_encode_buffer() YueHaibing
2018-11-08 3:13 ` Trond Myklebust
2018-11-08 17:26 ` bfields [this message]
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=20181108172633.GD4947@fieldses.org \
--to=bfields@fieldses.org \
--cc=anna.schumaker@netapp.com \
--cc=davem@davemloft.net \
--cc=jlayton@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trondmy@hammerspace.com \
--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