From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: gregkh@linuxfoundation.org
Cc: suwan.kim027@gmail.com, skhan@linuxfoundation.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] usbip: Fix receive error in vhci-hcd when using" failed to apply to 4.4-stable tree
Date: Sun, 29 Dec 2019 17:56:45 +0100 [thread overview]
Message-ID: <20191229165645.GG1292@mail-itl> (raw)
In-Reply-To: <157762916119642@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 2524 bytes --]
On Sun, Dec 29, 2019 at 03:19:21PM +0100, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 4.4-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
I think the bug this commit fixes (part of ea44d190764b commit) is not
present in 4.4, nor 4.9 branches.
In short: no need to backport it to 4.4 or 4.9 branch.
> thanks,
>
> greg k-h
>
> ------------------ original commit in Linus's tree ------------------
>
> From d986294ee55d719562b20aabe15a39bf8f863415 Mon Sep 17 00:00:00 2001
> From: Suwan Kim <suwan.kim027@gmail.com>
> Date: Fri, 13 Dec 2019 11:30:54 +0900
> Subject: [PATCH] usbip: Fix receive error in vhci-hcd when using
> scatter-gather
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> When vhci uses SG and receives data whose size is smaller than SG
> buffer size, it tries to receive more data even if it acutally
> receives all the data from the server. If then, it erroneously adds
> error event and triggers connection shutdown.
>
> vhci-hcd should check if it received all the data even if there are
> more SG entries left. So, check if it receivces all the data from
> the server in for_each_sg() loop.
>
> Fixes: ea44d190764b ("usbip: Implement SG support to vhci-hcd and stub driver")
> Reported-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> Tested-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> Signed-off-by: Suwan Kim <suwan.kim027@gmail.com>
> Acked-by: Shuah Khan <skhan@linuxfoundation.org>
> Cc: stable <stable@vger.kernel.org>
> Link: https://lore.kernel.org/r/20191213023055.19933-2-suwan.kim027@gmail.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> diff --git a/drivers/usb/usbip/usbip_common.c b/drivers/usb/usbip/usbip_common.c
> index 6532d68e8808..e4b96674c405 100644
> --- a/drivers/usb/usbip/usbip_common.c
> +++ b/drivers/usb/usbip/usbip_common.c
> @@ -727,6 +727,9 @@ int usbip_recv_xbuff(struct usbip_device *ud, struct urb *urb)
>
> copy -= recv;
> ret += recv;
> +
> + if (!copy)
> + break;
> }
>
> if (ret != size)
>
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-12-29 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 14:19 FAILED: patch "[PATCH] usbip: Fix receive error in vhci-hcd when using" failed to apply to 4.4-stable tree gregkh
2019-12-29 16:56 ` Marek Marczykowski-Górecki [this message]
2019-12-29 19:53 ` Shuah Khan
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=20191229165645.GG1292@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=gregkh@linuxfoundation.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=suwan.kim027@gmail.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