On Thu, Jul 27, 2023 at 11:53:02AM -0700, syzbot wrote: > > On Tue, Jul 25, 2023 at 11:57:22PM -0700, syzbot wrote: > >> syzbot has bisected this issue to: > >> > >> commit a52f58b34afe095ebc5823684eb264404dad6f7b > >> Author: Matthew Wilcox (Oracle) <willy@xxxxxxxxxxxxx> > >> Date: Mon Jul 24 18:54:10 2023 +0000 > >> > >> mm: handle faults that merely update the accessed bit under the VMA lock > >> > >> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1783585ea80000 > >> start commit: [unknown] > >> git tree: linux-next > > > > #syz test linux-next a52f58b34afe095ebc5823684eb264404dad6f7b > > "linux-next" does not look like a valid git repo address. Well, now, that's your fault, isn't it? You're abbreviating the git tree in the report, but then refusing to accept the abbreviation in the response.
