On Wed, Mar 13, 2019 at 09:24:21AM +0100, 'Dmitry Vyukov' via syzkaller-bugs wrote: > On Tue, Mar 12, 2019 at 11:50 PM Eric Biggers <ebiggers@xxxxxxxxxx> wrote: > > > > On Tue, Mar 12, 2019 at 09:33:44AM +0100, 'Dmitry Vyukov' via syzkaller-bugs wrote: > > > On Tue, Mar 12, 2019 at 7:25 AM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > > On Tue, 12 Mar 2019 07:08:38 +0100 Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > > > > > > > > > On Tue, Mar 12, 2019 at 12:37 AM Andrew Morton > > > > > <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > > > > > > On Mon, 11 Mar 2019 06:08:01 -0700 syzbot <syzbot+fa11f9da42b46cea3b4a@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > > > > > > > > syzbot has bisected this bug to: > > > > > > > > > > > > > > commit 29a4b8e275d1f10c51c7891362877ef6cffae9e7 > > > > > > > Author: Shakeel Butt <shakeelb@xxxxxxxxxx> > > > > > > > Date: Wed Jan 9 22:02:21 2019 +0000 > > > > > > > > > > > > > > memcg: schedule high reclaim for remote memcgs on high_work > > > > > > > > > > > > > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155bf5db200000 > > > > > > > start commit: 29a4b8e2 memcg: schedule high reclaim for remote memcgs on.. > > > > > > > git tree: linux-next > > > > > > > final crash: https://syzkaller.appspot.com/x/report.txt?x=175bf5db200000 > > > > > > > console output: https://syzkaller.appspot.com/x/log.txt?x=135bf5db200000 > > > > > > > kernel config: https://syzkaller.appspot.com/x/.config?x=611f89e5b6868db > > > > > > > dashboard link: https://syzkaller.appspot.com/bug?extid=fa11f9da42b46cea3b4a > > > > > > > userspace arch: amd64 > > > > > > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14259017400000 > > > > > > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141630a0c00000 > > > > > > > > > > > > > > Reported-by: syzbot+fa11f9da42b46cea3b4a@xxxxxxxxxxxxxxxxxxxxxxxxx > > > > > > > Fixes: 29a4b8e2 ("memcg: schedule high reclaim for remote memcgs on > > > > > > > high_work") > > > > > > > > > > > > The following patch > > > > > > memcg-schedule-high-reclaim-for-remote-memcgs-on-high_work-v3.patch > > > > > > might have fixed this. Was it applied? > > > > > > > > > > Hi Andrew, > > > > > > > > > > You mean if the patch was applied during the bisection? > > > > > No, it wasn't. Bisection is very specifically done on the same tree > > > > > where the bug was hit. There are already too many factors that make > > > > > the result flaky/wrong/inconclusive without changing the tree state. > > > > > Now, if syzbot would know about any pending fix for this bug, then it > > > > > would not do the bisection at all. But it have not seen any patch in > > > > > upstream/linux-next with the Reported-by tag, nor it received any syz > > > > > fix commands for this bugs. Should have been it aware of the fix? How? > > > > > > > > memcg-schedule-high-reclaim-for-remote-memcgs-on-high_work-v3.patch was > > > > added to linux-next on Jan 10. I take it that this bug was hit when > > > > testing the entire linux-next tree, so we can assume that > > > > memcg-schedule-high-reclaim-for-remote-memcgs-on-high_work-v3.patch > > > > does not fix it, correct? > > > > In which case, over to Shakeel! > > > > > > Jan 10 is exactly when this bug was reported: > > > https://groups.google.com/forum/#!msg/syzkaller-bugs/5YkhNUg2PFY/4-B5M7bDCAAJ > > > https://syzkaller.appspot.com/bug?extid=fa11f9da42b46cea3b4a > > > > > > We don't know if that patch fixed the bug or not because nobody tested > > > the reproducer with that patch. > > > > > > It seems that the problem here is that nobody associated the fix with > > > the bug report. So people looking at open bug reports will spend time > > > again and again debugging this just to find that this was fixed months > > > ago. syzbot also doesn't have a chance to realize that this is fixed > > > and bisection is not necessary anymore. It also won't confirm/disprove > > > that the fix actually fixes the bug because even if the crash will > > > continue to happen it will look like the old crash just continues to > > > happen, so nothing to notify about. > > > > > > Associating fixes with bug reports solves all these problems for > > > humans and bots. > > > > > > > I think syzbot needs to be more aggressive about invalidating old bug reports on > > linux-next, e.g. automatically invalidate linux-next bugs that no longer occur > > after a few weeks even if there is a reproducer. Patches get added, changed, > > and removed in linux-next every day. Bugs that syzbot runs into on linux-next > > are often obvious enough that they get reported by other people too, resulting > > in bugs being fixed or dropped without people ever seeing the syzbot report. > > How do you propose that people associate fixes with syzbot reports when they > > never saw the syzbot report in the first place? > > > > This is a problem on mainline too, of course. But we *know* it's a more severe > > problem on linux-next, and that a bug like this that only ever happened on > > linux-next and stopped happening 2 months ago, is much less likely to be > > relevant than a bug in mainline. Kernel developers don't have time to examine > > every single syzbot report so you need to help them out by reducing the noise. > > Please file an issue for this at https://github.com/google/syzkaller/issues I filed https://github.com/google/syzkaller/issues/1054 > > I also wonder how does this work for all other kernel bugs reports? > syzbot is not the only one reporting kernel bugs and we don't want to > invent new rules here. Well, I think you already know the answer to that. There's no unified bug tracking system for all kernel subsystems, so in the worst case bugs/features just get ignored until someone cares to bring it up again. I know you want to change that, but the larger problem is that there aren't enough people able and funded to do the work. For the kernel overall (some subsystems are better, OFC) there so many low-quality, duplicate, or irrelevant reports/requests that no one can keep up. That means maintainers have to focus on the highest priority reports/requests, such as the ones that are clearly relevant and get continued discussion, vs. some random problem someone had 2 years ago. Just putting stuff on a bug tracker does not magically make people work on it. I think the reality is that until people can actually be funded to immediately analyze every syzbot report, syzbot needs to be designed to help developers focus on the reports most likely to still be actual bugs. That means automatically closing bugs where the crash is no longer occurring, especially if it was on linux-next; and sending reminders if the crash is still occurring. > > Also note that what happens now may be not representative of what will > happen in a steady mode later. Now syzbot bisects old bugs accumulated > over 1+ year. Later if it reports a bug, it should bisect sooner. So > all of what happens in this bug report won't take place. > Sure, but I think there will continue to be syzbot reports that the relevant people either don't see, or don't have time or expertise to look into. This is especially true when the same bug is filed as many different bug reports. - Eric
