linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+011e4ea1da6692cf881c@syzkaller.appspotmail.com>
To: dhowells@redhat.com, jannh@google.com,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com,  viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] possible deadlock in pipe_write
Date: Fri, 24 Nov 2023 07:03:06 -0800	[thread overview]
Message-ID: <000000000000eebb5d060ae73f1e@google.com> (raw)
In-Reply-To: <CAG48ez3AazYzfJCFgu2MKSoxMEpJXz0td+rbeCOhsM38i78m3A@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+011e4ea1da6692cf881c@syzkaller.appspotmail.com

Tested on:

commit:         56c486e6 fs/pipe: Fix lockdep false-positive in watchq..
git tree:       https://github.com/thejh/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=128b880ce80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=1e6a76f6c7029ca2
dashboard link: https://syzkaller.appspot.com/bug?extid=011e4ea1da6692cf881c
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

      reply	other threads:[~2023-11-24 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21  2:34 [syzbot] possible deadlock in pipe_write syzbot
2022-03-21 14:41 ` Jann Horn
2022-03-21 16:03 ` David Howells
2022-03-21 16:17   ` Jann Horn
2023-11-24 14:38     ` Jann Horn
2023-11-24 15:03       ` syzbot [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=000000000000eebb5d060ae73f1e@google.com \
    --to=syzbot+011e4ea1da6692cf881c@syzkaller.appspotmail.com \
    --cc=dhowells@redhat.com \
    --cc=jannh@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).