From: Greg KH <gregkh@linuxfoundation.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: stable@vger.kernel.org, kuba@kernel.org,
simon.horman@corigine.com, joneslee@google.com,
oliver@neukum.org, davem@davemloft.net, bay@hackerdom.ru,
linux-usb@vger.kernel.org, netdev@vger.kernel.or,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][stable-4.{14,19}.y 0/3] net: cdc_ncm: Backport fixes
Date: Wed, 7 Jun 2023 20:15:17 +0200 [thread overview]
Message-ID: <2023060705-thimble-kebab-d563@gregkh> (raw)
In-Reply-To: <20230605122045.2455888-1-tudor.ambarus@linaro.org>
On Mon, Jun 05, 2023 at 12:20:42PM +0000, Tudor Ambarus wrote:
> Backport patches in order to fix the kernel bug reported at:
> Link: https://syzkaller.appspot.com/bug?extid=b982f1059506db48409d
>
> Alexander's patches are prerequisites for the last. I made sure there
> are no other fixes in torvalds/master for the prerequisite patches.
> Compile tested. Intended for stable/linux-4.{14,19}.y.
>
> Alexander Bersenev (2):
> cdc_ncm: Implement the 32-bit version of NCM Transfer Block
> cdc_ncm: Fix the build warning
>
> Tudor Ambarus (1):
> net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize
>
> drivers/net/usb/cdc_ncm.c | 435 ++++++++++++++++++++++++-------
> drivers/net/usb/huawei_cdc_ncm.c | 8 +-
> include/linux/usb/cdc_ncm.h | 15 +-
> 3 files changed, 355 insertions(+), 103 deletions(-)
>
> --
> 2.41.0.rc0.172.g3f132b7071-goog
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-06-07 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 12:20 [PATCH][stable-4.{14,19}.y 0/3] net: cdc_ncm: Backport fixes Tudor Ambarus
2023-06-05 12:20 ` [PATCH][stable-4.{14,19}.y 1/3] cdc_ncm: Implement the 32-bit version of NCM Transfer Block Tudor Ambarus
2023-06-05 12:20 ` [PATCH][stable-4.{14,19}.y 2/3] cdc_ncm: Fix the build warning Tudor Ambarus
2023-06-05 12:20 ` [PATCH][stable-4.{14,19}.y 3/3] net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize Tudor Ambarus
2023-06-07 18:15 ` Greg KH [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=2023060705-thimble-kebab-d563@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bay@hackerdom.ru \
--cc=davem@davemloft.net \
--cc=joneslee@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.or \
--cc=oliver@neukum.org \
--cc=simon.horman@corigine.com \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.