netdev - Re: kernel BUG at net/core/skbuff.c:109!

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

Date:   Fri, 5 Feb 2021 19:07:00 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     "Tj (Elloe Linux)" <ml.linux@...oe.vision>
Cc:     netdev <netdev@...r.kernel.org>,
        Callum O'Connor <callum.oconnor@...oe.vision>
Subject: Re: kernel BUG at net/core/skbuff.c:109!

On Wed, 3 Feb 2021 11:55:25 +0000 Tj (Elloe Linux) wrote:
> On a recent build (5.10.0) we've seen several hard-to-pinpoint complete
> lock-ups requiring power-off restarts.
> 
> Today we found a small clue in the kernel log but unfortunately the
> complete backtrace wasn't captured (presumably system froze before log
> could be flushed) but I thought I should share it for investigation.
> 
> kernel BUG at net/core/skbuff.c:109!
> 
> kernel: skbuff: skb_under_panic: text:ffffffffc103c622 len:1228 put:48

text:ffffffffc103c622

That's a return address, IOW address of the caller, if I'm reading the
code right. Any chance you could decode that?
./scripts/decode_stack_trace is your friend.

> head:ffffa00202858000 data:ffffa00202857ff2 tail:0x4be end:0x6c0 dev:wlp4s0

dev:wlp4s0

Can you tell us what driver drives this device?

> kernel: ------------[ cut here ]------------
> kernel: kernel BUG at net/core/skbuff.c:109!