linux-kernel - [BUG] kernel BUG at mm/slub.c

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

Message-ID: <1624640454.149631.1632987871186@office.mailbox.org>
Date:   Thu, 30 Sep 2021 09:44:31 +0200 (CEST)
From:   torvic9@...lbox.org
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "paolo.valente@...aro.org" <paolo.valente@...aro.org>,
        "axboe@...nel.dk" <axboe@...nel.dk>,
        "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>
Subject: [BUG] kernel BUG at mm/slub.c - possible BFQ issue?

Hello,

I encounter a hard freeze on both 5.14 and 5.15 when using BFQ.
Unfortunately, I do not have a full error log, because the computer
totally freezes and slightly corrupts the display, so it's
impossible to read the entire message.

However, what I could get is the following:

  kernel BUG at mm/slub.c:379
  invalid opcode: 0000 [#1]
  RIP: 0010:__slab_free
  [...]
  Call Trace:
  bfq_set_next_ioprio_data
  [...]
  bfq_put_queue
  bfq_insert_requests
  [...]

This issue appears more or less randomly and it sometimes takes a
little while to reproduce it (running fio helps).
The call trace always contains references to BFQ, but they are not
always the exact same. Once, I could see on the corrupted display
the message "general protection fault".
I could reproduce this issue on two computers.

Not quite sure but I *think* the issue first appeared somewhere around
5.14.5 or 5.14.6, during which time BFQ only got the following commit:

  (88013a0c5d99) block, bfq: honor already-setup queue merges

5.13 doesn't seem to be affected AFAICS.

Does anyone have an idea what is going on?
I will now revert the above commit and see if that helps...

Thanks,
Tor