Messages in this thread | | | Date | Fri, 23 Sep 2022 23:35:43 +0900 | Subject | Re: [PATCH] fs/ntfs3: fix negative shift size in true_sectors_per_clst() | From | Tetsuo Handa <> |
| |
On 2022/09/23 20:58, Aleksandr Nogikh wrote: > We do have plans to start inspecting LKML messages for the patches > that mention syzbot-reported bugs. It will be possible then to display > them all on the bug page and somehow mark bugs with a PATCH sent on > the list.
I interpret it as an attempt to automatically show "Patch proposed" state. But since not all patches have Reported-by: tag, and/or a proposed patch with Reported-by: tag might be withdrawn via review, that state should be also manually changeable.
> And then syzbot should just display all such received comments on the > bug's web page, right?
Whether "all comments" or "last comment" needs some decision. It might be a few words indicating culprit subsystem (probably "last" should overwrite), it might be memo describing how far debugging went (probably "all" is helpful), it might be some URL where discussions/patches are (probably "all" is helpful), it might be trying to show or hide "Patch proposed" state (probably "last" should overwrite).
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.
For example, https://syzkaller.appspot.com/bug?extid=9ca7a12fd736d93e0232 was forgotten for 1000 days after 7 patch testing requests. I can't easily find the intent of each diff (e.g. just debug printk() or proper fix). It seems the last one was about to formal submit, but I can't find why it is not yet applied.
| |