From: Greg KH <greg@kroah.com>
To: Juergen Gross <jgross@suse.com>
Cc: stable@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/blkfront: fix bug in backported patch
Date: Thu, 23 Dec 2021 11:57:57 +0100 [thread overview]
Message-ID: <YcRWNWtraLXt9W8v@kroah.com> (raw)
In-Reply-To: <20211223105308.17077-1-jgross@suse.com>
On Thu, Dec 23, 2021 at 11:53:08AM +0100, Juergen Gross wrote:
> The backport of commit 8f5a695d99000fc ("xen/blkfront: don't take local
> copy of a request from the ring page") to stable 4.4 kernel introduced
> a bug when adding the needed blkif_ring_get_request() function, as
> info->ring.req_prod_pvt was incremented twice now.
>
> Fix that be deleting the now superfluous increments after calling that
> function.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> drivers/block/xen-blkfront.c | 4 ----
> 1 file changed, 4 deletions(-)
So this is only needed in 4.4.y? No other backports were incorrect?
thanks,
greg k-h
next prev parent reply other threads:[~2021-12-23 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 10:53 [PATCH] xen/blkfront: fix bug in backported patch Juergen Gross
2021-12-23 10:57 ` Greg KH [this message]
2021-12-23 13:40 ` Juergen Gross
2021-12-27 12:43 ` Greg KH
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=YcRWNWtraLXt9W8v@kroah.com \
--to=greg@kroah.com \
--cc=jgross@suse.com \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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