netdev - Re: [PATCH net v4 1/1] mlxbf_gige: Fix kernel panic at shutdown

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]

Date: Sat, 22 Jul 2023 02:29:07 +0300
From: Vladimir Oltean <olteanv@...il.com>
To: Asmaa Mnebhi <asmaa@...dia.com>
Cc: "davem@...emloft.net" <davem@...emloft.net>,
	"edumazet@...gle.com" <edumazet@...gle.com>,
	"kuba@...nel.org" <kuba@...nel.org>,
	"pabeni@...hat.com" <pabeni@...hat.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"sridhar.samudrala@...el.com" <sridhar.samudrala@...el.com>,
	"maciej.fijalkowski@...el.com" <maciej.fijalkowski@...el.com>,
	David Thompson <davthompson@...dia.com>
Subject: Re: [PATCH net v4 1/1] mlxbf_gige: Fix kernel panic at shutdown

On Fri, Jul 21, 2023 at 11:27:10PM +0000, Asmaa Mnebhi wrote:
> > > [  285.126250] mlxbf_gige MLNXBF17:00: shutdown [  285.130669] Unable
> > > to handle kernel NULL pointer dereference at virtual address
> > > 0000000000000070 [  285.139447] Mem abort info:
> > > [  285.142228]   ESR = 0x0000000096000004
> > > [  285.145964]   EC = 0x25: DABT (current EL), IL = 32 bits
> > > [  285.151261]   SET = 0, FnV = 0
> > > [  285.154303]   EA = 0, S1PTW = 0
> > > [  285.157430]   FSC = 0x04: level 0 translation fault
> > > [  285.162293] Data abort info:
> > > [  285.165159]   ISV = 0, ISS = 0x00000004
> > > [  285.168980]   CM = 0, WnR = 0
> > > [  285.171932] user pgtable: 4k pages, 48-bit VAs,
> > > pgdp=000000011d373000 [  285.178358] [0000000000000070]
> > > pgd=0000000000000000, p4d=0000000000000000 [  285.185134] Internal
> > > error: Oops: 96000004 [#1] SMP
> > 
> > That is not a stack trace. The stack trace is what appears between the lines "Call
> > trace:" and "---[ end trace 0000000000000000 ]---", and it is missing from what
> > you've posted.
> > 
> > It would be nice if you could also post-process the stack trace you get through
> > the command below (run in a kernel tree):
> > 
> > cat stack_trace | scripts/decode_stacktrace.sh path/to/vmlinux .
> > 
> > so that we could see the actual C code line numbers, and not just the offsets
> > within your particular binary image.
> 
> Hi Vladimir,
> 
> Do you want me to just send it as a reply or send a v5 and add it to the commit message?

As a reply, for now, please. I haven't requested any changes to the patch.