All of lore.kernel.org
 help / color / mirror / Atom feed
From: linyyuan@codeaurora.org
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, Linyu Yuan <linyyuan@codeaurora.com>
Subject: Re: [PATCH] usb: gadget: eem: fix wrong eem header operation
Date: Mon, 07 Jun 2021 10:27:08 +0800	[thread overview]
Message-ID: <440862cb6d6a2835cd4cd6f830baeaaf@codeaurora.org> (raw)
In-Reply-To: <YLoFayeoyqElpVSU@kroah.com>

On 2021-06-04 18:50, Greg KH wrote:
> On Thu, Jun 03, 2021 at 11:09:47PM +0800, Linyu Yuan wrote:
>> From: Linyu Yuan <linyyuan@codeaurora.com>
>> 
>> when skb_clone() or skb_copy_expand() fail,
> 
> How can these calls fail?  If they do, what is the overall system
> health?
indeed skb_copy_expand() fail on system when it have low continuous 
memory region
when using bigger MTU.
> 
>> it should pull skb with lengh indicated by header,
>> or not it will read network data and check it as header.
>> 
>> Signed-off-by: Linyu Yuan <linyyuan@codeaurora.com>
>> ---
>>  drivers/usb/gadget/function/f_eem.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> What commit does this fix?  Should it go to stable kernels?  If so, how
> far back?
this change can't avoid all system memory issue which cause skb failure,
but i help reduce driver parse wrong network data which may consume too 
much CPU time.

i will cc stable@vger.kernel.org on V2. i think it can apply to all 
active stable branch,
from 4.4 to 5.10.

> 
> And any reason you didn't use scripts/get_maintainer.pl for who to send
> your patch to?
thanks very much, i will follow your suggestion and provide a V2.
> 
> thanks,
> 
> greg k-h

      reply	other threads:[~2021-06-07  2:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 15:09 [PATCH] usb: gadget: eem: fix wrong eem header operation Linyu Yuan
2021-06-04 10:50 ` Greg KH
2021-06-07  2:27   ` linyyuan [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=440862cb6d6a2835cd4cd6f830baeaaf@codeaurora.org \
    --to=linyyuan@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linyyuan@codeaurora.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 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.