From: Jens Axboe <axboe@kernel.dk>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-block@vger.kernel.org, Jan Kara <jack@suse.cz>,
linux-scsi <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Bart Van Assche <bart.vanassche@sandisk.com>,
Omar Sandoval <osandov@osandov.com>,
Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH v3] scsi, block: fix duplicate bdi name registration crashes
Date: Thu, 2 Feb 2017 08:23:55 -0700 [thread overview]
Message-ID: <07c52003-cd32-ee02-1d73-64586de7e9eb@kernel.dk> (raw)
In-Reply-To: <f3671618-eab3-7597-eebb-f46fefbac12a@kernel.dk>
On 02/01/2017 03:43 PM, Jens Axboe wrote:
> On 02/01/2017 02:40 PM, Dan Williams wrote:
>> On Wed, Feb 1, 2017 at 2:35 PM, Jens Axboe <axboe@kernel.dk> wrote:
>>> On 02/01/2017 02:05 PM, Dan Williams wrote:
>>>> Warnings of the following form occur because scsi reuses a devt number
>>>> while the block layer still has it referenced as the name of the bdi
>>>> [1]:
>>>>
>>>> WARNING: CPU: 1 PID: 93 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80
>>>> sysfs: cannot create duplicate filename '/devices/virtual/bdi/8:192'
>>>> [..]
>>>> Call Trace:
>>>> dump_stack+0x86/0xc3
>>>> __warn+0xcb/0xf0
>>>> warn_slowpath_fmt+0x5f/0x80
>>>> ? kernfs_path_from_node+0x4f/0x60
>>>> sysfs_warn_dup+0x62/0x80
>>>> sysfs_create_dir_ns+0x77/0x90
>>>> kobject_add_internal+0xb2/0x350
>>>> kobject_add+0x75/0xd0
>>>> device_add+0x15a/0x650
>>>> device_create_groups_vargs+0xe0/0xf0
>>>> device_create_vargs+0x1c/0x20
>>>> bdi_register+0x90/0x240
>>>> ? lockdep_init_map+0x57/0x200
>>>> bdi_register_owner+0x36/0x60
>>>> device_add_disk+0x1bb/0x4e0
>>>> ? __pm_runtime_use_autosuspend+0x5c/0x70
>>>> sd_probe_async+0x10d/0x1c0
>>>> async_run_entry_fn+0x39/0x170
>>>>
>>>> This is a brute-force fix to pass the devt release information from
>>>> sd_probe() to the locations where we register the bdi,
>>>> device_add_disk(), and unregister the bdi, blk_cleanup_queue().
>>>>
>>>> Thanks to Omar for the quick reproducer script [2]. This patch survives
>>>> where an unmodified kernel fails in a few seconds.
>>>
>>> What is the patch against? Doesn't seem to apply cleanly for me on
>>> master, nor the 4.11 block tree.
>>>
>>
>> I built it on top of Jan's bdi fixes series [1]. I can rebase to
>> block/for-next, just let me know which patches you want to take first.
>>
>> [1]: http://marc.info/?l=linux-block&m=148586843819160&w=2
>
> Ah, no that's fine, we'll just pull Jan's stuff in first. Makes sense.
Both are now applied, thanks Dan.
--
Jens Axboe
next prev parent reply other threads:[~2017-02-02 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 22:05 [PATCH v3] scsi, block: fix duplicate bdi name registration crashes Dan Williams
2017-02-01 22:23 ` Bart Van Assche
2017-02-01 22:35 ` Jens Axboe
2017-02-01 22:40 ` Dan Williams
2017-02-01 22:43 ` Jens Axboe
2017-02-02 15:23 ` Jens Axboe [this message]
2017-02-02 8:14 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07c52003-cd32-ee02-1d73-64586de7e9eb@kernel.dk \
--to=axboe@kernel.dk \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bart.vanassche@sandisk.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=osandov@fb.com \
--cc=osandov@osandov.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).