On Tue, Sep 26, 2023 at 11:08:07PM +0100, Matthew Wilcox wrote: > Got this in linux-next 20230926, and I don't think it's due to my > patches on top (it may be, will verify): Confirmed not my patches; git bisect start # status: waiting for both good and bad commits # good: [6465e260f48790807eef06b583b38ca9789b6072] Linux 6.6-rc3 git bisect good 6465e260f48790807eef06b583b38ca9789b6072 # status: waiting for bad commit, 1 good commit known # bad: [4ae73bba62a367f2314f6ce69e3085a941983d8b] Add linux-next specific files for 20230926 git bisect bad 4ae73bba62a367f2314f6ce69e3085a941983d8b # good: [cc2f2a99c4be7c44a3441dd8f4b9e475d30800c3] Merge branch 'for-next' of https://evilpiepirate.org/git/bcachefs.git git bisect good cc2f2a99c4be7c44a3441dd8f4b9e475d30800c3 # good: [5a3bc5b9e4e9744f372692a88fd70750ee4851b3] Merge branch 'for-linux-next' of git://anongit.freedesktop.org/drm/drm-misc git bisect good 5a3bc5b9e4e9744f372692a88fd70750ee4851b3 I'm going to sleep now instead of running the last 10 steps of the bisect. If nobody's found this when I wake up, I'll finish it then. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
