All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "lpc.li" <lpc.li@huawei.com>
Cc: balbi@kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [usb gadget]use dev_kfree_skb_irq instead of dev_kfree_skb
Date: Fri, 22 Dec 2017 08:50:05 +0100	[thread overview]
Message-ID: <20171222075005.GA18229@kroah.com> (raw)
In-Reply-To: <bab52498-2656-390e-9a7f-f5f5d6ecd00e@huawei.com>

On Fri, Dec 22, 2017 at 03:43:15PM +0800, lpc.li wrote:
> Hi,
> Ethernet Gadget (with CDC Ethernet support) and RNDIS support, device
> is Hisilicon asic and host is PC Windows. Howerver, it has one
> warning. In the rndis_add_header of the file f_rndis.c,
> dev_kfree_skb_irq replaces dev_kfree_skb. And the waning is
> eliminated. I think we can't use dev_kfree_skb in irq disable context,
> because spin_lock_irqsave make sure we are always in irq disable
> context, use dev_kfree_skb_irq instead of dev_kfree_skb is better than
> dev_kfree_skb_any.

Can you make up a patch for this please?

> 
> #<--CO------------[ cut here ]------------
> WARNING: CPU: 0 PID: 22 at kernel/softirq.c:146 __local_bh_enable_ip+0x8c/0xb4()
> Modules linked in: g_ether usb_f_ecm usb_f_rndis u_ether libcomposite configfs udc_hisi hi_gpio(O) hifb(O) hi3559_tde(PO) hi3559_sys(PO) hi3559_base(PO) hi_osal(O) hi_ipcm(O)
> CPU: 0 PID: 22 Comm: kworker/0:1 Tainted: P O 3.18.20 #1

Note, 3.18 is _VERY_ old, are you sure this isn't resolved in a modern
and secure kernel release? :)

thanks,

greg k-h

       reply	other threads:[~2017-12-22  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bab52498-2656-390e-9a7f-f5f5d6ecd00e@huawei.com>
2017-12-22  7:50 ` Greg KH [this message]
2017-12-22  8:19   ` [usb gadget]use dev_kfree_skb_irq instead of dev_kfree_skb Lipengcheng

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=20171222075005.GA18229@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lpc.li@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 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.