From: Christian Brauner <brauner@kernel.org>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: sforshee@kernel.org, linux-fsdevel@vger.kernel.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
lennart@poettering.net
Subject: Re: 6.15-rc1/regression/bisected - commit 474f7825d533 is broke systemd-nspawn on my system
Date: Tue, 8 Apr 2025 11:18:50 +0200 [thread overview]
Message-ID: <20250408-vorher-karnickel-330646f410bd@brauner> (raw)
In-Reply-To: <CABXGCsPzb3KzJQph_PCg6N7526FEMqtidejNRZ0heF6Mv2xwdA@mail.gmail.com>
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@kernel.org> 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(-)
next prev parent reply other threads:[~2025-04-08 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 7:14 Mikhail Gavrilov
2025-04-07 14:15 ` Christian Brauner
2025-04-07 14:34 ` Mikhail Gavrilov
2025-04-08 8:23 ` Christian Brauner
2025-04-08 8:50 ` Mikhail Gavrilov
2025-04-08 9:18 ` Christian Brauner [this message]
2025-04-08 9:34 ` Mikhail Gavrilov
2025-04-08 10:21 ` Christian Brauner
2025-04-08 13:05 ` Mikhail Gavrilov
2025-04-09 8:36 ` Christian Brauner
2025-04-09 14:29 ` Mikhail Gavrilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250408-vorher-karnickel-330646f410bd@brauner \
--to=brauner@kernel.org \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=sforshee@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®