From: Bart Van Assche <bvanassche@acm.org>
To: syzbot <syzbot+e7624af9c1ef3b617512@syzkaller.appspotmail.com>,
axboe@kernel.dk, idryomov@gmail.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, sagi@grimberg.me,
snitzer@redhat.com, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, wgh@torlan.ru,
zkabelac@redhat.com
Subject: Re: INFO: task hung in blkdev_issue_flush (2)
Date: Tue, 2 Jul 2019 09:01:10 -0700 [thread overview]
Message-ID: <6a853698-6244-7c4e-77cd-73e4fd672376@acm.org> (raw)
In-Reply-To: <0000000000009c93d5058cb46073@google.com>
On 7/2/19 8:27 AM, syzbot wrote:
> Showing all locks held in the system:
> 1 lock held by khungtaskd/1043:
> #0: 00000000f7c610b3 (rcu_read_lock){....}, at:
> debug_show_all_locks+0x5f/0x27e kernel/locking/lockdep.c:5149
> 2 locks held by rsyslogd/8451:
> #0: 00000000dfc1566f (&f->f_pos_lock){+.+.}, at:
> __fdget_pos+0xee/0x110 fs/file.c:801
> #1: 0000000054220207 (&rq->lock){-.-.}, at: rq_lock
> kernel/sched/sched.h:1168 [inline]
> #1: 0000000054220207 (&rq->lock){-.-.}, at: __schedule+0x1f5/0x1560
> kernel/sched/core.c:3397
> 2 locks held by getty/8541:
> #0: 000000004ff543bd (&tty->ldisc_sem){++++}, at:
> ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
> #1: 000000002a3905f3 (&ldata->atomic_read_lock){+.+.}, at:
> n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
> 2 locks held by getty/8542:
> #0: 000000006e67fcec (&tty->ldisc_sem){++++}, at:
> ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
> #1: 00000000ee71e4f3 (&ldata->atomic_read_lock){+.+.}, at:
> n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
> 2 locks held by getty/8543:
> #0: 00000000bd0907a0 (&tty->ldisc_sem){++++}, at:
> ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
> #1: 000000000876abce (&ldata->atomic_read_lock){+.+.}, at:
> n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
> 2 locks held by getty/8544:
> #0: 00000000710d6f7d (&tty->ldisc_sem){++++}, at:
> ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
> #1: 00000000af289586 (&ldata->atomic_read_lock){+.+.}, at:
> n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
> 2 locks held by getty/8545:
> #0: 000000003399e62d (&tty->ldisc_sem){++++}, at:
> ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
> #1: 00000000ee97f91a (&ldata->atomic_read_lock){+.+.}, at:
> n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
> 2 locks held by getty/8546:
> #0: 00000000ff2274c6 (&tty->ldisc_sem){++++}, at:
> ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
> #1: 00000000b96c5a9f (&ldata->atomic_read_lock){+.+.}, at:
> n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
> 2 locks held by getty/8547:
> #0: 000000005165f028 (&tty->ldisc_sem){++++}, at:
> ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:341
> #1: 00000000e89d5b4a (&ldata->atomic_read_lock){+.+.}, at:
> n_tty_read+0x232/0x1b70 drivers/tty/n_tty.c:2156
Since the tty layer does not call any block layer code, does this mean
that the root cause is in the tty code instead of in the block layer?
Bart.
prev parent reply other threads:[~2019-07-02 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 15:27 syzbot
2019-07-02 16:01 ` Bart Van Assche [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=6a853698-6244-7c4e-77cd-73e4fd672376@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=idryomov@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=snitzer@redhat.com \
--cc=syzbot+e7624af9c1ef3b617512@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=wgh@torlan.ru \
--cc=zkabelac@redhat.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
all inboxes | Powered by JetHome®