On 9/14/21 11:09 AM, Greg Kroah-Hartman wrote:
On Tue, Sep 14, 2021 at 11:03:07AM -0700, Guenter Roeck wrote:
On Tue, Sep 14, 2021 at 06:15:25PM +0200, Greg Kroah-Hartman wrote:
On Tue, Sep 14, 2021 at 09:03:38AM -0700, Guenter Roeck wrote:
Hi,
I see the following crashes in v4.14.y-queue and v4.19.y-queue.
Please let me know if I need to bisect.
[ ... ]
Bisection would be great to track this down if at all possible.
Attached. Reverting the offending patch fixes the problem in both v4.14.y-queue
and v4.19.y-queue.
Guenter
---
# bad: [d73a5c7790019b70d9454ee9797c223198ad8ff0] Linux 4.14.247-rc1
# good: [f96eb53cbd76415edfba99c2cfa88567a885a428] Linux 4.14.246
git bisect start 'HEAD' 'v4.14.246'
# bad: [33a419b7cde2a3b8a0932319b6d54914717797f0] block: nbd: add sanity check for first_minor
git bisect bad 33a419b7cde2a3b8a0932319b6d54914717797f0
# good: [69f55eceb19466d9b20f926dbd16a4a0ad22ddbb] Revert "btrfs: compression: don't try to compress if we don't have enough pages"
git bisect good 69f55eceb19466d9b20f926dbd16a4a0ad22ddbb
# good: [f749b828e2bd070a33c3e8a1eda0e5e2de15ae81] power: supply: max17042_battery: fix typo in MAx17042_TOFF
git bisect good f749b828e2bd070a33c3e8a1eda0e5e2de15ae81
# good: [adccd339c64fbcd7098cf58a57acc3b7db3488d5] crypto: qat - fix naming for init/shutdown VF to PF notifications
git bisect good adccd339c64fbcd7098cf58a57acc3b7db3488d5
# good: [fe223807816e23234dc25460fabbe8957fec14e4] m68k: emu: Fix invalid free in nfeth_cleanup()
git bisect good fe223807816e23234dc25460fabbe8957fec14e4
# good: [17c695dab8970f9c7396bb7ccb25cc204b685f0b] spi: spi-pic32: Fix issue with uninitialized dma_slave_config
git bisect good 17c695dab8970f9c7396bb7ccb25cc204b685f0b
# good: [e2ff046bc5c21120d29085f33d3c56e3cf024ec3] clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock source channel
git bisect good e2ff046bc5c21120d29085f33d3c56e3cf024ec3
# first bad commit: [33a419b7cde2a3b8a0932319b6d54914717797f0] block: nbd: add sanity check for first_minor
Odd, but thanks for letting me know, I'll go drop this patch from 4.14.y
and 4.19.y queues.
This is not odd: the cleanup code in v4.14.y and v4.19.y is messed up after
this patch (the code was rearranged later). It looks like the new check
fails there for some reason, leaving a mess behind.
Guenter
