On Tue, Apr 08, 2025 at 01:50:16PM +0500, Mikhail Gavrilov wrote: > On Tue, Apr 8, 2025 at 1:24 PM Christian Brauner <brauner@xxxxxxxxxx> wrote: > > > > I have a hard time seeing what that would caused by. I'll try to look > > into it but it's not a lot to go by and this just shows a hanging FUSE > > request which seems very unrelated to the change you point to. > > > > I could perform another bisect and identify the subsequent commit that > caused the issue if I could revert 474f7825d533. I'm confused why that's an issue: > git reset --hard 474f7825d5335798742b92f067e1d22365013107 HEAD is now at 474f7825d533 fs: add copy_mount_setattr() helper > git revert --no-edit 474f7825d5335798742b92f067e1d22365013107 [work.bisect e5673958d85c] Revert "fs: add copy_mount_setattr() helper" Date: Tue Apr 8 11:14:31 2025 +0200 1 file changed, 33 insertions(+), 40 deletions(-)
