LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Martijn Coenen <maco@android.com>
To: Jan Kara <jack@suse.cz>
Cc: syzbot <syzbot+e38306788a2e7102a3b6@syzkaller.appspotmail.com>,
amir73il@gmail.com, Dan Carpenter <dan.carpenter@oracle.com>,
dwindsor@gmail.com, elena.reshetova@intel.com,
LKML <linux-kernel@vger.kernel.org>,
mszeredi@redhat.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: INFO: task hung in fsnotify_mark_destroy_workfn
Date: Tue, 24 Apr 2018 10:30:49 +0200 [thread overview]
Message-ID: <CAB0TPYGLW-bCRBTj--Y3xrgridzzR0V4Q+OCa6wv+yCi7RDaBA@mail.gmail.com> (raw)
In-Reply-To: <20180418093636.alasuzdjwjb2qovv@quack2.suse.cz>
On Wed, Apr 18, 2018 at 11:36 AM, Jan Kara <jack@suse.cz> wrote:
> OK, so we are waiting for the grace period on fsnotify_mark_srcu. Seems
> like someone is holding fsnotify_mark_srcu too long or srcu period cannot
> finish for some other reason. However the reproducer basically contains
> only one binder ioctl and I have no idea how that's connected with fsnotify
> in any way.
Yeah, binder isn't involved with fsnotify at all.
> So either the reproducer is wrong, or binder is corrupting
> memory and fsnotify is just a victim, or something like that...
>From the dumped stacks I don't see how binder is involved in that task
getting hung up, so either it's not related to binder after all, or it
is indeed some form of corruption, but then I wouldn't expect it to
reproduce in the same way every time (or otherwise expect KASAN to
catch it). I'll try to see if I can repro it locally.
Martijn
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
prev parent reply other threads:[~2018-04-24 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 1:02 syzbot
2018-04-18 7:30 ` Dan Carpenter
2018-04-18 9:36 ` Jan Kara
2018-04-19 15:42 ` Dmitry Vyukov
2018-04-24 8:30 ` Martijn Coenen [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=CAB0TPYGLW-bCRBTj--Y3xrgridzzR0V4Q+OCa6wv+yCi7RDaBA@mail.gmail.com \
--to=maco@android.com \
--cc=amir73il@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=dwindsor@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=syzbot+e38306788a2e7102a3b6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--subject='Re: INFO: task hung in fsnotify_mark_destroy_workfn' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).