On Tue, Oct 31, 2017 at 2:03 PM, Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > On Tue, Oct 31, 2017 at 3:45 PM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: >> Quoting syzbot (2017-10-27 09:09:50) >>> This bug is generated by a dumb bot. It may contain errors. >>> See https://goo.gl/tpsmEJ for details. >>> Direct all questions to syzkaller@xxxxxxxxxxxxxxxx. >>> >>> syzbot will keep track of this bug report. >>> Once a fix for this bug is committed, please reply to this email with: >>> #syz fix: exact-commit-title >>> To mark this as a duplicate of another syzbot report, please reply with: >>> #syz dup: exact-subject-of-another-report >>> If it's a one-off invalid bug report, please reply with: >>> #syz invalid >>> Note: if the crash happens again, it will cause creation of a new bug >>> report. >> >> Can we use >> >> Reported-by: syzbot <bot+8de19a03d6fdf256eb2b90ec48916b6f47b9b5a3@xxxxxxxxxxxxxxxxxxxxxxxxx> >> >> as a unique tag for tracking purposes? > > > Hi, > > Seems to be a common question. I've added the following to bug template: > > Please credit me with: Reported-by: syzbot <syzkaller@xxxxxxxxxxxxxxxx> > > will now be present on newly reported bugs: > > https://groups.google.com/forum/#!topic/syzkaller-bugs/XE8YSiSZDdA This was fixed by: #syz fix: drm: Require __GFP_NOFAIL for the legacy drm_modeset_lock_all Now we indeed can use: Reported-by: syzbot <bot+8de19a03d6fdf256eb2b90ec48916b6f47b9b5a3@xxxxxxxxxxxxxxxxxxxxxxxxx> which avoids the need to go back and manually attach fixing commit to the report like this. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
