linux-kernel - Re: [ata_port_detach] WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6613 ata_port

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]

Message-ID: <CAK8P3a321sP3H0CK4zC1=506NGaLCGcNN199St45GFUVWZp-nw@mail.gmail.com>
Date:   Tue, 21 Nov 2017 12:30:25 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Fengguang Wu <fengguang.wu@...el.com>
Cc:     Tejun Heo <tj@...nel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        IDE-ML <linux-ide@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        LKP <lkp@...org>
Subject: Re: [ata_port_detach] WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6613
 ata_port_detach+0x9b/0x180

On Tue, Nov 21, 2017 at 11:54 AM, Fengguang Wu <fengguang.wu@...el.com> wrote:
> Hello,
>
> FYI this happens in mainline kernel 4.14.0-12891-gc8a0739.
> It at least dates back to v4.11.
>
> It occurs in 4 out of 4 boots.

I see that this is the result of CONFIG_DEBUG_TEST_DRIVER_REMOVE=y,
which tries to remove the device immediately after probing.

The ATA_PFLAG_UNLOADED only gets set in ata_eh_unload(), it looks
like that never gets called when we unload while ATA_PFLAG_INITIALIZING
is still set during async probing.

      Arnd