All of lore.kernel.org
 help / color / mirror / Atom feed
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: for-4.12/block branch
Date: Fri, 21 Apr 2017 15:32:27 +0000	[thread overview]
Message-ID: <1492788745.2550.1.camel@sandisk.com> (raw)

Hello Jens,

Since yesterday the following complaint is reported frequently after having
installed the for-4.12/block branch on my test setup. Unless someone has a
better proposal, I will run a bisect.

BUG: sleeping function called from invalid context at ./include/linux/buffe=
r_head.h:349
in_atomic(): 1, irqs_disabled(): 0, pid: 8019, name: find
CPU: 10 PID: 8019 Comm: find Tainted: G=A0=A0=A0=A0=A0=A0=A0=A0W I=A0=A0=A0=
=A0=A04.11.0-rc4-dbg+ #2
Call Trace:
=A0dump_stack+0x68/0x93
=A0___might_sleep+0x16e/0x230
=A0__might_sleep+0x4a/0x80
=A0__ext4_get_inode_loc+0x1e0/0x4e0
=A0ext4_iget+0x70/0xbc0
=A0ext4_iget_normal+0x2f/0x40
=A0ext4_lookup+0xb6/0x1f0
=A0lookup_slow+0x104/0x1e0
=A0walk_component+0x19a/0x330
=A0path_lookupat+0x4b/0x100
=A0filename_lookup+0x9a/0x110
=A0user_path_at_empty+0x36/0x40
=A0vfs_statx+0x67/0xc0
=A0SYSC_newfstatat+0x20/0x40
=A0SyS_newfstatat+0xe/0x10
=A0entry_SYSCALL_64_fastpath+0x18/0xad

Bart.=

             reply	other threads:[~2017-04-21 15:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 15:32 Bart Van Assche [this message]
2017-04-21 16:25 ` for-4.12/block branch 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
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=1492788745.2550.1.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.