netdev - Re: [PATCH net-next v3] net: wwan: t7xx: fix GFP_KERNEL usage in spin

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220520172556.1d62b899@kernel.org>
Date:   Fri, 20 May 2022 17:25:56 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Loic Poulain <loic.poulain@...aro.org>
Cc:     Ziyang Xuan <william.xuanziyang@...wei.com>,
        chandrashekar.devegowda@...el.com, linuxwwan@...el.com,
        chiranjeevi.rapolu@...ux.intel.com, haijun.liu@...iatek.com,
        m.chetan.kumar@...ux.intel.com, ricardo.martinez@...ux.intel.com,
        ryazanov.s.a@...il.com, johannes@...solutions.net,
        davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3] net: wwan: t7xx: fix GFP_KERNEL usage in
 spin_lock context

On Thu, 19 May 2022 09:29:12 +0200 Loic Poulain wrote:
> On Thu, 19 May 2022 at 09:26, Ziyang Xuan <william.xuanziyang@...wei.com> wrote:
> >
> > t7xx_cldma_clear_rxq() call t7xx_cldma_alloc_and_map_skb() in spin_lock
> > context, But __dev_alloc_skb() in t7xx_cldma_alloc_and_map_skb() uses
> > GFP_KERNEL, that will introduce scheduling factor in spin_lock context.
> >
> > Because t7xx_cldma_clear_rxq() is called after stopping CLDMA, so we can
> > remove the spin_lock from t7xx_cldma_clear_rxq().
> >
> > Fixes: 39d439047f1d ("net: wwan: t7xx: Add control DMA interface")
> > Suggested-by: Ricardo Martinez <ricardo.martinez@...ux.intel.com>
> > Signed-off-by: Ziyang Xuan <william.xuanziyang@...wei.com>  
> 
> Reviewed-by: Loic Poulain <loic.poulain@...aro.org>

Wait, you reviewed two different fixes for the same issue?
Please say something when that happens I thought both are needed :/