[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANp29Y7cBbk8AbLq1z7w_PjQ-2fzG9FNyWyH+aH4oG9hfEm6nw@mail.gmail.com>
Date: Sat, 24 Sep 2022 14:03:05 +0200
From: Aleksandr Nogikh <nogikh@...gle.com>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: Randy Dunlap <rdunlap@...radead.org>,
Konstantin Komarov <almaz.alexandrovich@...agon-software.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Namjae Jeon <linkinjeon@...nel.org>,
Shigeru Yoshida <syoshida@...hat.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
syzbot <syzbot+1631f09646bc214d2e76@...kaller.appspotmail.com>,
"'Aleksandr Nogikh' via syzkaller-bugs"
<syzkaller-bugs@...glegroups.com>, ntfs3@...ts.linux.dev,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fs/ntfs3: fix negative shift size in true_sectors_per_clst()
> > By the way, a possible improvement on "Patch testing requests:" table.
> > Although the "Patch" link showing diff output after applying proposed patch is OK,
> > I'd like to also see a link to original "#syz test:" mail, for the intent of diff
> > (which would be in patch description part if it was a formal patch) is dropped from
> > diff output in the "Patch" link.
>
> Interesting!
> I created an issue to keep track of this:
> https://github.com/google/syzkaller/issues/3392
> The presence of the link will, though, depend on whether the user did
> Cc some public mailing lists while making the patch testing request.
Upd from Dmitry:
https://github.com/google/syzkaller/issues/3392#issuecomment-1256952263
We actually do provide these links, but they're rarely present for the
reason I mentioned above.
Powered by blists - more mailing lists