linux-kernel - Re: [lkp-robot] [scsi, block] 0dba1314d4: WARNING:at_fs/sysfs/dir.c:#sysfs_warn

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: <CAPcyv4gE0+3pZQV=V75wxddFVhWeAz1abfJ=q8D1Zi+8Oi17rA@mail.gmail.com>
Date:   Sun, 5 Feb 2017 21:13:53 -0800
From:   Dan Williams <dan.j.williams@...el.com>
To:     Christoph Hellwig <hch@....de>
Cc:     kernel test robot <xiaolong.ye@...el.com>,
        Jens Axboe <axboe@...com>,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        Bart Van Assche <bart.vanassche@...disk.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        Jan Kara <jack@...e.cz>, Omar Sandoval <osandov@...ndov.com>,
        Omar Sandoval <osandov@...com>,
        LKML <linux-kernel@...r.kernel.org>,
        Jens Axboe <axboe@...nel.dk>, LKP <lkp@...org>
Subject: Re: [lkp-robot] [scsi, block] 0dba1314d4: WARNING:at_fs/sysfs/dir.c:#sysfs_warn_dup

On Sun, Feb 5, 2017 at 1:13 AM, Christoph Hellwig <hch@....de> wrote:
> Dan,
>
> can you please quote your emails?  I can't find any content inbetween
> all these quotes.

Sorry, I'm using gmail, but I'll switch to attaching the logs.

So with help from Xiaolong I was able to reproduce this, and it does
not appear to be a regression. We simply change the failure output of
an existing bug. Attached is a log of the same test on v4.10-rc7 (i.e.
without the recent block/scsi fixes), and it shows sda being
registered twice.

"[    6.647077] kobject (d5078ca4): tried to init an initialized
object, something is seriously wrong."

The change that "scsi, block: fix duplicate bdi name registration
crashes" makes is to properly try to register sdb since the sda devt
is still alive. However that's not a fix because we've managed to call
blk_register_queue() twice on the same queue.

View attachment "4.10-rc7.log" of type "text/x-log" (27843 bytes)