From: Leo Yan <leo.yan@linaro.org>
To: John Stultz <john.stultz@linaro.org>
Cc: John Youn <johnyoun@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux USB List <linux-usb@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>
Subject: Re: [PATCH] usb: dwc2: fix panic for coherent memory allocation
Date: Sat, 7 Jan 2017 17:42:07 +0800 [thread overview]
Message-ID: <20170107094207.GC29727@leoy-linaro> (raw)
In-Reply-To: <CALAqxLV4GcgavXw9WFieHVy0n9Gd86ZOv=yLaGTyiUZae58a0A@mail.gmail.com>
On Fri, Jan 06, 2017 at 01:36:11PM -0800, John Stultz wrote:
> On Thu, Jan 5, 2017 at 6:50 PM, Leo Yan <leo.yan@linaro.org> wrote:
> > When use configfs to configure USB port as as ethernet gadget, the
> > kernel has panic with below backtrace; it clearly indicates the
> > coherent memory allocation is happened in the interrupt context,
> > but the function __get_vm_area_node() is possible to be scheduling
> > out so function __get_vm_area_node() triggers panic if it's called
> > from interrupt context.
> >
> > To fix this issue, simply to change gfp_flag from GFP_KERNEL to
> > GFP_NOWAIT so it can support to allocate coherent memory from
> > interrupt context.
>
> This looks like it duplicates the similar patch I'm told should be
> queued for 4.10-rc3:
> https://lkml.org/lkml/2016/12/1/120
Yeah, this patch is duplicate. Please ignore this one.
Thanks,
Leo Yan
prev parent reply other threads:[~2017-01-07 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 2:50 [PATCH] usb: dwc2: fix panic for coherent memory allocation Leo Yan
2017-01-06 21:36 ` John Stultz
2017-01-07 9:42 ` Leo Yan [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=20170107094207.GC29727@leoy-linaro \
--to=leo.yan@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=johnyoun@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=zhangfei.gao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox