From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "axboe@fb.com" <axboe@fb.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: for-4.12/block branch
Date: Fri, 21 Apr 2017 16:40:52 +0000 [thread overview]
Message-ID: <1492792852.2550.7.camel@sandisk.com> (raw)
In-Reply-To: <b248fae1-c51f-be03-d27c-a9730b65132a@fb.com>
On Fri, 2017-04-21 at 10:33 -0600, Jens Axboe wrote:
> On 04/21/2017 10:31 AM, Bart Van Assche wrote:
> > On Fri, 2017-04-21 at 10:25 -0600, Jens Axboe wrote:
> > > On 04/21/2017 09:32 AM, Bart Van Assche wrote:
> > > > Hello Jens,
> > > >=20
> > > > Since yesterday the following complaint is reported frequently afte=
r having
> > > > installed the for-4.12/block branch on my test setup. Unless someon=
e has a
> > > > better proposal, I will run a bisect.
> > > >=20
> > > > BUG: sleeping function called from invalid context at ./include/lin=
ux/buffer_head.h:349
> > > > in_atomic(): 1, irqs_disabled(): 0, pid: 8019, name: find
> > > > CPU: 10 PID: 8019 Comm: find Tainted: G W I 4.11.0-rc4-d=
bg+ #2
> > > > Call Trace:
> > > > dump_stack+0x68/0x93
> > > > ___might_sleep+0x16e/0x230
> > > > __might_sleep+0x4a/0x80
> > > > __ext4_get_inode_loc+0x1e0/0x4e0
> > > > ext4_iget+0x70/0xbc0
> > > > ext4_iget_normal+0x2f/0x40
> > > > ext4_lookup+0xb6/0x1f0
> > > > lookup_slow+0x104/0x1e0
> > > > walk_component+0x19a/0x330
> > > > path_lookupat+0x4b/0x100
> > > > filename_lookup+0x9a/0x110
> > > > user_path_at_empty+0x36/0x40
> > > > vfs_statx+0x67/0xc0
> > > > SYSC_newfstatat+0x20/0x40
> > > > SyS_newfstatat+0xe/0x10
> > > > entry_SYSCALL_64_fastpath+0x18/0xad
> > >=20
> > > How are you reproducing this? I've been running testing on the test b=
ox
> > > and I run it on my laptop as well, but I haven't seen anything odd.
> >=20
> > Hello Jens,
> >=20
> > All I have to do to reproduce this is to build, install and boot the ke=
rnel.
> > Maybe we are using a different kernel config?
>=20
> I'd say odds are good we are not using an identical kernel config :-)
> What is your root device? Is it using mq and scheduling, or what's
> the config?
Hello Jens,
The boot device is a SATA disk:
# lsscsi
[0:0:0:0]=A0=A0=A0=A0disk=A0=A0=A0=A0ATA=A0=A0=A0=A0=A0=A0ST1000NM0033-9ZM =
GA67=A0=A0/dev/sda=A0
SCSI-mq is enabled and the default I/O scheduler is the deadline scheduler.
>From the kernel .config:
CONFIG_DEFAULT_IOSCHED=3D"deadline"
CONFIG_SCSI_MQ_DEFAULT=3Dy
The bisect I started earlier this morning is nearing completion - three ste=
ps
are left. These are the steps I performed so far:
$ git bisect log
git bisect start
# good: [c02ed2e75ef4c74e41e421acb4ef1494671585e8] Linux 4.11-rc4
git bisect good c02ed2e75ef4c74e41e421acb4ef1494671585e8
# bad: [95c55ff425faa190fd8ba55090fbdf33d8b2f0ae] mtip32xx: fix dereference=
of stack garbage
git bisect bad 95c55ff425faa190fd8ba55090fbdf33d8b2f0ae
# good: [65f619d2535197d97067eeeef75a40f25b552e69] Merge branch 'for-linus'=
into for-4.12/block
git bisect good 65f619d2535197d97067eeeef75a40f25b552e69
# good: [c074170e65995706be78e8c57ed2017c638d5464] block, bfq: add more fai=
rness with writes and slow processes
git bisect good c074170e65995706be78e8c57ed2017c638d5464
# good: [c7f014771b18e002fed373838fe14cf2065f3499] exofs: Convert to separa=
tely allocated bdi
git bisect good c7f014771b18e002fed373838fe14cf2065f3499
# good: [e0af413a45cbbf179a87fef0576882a8e6006244] dm rq: don't pass irrele=
vant error code to blk_mq_complete_request
git bisect good e0af413a45cbbf179a87fef0576882a8e6006244
Bart.=
next prev parent reply other threads:[~2017-04-21 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 15:32 for-4.12/block branch Bart Van Assche
2017-04-21 16:25 ` Jens Axboe
2017-04-21 16:31 ` Bart Van Assche
2017-04-21 16:33 ` Jens Axboe
2017-04-21 16:40 ` Bart Van Assche [this message]
2017-04-21 16:48 ` Jens Axboe
2017-04-21 16:56 ` Jens Axboe
2017-04-21 17:05 ` Bart Van Assche
2017-04-21 17:07 ` Jens Axboe
2017-04-21 17:12 ` Jens Axboe
2017-04-21 17:39 ` Bart Van Assche
2017-04-21 17:53 ` Jens Axboe
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=1492792852.2550.7.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@fb.com \
--cc=linux-block@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.