linux-kernel - Re: [PATCH] usb: dwc2: fix panic for coherent memory allocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170107094207.GC29727@leoy-linaro>
Date:   Sat, 7 Jan 2017 17:42:07 +0800
From:   Leo Yan <leo.yan@...aro.org>
To:     John Stultz <john.stultz@...aro.org>
Cc:     John Youn <johnyoun@...opsys.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux USB List <linux-usb@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>,
        Zhangfei Gao <zhangfei.gao@...aro.org>
Subject: Re: [PATCH] usb: dwc2: fix panic for coherent memory allocation

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@...aro.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