Re: [PATCH] fs/ntfs3: fix negative shift size in true_sectors_per_clst()

Tetsuo Handa
2022-09-23T01:26:24Z

On 2022/09/23 9:38, Randy Dunlap wrote:
> I slightly prefer the earlier patch:
>
> https://lore.kernel.org/all/20220823144625.1627736-1-syoshida@redhat.com/
>
> but it appears that the NTFS3 maintainer is MIA again. :(
>

Shigeru Yoshida posted a patch against https://syzkaller.appspot.com/bug?extid=35b87c668935bb55e666
and I posted a patch against https://syzkaller.appspot.com/bug?extid=1631f09646bc214d2e76 .
We didn't realize that these are the same problem.

It seems that sending to not only syzbot+XXXXXXXXXXXXXXXXXXXX@syzkaller.appspotmail.com
but also syzkaller-bugs@googlegroups.com is required for proposed patches to be recorded
(in order to avoid duplicated works) into a page linked from "Status:" in each bug page.

Since https://syzkaller.appspot.com/upstream does not have a column for tracking intermediate
status between "Open" and "Fixed" (e.g. cause identified, patch proposed) because it can take
long time until patches are accepted into one of git trees syzbot is tracking, we need to
utilize "Last activity" in the list page and a page linked from "Status:" in each bug page.
Time to boost priority for implementing user-supplied comment column (e.g. "#syz memo:" command)
to each bug?