All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+da4f9f61f96525c62cc7@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] possible deadlock in seq_read_iter (2)
Date: Sun, 28 Jan 2024 00:24:03 -0800	[thread overview]
Message-ID: <0000000000007b3188060ffd4061@google.com> (raw)
In-Reply-To: <20240128075340.1015-1-hdanton@sina.com>

Hello,

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

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

Tested on:

commit:         8a696a29 Merge tag 'platform-drivers-x86-v6.8-2' of gi..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1516855fe80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5057c9bffe24fc70
dashboard link: https://syzkaller.appspot.com/bug?extid=da4f9f61f96525c62cc7
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:[~2024-01-28  8:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 13:17 [syzbot] [overlayfs?] possible deadlock in seq_read_iter (2) syzbot
2023-12-19 19:43 ` syzbot
2024-01-27 11:46   ` Hillf Danton
2024-01-27 11:57     ` syzbot
2024-01-28 21:43     ` Al Viro
2024-01-29  5:07       ` Hillf Danton
2024-01-28  7:53   ` Hillf Danton
2024-01-28  8:24     ` syzbot [this message]
2023-12-20  0:30 ` syzbot
2023-12-20  3:53   ` Amir Goldstein
2023-12-20  4:13     ` syzbot
2024-01-27  2:28 ` syzbot
2024-01-28 10:11   ` Amir Goldstein

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=0000000000007b3188060ffd4061@google.com \
    --to=syzbot+da4f9f61f96525c62cc7@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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 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.