https://bugzilla.kernel.org/show_bug.cgi?id=219198 --- Comment #9 from Markus Rathgeb (maggu2810@xxxxxxxxx) --- Does a git bisect help you to identify the problematic change(s) I am currently in the progress... $ git bisect log git bisect start # status: waiting for both good and bad commits # bad: [8400291e289ee6b2bf9779ff1c83a291501f017b] Linux 6.11-rc1 git bisect bad 8400291e289ee6b2bf9779ff1c83a291501f017b # status: waiting for good commit(s), bad commit known # good: [7ba498d9d1bb67bcbc2a79f19a9054cdc8b95098] Linux 6.10.6 git bisect good 7ba498d9d1bb67bcbc2a79f19a9054cdc8b95098 # good: [0c3836482481200ead7b416ca80c68a29cfdaabd] Linux 6.10 git bisect good 0c3836482481200ead7b416ca80c68a29cfdaabd # good: [280e36f0d5b997173d014c07484c03a7f7750668] nsfs: use cleanup guard git bisect good 280e36f0d5b997173d014c07484c03a7f7750668 But if you already know what related changes has been done, I could cancel it. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
