From: Amir Goldstein <amir73il@gmail.com>
To: syzbot <syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com>
Cc: hdanton@sina.com, linux-fsdevel@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, mszeredi@redhat.com,
syzbot@syzkalhler.appspotmail.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
zohar@linux.ibm.com, zohar@us.ibm.com
Subject: Re: [syzbot] [integrity] [overlayfs] possible deadlock in mnt_want_write (2)
Date: Thu, 5 Oct 2023 13:26:06 +0300 [thread overview]
Message-ID: <CAOQ4uxjw_XztGxrhR9LWtz_SszdURkM+Add2q8A9BAt0z901kA@mail.gmail.com> (raw)
In-Reply-To: <0000000000001081fc0606f52ed9@google.com>
On Thu, Oct 5, 2023 at 12:59 PM syzbot
<syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot tried to test the proposed patch but the build/boot failed:
My mistake. Please try again:
#syz test: https://github.com/amir73il/linux ima-ovl-fix
next prev parent reply other threads:[~2023-10-05 14:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000067d24205c4d0e599@google.com>
2021-07-19 15:11 ` [syzbot] possible deadlock in mnt_want_write (2) Miklos Szeredi
2021-07-22 13:50 ` Mimi Zohar
2022-07-02 17:27 ` syzbot
2022-07-05 12:53 ` Mimi Zohar
[not found] ` <20220706121038.2045-1-hdanton@sina.com>
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 [this message]
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
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=CAOQ4uxjw_XztGxrhR9LWtz_SszdURkM+Add2q8A9BAt0z901kA@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=hdanton@sina.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
--cc=syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com \
--cc=syzbot@syzkalhler.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.ibm.com \
--cc=zohar@us.ibm.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;
as well as URLs for NNTP newsgroup(s).