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: <MWHPR1801MB191826BCB156AB7ADA1F6AF3D3EFA@MWHPR1801MB1918.namprd18.prod.outlook.com>
Date:   Wed, 6 Sep 2023 08:24:53 +0000
From:   Ratheesh Kannoth <rkannoth@...vell.com>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Sunil Kovvuri Goutham <sgoutham@...vell.com>,
        Geethasowjanya Akula <gakula@...vell.com>,
        Subbaraya Sundeep Bhatta <sbhatta@...vell.com>,
        Hariprasad Kelam <hkelam@...vell.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "edumazet@...gle.com" <edumazet@...gle.com>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "pabeni@...hat.com" <pabeni@...hat.com>,
        "hawk@...nel.org" <hawk@...nel.org>,
        "alexander.duyck@...il.com" <alexander.duyck@...il.com>,
        "ilias.apalodimas@...aro.org" <ilias.apalodimas@...aro.org>,
        "linyunsheng@...wei.com" <linyunsheng@...wei.com>
Subject: RE: [EXT] Re: [PATCH net v1] octeontx2-pf: Fix page pool cache index
 corruption.

> From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> Subject: [EXT] Re: [PATCH net v1] octeontx2-pf: Fix page pool cache index
> corruption.
> 
> > +	napi_schedule(wrk->napi);
> 
> This will delay NAPI until "some random point in the future" for instance if an
> interrupt on _this_ CPU fires. You only set the softirq state and never enforce
> it here. This works as intended if invoked from an IRQ but this here a worker/
> process context.
ACK.  Do we need to be so precise here ? Anyway we are short of rx buffers and want to schedule NAPI after some time 
(in delayed workqueue) to recheck on rx buffers.  Softirq state will be checked even on timer interrupt returns, right ?.  I was thinking 
Case - what will happen if workqueue never got a chance to run if system is stressed with interrupts. 
 
> You can either put local_bh_disable()/enable() around napi_schedule() or
> use it from a timer callback and skip the worker.
Switching to  a timer callback makes sense. 

-Ratheesh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ