syzbot suspects this issue was fixed by commit:
commit b4a221ea8a1f890b50838ef389d016c7ff280abc
Author: Archie Pusaka
Date: Fri Jan 22 08:36:11 2021 +
Bluetooth: advmon offload MSFT add rssi support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14ef5ad6d0
start comm
Commit 36211f7fc1e7 ("Bluetooth: Pause service discovery for suspend")
seems like a bugfix as well but there is no Fixes tag there either. The
commit message should be more clear what the effect of the bug looks
like to the user. I like to write something like this:
[PATCH] Bluetooth: Pause serv
Sasha, do your stable patch picker scripts look at syzbot fix commands
to select patches to back port? In this case a bug was fixed while
adding a new feature. No one noticed the bug fix and there was no Fixes
tag.
On Sun, Jan 31, 2021 at 06:01:54PM +0800, Hillf Danton wrote:
> On Thu, 28 Jan 20
Hello,
syzbot found the following issue on:
HEAD commit:b491e6a7 net: lapb: Add locking to the lapb module
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=17ba0f2cd0
kernel config: https://syzkaller.appspot.com/x/.config?x=be33d8015c9de024
dashboard link: ht