From: Mimi Zohar <zohar@linux.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>,
syzbot <syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com>,
Hillf Danton <hdanton@sina.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: [syzbot] possible deadlock in mnt_want_write (2)
Date: Thu, 22 Jul 2021 09:50:06 -0400 [thread overview]
Message-ID: <decadc5869f3de0bc78f783703e5ca9286f42522.camel@linux.ibm.com> (raw)
In-Reply-To: <CAJfpegsYNcv+mEVpLBxVGSQhXr0Q_UnOUC1VkYuYB=xzRt+f-A@mail.gmail.com>
[CC'ing Hillf Danton <hdanton@sina.com>]
Hi Miklos,
On Mon, 2021-07-19 at 17:11 +0200, Miklos Szeredi wrote:
> [CC: linux-intergrity]
>
> On Tue, 15 Jun 2021 at 18:59, syzbot
> <syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit: 06af8679 coredump: Limit what can interrupt coredumps
> > git tree: upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=162f99afd00000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=547a5e42ca601229
> > dashboard link: https://syzkaller.appspot.com/bug?extid=b42fe626038981fb7bfa
> > compiler: Debian clang version 11.0.1-2
> >
> > Unfortunately, I don't have any reproducer for this issue yet.
There was a similar syzbot report and followup discussion [1].
According to Amir Goldstein, it's a false positive lockdep warning.
At this point we understand how to fix the problem, but are waiting for
a reproducer.
thanks,
Mimi
[1] Message-Id: <20210616090142.734-1-hdanton@sina.com>
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com
next prev parent reply other threads:[~2021-07-22 13:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 16:59 [syzbot] possible deadlock in mnt_want_write (2) syzbot
2021-07-19 15:11 ` Miklos Szeredi
2021-07-22 13:50 ` Mimi Zohar [this message]
2022-07-02 17:27 ` syzbot
2022-07-05 12:53 ` Mimi Zohar
2022-07-06 12:10 ` Hillf Danton
2022-07-06 22:24 ` Mimi Zohar
2023-06-06 9:12 ` Miklos Szeredi
2023-06-06 9:12 ` syzbot
2023-06-06 9:13 ` Miklos Szeredi
2023-10-04 16:45 ` [syzbot] [integrity] [overlayfs] " syzbot
2023-10-05 9:36 ` Amir Goldstein
2023-10-05 9:59 ` syzbot
2023-10-05 10:26 ` Amir Goldstein
2023-10-05 10:46 ` syzbot
2023-10-05 11:47 ` Mimi Zohar
2023-10-05 13:22 ` Amir Goldstein
2023-10-05 13:35 ` Mimi Zohar
[not found] <20220703013354.1025-1-hdanton@sina.com>
2022-07-03 6:42 ` [syzbot] " syzbot
[not found] <20220703070714.1237-1-hdanton@sina.com>
2022-07-03 7:40 ` syzbot
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=decadc5869f3de0bc78f783703e5ca9286f42522.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=hdanton@sina.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.