From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] blk-mq: fix up placement of debugfs directory of queue files
Date: Sat, 6 Jul 2019 18:50:44 +0200 [thread overview]
Message-ID: <20190706165044.GA18886@kroah.com> (raw)
In-Reply-To: <a4e28385-6f87-05f5-edb2-d68446771b7c@kernel.dk>
On Sat, Jul 06, 2019 at 10:07:14AM -0600, Jens Axboe wrote:
> On 7/6/19 9:50 AM, Greg Kroah-Hartman wrote:
> > When the blk-mq debugfs file creation logic was "cleaned up" it was
> > cleaned up too much, causing the queue file to not be created in the
> > correct location. Turns out the check for the directory being present
> > is needed as if that has not happened yet, the files should not be
> > created, and the function will be called later on in the initialization
> > code so that the files can be created in the correct location.
>
> How about we shove this in for 5.2 final? Trivial enough to do, and it
> would suck to have 5.2 released with this.
Sure, no objection from me!
> Though not sure what devices this actually impacts, I haven't noticed
> anything awry on my setups?
I can easily trigger this with loop devices. I know Stephen reported
this and I don't know if that was the driver that caused it for him. I
have also seen this happen in syzbot boot logs already, but again, don't
know what block devices they are using that causes this.
thanks,
greg k-h
prev parent reply other threads:[~2019-07-06 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 15:50 [PATCH] blk-mq: fix up placement of debugfs directory of queue files Greg Kroah-Hartman
2019-07-06 16:07 ` Jens Axboe
2019-07-06 16:50 ` Greg Kroah-Hartman [this message]
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=20190706165044.GA18886@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.