From: "Theodore Ts'o" <tytso@mit.edu>
To: syzbot <syzbot+62120febbd1ee3c3c860@syzkaller.appspotmail.com>
Cc: hdanton@sina.com, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] possible deadlock in ext4_xattr_get
Date: Mon, 8 Aug 2022 21:48:08 -0400 [thread overview]
Message-ID: <YvG82FfLA4iI0ZAT@mit.edu> (raw)
In-Reply-To: <00000000000017bd2d05e5c47f10@google.com>
On Mon, Aug 08, 2022 at 06:03:12PM -0700, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-and-tested-by: syzbot+62120febbd1ee3c3c860@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: cb71b93c Add linux-next specific files for 20220628
> git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> console output: https://syzkaller.appspot.com/x/log.txt?x=12afd10e080000
> kernel config: https://syzkaller.appspot.com/x/.config?x=badbc1adb2d582eb
> dashboard link: https://syzkaller.appspot.com/bug?extid=62120febbd1ee3c3c860
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> patch: https://syzkaller.appspot.com/x/patch.diff?x=104ed896080000
>
Hi Hillf,
Thanks for looking at this. For some reason, your e-mails with the
patch are available on the syzkaller-bugs google groups archive. For
example:
https://groups.google.com/g/syzkaller-bugs/c/NgC9hA3GX_Q/m/vVqsx8KTBQAJ
But even though your messages appear to be cc'ed to linux-kernel, I'm
not seeing your messages on lore.kernel.org's mail archives. (wWith
apologies to Lewis Caroll) "Curiouser and curiouser...."
This makes me worried that somehow some or all of your messages to
linux-ext4@ or linux-kernel@ on this matter are somehow getting lost.
We see syzkaller's reply to your messages, and anything that you've
cc'ed to syzkaller-bugs@googlegroups.com is available archived on
Google Groups. However, if there were any other messages that you
have sent, they may have been unseed by anyone else. :-(
If you could send a patch with a full description and the appropriate
Fixes: and CC: stable tags, could you make sure that you explicitly Cc
me, just in case something is funny going on with your e-mails to
mailing lists at vger.kernel.org?
Many thanks!
- Ted
next prev parent reply other threads:[~2022-08-09 1:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220808133219.2248-1-hdanton@sina.com>
2022-08-09 1:03 ` [syzbot] possible deadlock in ext4_xattr_get syzbot
2022-08-09 1:48 ` Theodore Ts'o [this message]
[not found] <20220808121037.2180-1-hdanton@sina.com>
2022-08-08 12:21 ` syzbot
[not found] <20220808111439.2119-1-hdanton@sina.com>
2022-08-08 11:26 ` syzbot
2022-08-07 13:08 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=YvG82FfLA4iI0ZAT@mit.edu \
--to=tytso@mit.edu \
--cc=hdanton@sina.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+62120febbd1ee3c3c860@syzkaller.appspotmail.com \
--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.