linux-kernel - RE: [EXT] Re: [PATCH 1/1] net: mvpp2: clear BM pool before initialization

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 for Android: free password hash cracker in your pocket

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

Message-ID: 
 <PH0PR18MB4543D125A30B59379B4EDF2DEC722@PH0PR18MB4543.namprd18.prod.outlook.com>
Date: Wed, 17 Jan 2024 03:55:13 +0000
From: "Jenishkumar Patel [C]" <jpatel2@...vell.com>
To: 'Jakub Kicinski' <kuba@...nel.org>
CC: "marcin.s.wojtas@...il.com" <marcin.s.wojtas@...il.com>,
        "linux@...linux.org.uk" <linux@...linux.org.uk>,
        "davem@...emloft.net"
	<davem@...emloft.net>,
        "edumazet@...gle.com" <edumazet@...gle.com>,
        "pabeni@...hat.com" <pabeni@...hat.com>,
        "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: RE: [EXT] Re: [PATCH 1/1] net: mvpp2: clear BM pool before
 initialization


-----Original Message-----
From: Jakub Kicinski <kuba@...nel.org> 
Sent: Tuesday, January 16, 2024 8:41 PM
To: Jenishkumar Patel [C] <jpatel2@...vell.com>
Cc: marcin.s.wojtas@...il.com; linux@...linux.org.uk; davem@...emloft.net; edumazet@...gle.com; pabeni@...hat.com; netdev@...r.kernel.org; linux-kernel@...r.kernel.org
Subject: [EXT] Re: [PATCH 1/1] net: mvpp2: clear BM pool before initialization

External Email

----------------------------------------------------------------------
On Mon, 15 Jan 2024 21:57:54 -0800 Jenishkumar Maheshbhai Patel wrote:
> Register value persisted after booting the kernel using kexec which 
> resulted in kernel panic. Thus cleared the BM pool registers before 
> initialisation to fix the issue.

s/persisted/persist/
s/resulted/results/
s/cleared/clear/

When you post v2 please add a Fixes tag -- it may be the first commit that added this driver if the issue has always been there.

I will make corrections and post it in v2.