From: Omar Sandoval <osandov@osandov.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Theodore Ts'o <tytso@mit.edu>, Omar Sandoval <osandov@fb.com>,
Andi Kleen <ak@linux.intel.com>,
linux-block@vger.kernel.org
Subject: Re: [REGRESSION] commit c2b3c170db610 causes blktests block/002 failure
Date: Thu, 27 Jun 2019 10:14:38 -0700 [thread overview]
Message-ID: <20190627171438.GA31481@vader> (raw)
In-Reply-To: <e84b29e1-209e-d598-0828-bed5e3b98093@acm.org>
On Tue, Jun 18, 2019 at 04:09:26PM -0700, Bart Van Assche wrote:
> On 6/9/19 11:14 AM, Theodore Ts'o wrote:
> > I recently noticed that block/002 from blktests started failing:
> >
> > root@kvm-xfstests:~# cd blktests/
> > root@kvm-xfstests:~/blktests# ./check block/002
> > block/002 (remove a device while running blktrace)
> > runtime ...
> > [ 12.598314] run blktests block/002 at 2019-06-09 13:09:00
> > [ 12.621298] scsi host0: scsi_debug: version 0188 [20190125]
> > [ 12.621298] dev_size_mb=8, opts=0x0, submit_queues=1, statistics=0
> > [ 12.625578] scsi 0:0:0:0: Direct-Access Linux scsi_debug 0188 PQ: 0 ANSI: 7
> > [ 12.627109] sd 0:0:0:0: Power-on or device reset occurred
> > [ 12.630322] sd 0:0:0:0: Attached scsi generic sg0 type 0
> > [ 12.634693] sd 0:0:0:0: [sda] 16384 512-byte logical blocks: (8.39 MB/8.00 MiB)
> > [ 12.638881] sd 0:0:0:0: [sda] Write Protect is off
> > [ 12.639464] sd 0:0:0:0: [sda] Mode Sense: 73 00 10 08
> > [ 12.646951] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
> > [ 12.658210] sd 0:0:0:0: [sda] Optimal transfer size 524288 bytes
> > [ 12.722771] sd 0:0:0:0: [sda] Attached SCSI disk
> > block/002 (remove a device while running blktrace) [failed]left
> > runtime ... 0.945s0: [sda] Synchronizing SCSI cache
> > --- tests/block/002.out 2019-05-27 13:52:17.000000000 -0400
> > +++ /root/blktests/results/nodev/block/002.out.bad 2019-06-09 13:09:01.034094065 -0400
> > @@ -1,2 +1,3 @@
> > Running block/002
> > +debugfs directory leaked
> > Test complete
> > root@kvm-xfstests:~/blktests#
> >
> > The git bisect log (see attached) pointed at this commit:
> >
> > commit c2b3c170db610896e4e633cba2135045333811c2 (HEAD, refs/bisect/bad)
> > Author: Andi Kleen <ak@linux.intel.com>
> > Date: Tue Mar 26 15:18:20 2019 -0700
> >
> > perf stat: Revert checks for duration_time
> > This reverts e864c5ca145e ("perf stat: Hide internal duration_time
> > counter") but doing it manually since the code has now moved to a
> > different file.
> > The next patch will properly implement duration_time as a full event, so
> > no need to hide it anymore.
> > Signed-off-by: Andi Kleen <ak@linux.intel.com>
> > Acked-by: Jiri Olsa <jolsa@kernel.org>
> > Link: http://lkml.kernel.org/r/20190326221823.11518-2-andi@firstfloor.org
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> >
> > Is this a known issue?
>
> Hi Ted,
>
> Test block/002 removes a SCSI device by writing into the "delete" sysfs
> attribute. As one can see in __scsi_remove_device() that triggers a
> synchronous call of blk_cleanup_queue(). The "debugfs directory leaked"
> message is reported if the request queue debugfs directory is found after
> SCSI device deletion has finished. Request queue debugfs directory deletion
> happens upon the final put of the request queue (see also
> __blk_release_queue()). I don't think that there is any guarantee that the
> debugfs directory disappears immediately after SCSI device deletion has
> finished. In other words, I think that this is a bug in test block/002.
> Omar, are you the author of that test script?
Hi, Bart, yes I wrote this test. I can reproduce the failure. I'll try
to find a reliable way to wait, otherwise I'll probably just toss a
sleep in here.
next prev parent reply other threads:[~2019-06-27 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 18:14 [REGRESSION] commit c2b3c170db610 causes blktests block/002 failure Theodore Ts'o
2019-06-18 23:09 ` Bart Van Assche
2019-06-27 17:14 ` Omar Sandoval [this message]
2019-06-28 16:20 ` Bart Van Assche
2019-06-27 20:24 ` Andi Kleen
2019-08-16 17:24 ` Andi Kleen
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=20190627171438.GA31481@vader \
--to=osandov@osandov.com \
--cc=ak@linux.intel.com \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.com \
--cc=tytso@mit.edu \
/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