[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<CY4PR1801MB1911912084C9C9F451207F7DD3E6A@CY4PR1801MB1911.namprd18.prod.outlook.com>
Date: Wed, 30 Aug 2023 07:14:41 +0000
From: Ratheesh Kannoth <rkannoth@...vell.com>
To: Jesper Dangaard Brouer <hawk@...nel.org>,
Sebastian Andrzej Siewior
<bigeasy@...utronix.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "David S. Miller" <davem@...emloft.net>,
Eric Dumazet
<edumazet@...gle.com>,
Geethasowjanya Akula <gakula@...vell.com>,
Ilias
Apalodimas <ilias.apalodimas@...aro.org>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Subbaraya Sundeep Bhatta
<sbhatta@...vell.com>,
Sunil Kovvuri Goutham <sgoutham@...vell.com>,
Thomas
Gleixner <tglx@...utronix.de>,
Hariprasad Kelam <hkelam@...vell.com>,
Alexander Lobakin <aleksander.lobakin@...el.com>,
Qingfang DENG
<qingfang.deng@...lower.com.cn>
Subject: RE: [EXT] Re: [BUG] Possible unsafe page_pool usage in octeontx2
> From: Jesper Dangaard Brouer <hawk@...nel.org>
> Subject: [EXT] Re: [BUG] Possible unsafe page_pool usage in octeontx2
>
> This WQ process is not allowed to use the page_pool_alloc() API this way
> (from a work-queue). The PP alloc-side API must only be used under NAPI
> protection. Thanks for spotting this Sebastian!
>
> Will/can any of the Cc'ed Marvell people work on a fix?
We are working on it.
Powered by blists - more mailing lists