Bug#1049873: closing 1049873

From	Salvatore Bonaccorso <carnil@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#1049873: closing 1049873
Date	2025-02-14 06:50 +0100
Message-ID	<KfWKl-gF98-1@gated-at.bofh.it> (permalink)
References	(4 earlier) <KffP3-gbcj-1@gated-at.bofh.it> <H3nYC-2gmc-5@gated-at.bofh.it> <KfRB0-gBZz-1@gated-at.bofh.it> <H3nYC-2gmc-5@gated-at.bofh.it> <KfRB0-gBZz-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

On Fri, Feb 14, 2025 at 01:13:52AM +0100, Christoph Anton Mitterer wrote:
> On Wed, 2025-02-12 at 08:50 +0100, Salvatore Bonaccorso wrote:
> > Yes my undsetstanding from your comments was that 6.12.13-1 does not
> > expose the problem.
> 
> Okay... let me summarise :-)
> 
> - 6.12. doesn't show the original problem (hanging mv) described in
>   this bug
>   I briefly (and wrongly) thought, that instead the NFS4.1 mountpoint
>   would not update the file size after the mv succeeded, but that was
>   probably just a mistake on my side.
> - The bookworm kernel *does* show the original problem (hanging mv).

Then after all my marking as fixed in 6.12.13-1 was actually okay, and
the BTS knows that the 6.1.y version was still unfixed.


> > I have reopened the bug, but I believe the only one who actually can
> > do something here is either you, and bisect the changes down to what
> > broke the behaviour, or someone else using dCache and having the
> > possiblity to do experiments on a dedicated note.
> > 
> > I would start bisecting first by debian kernel-image packages by
> > narring down more closely where the behaviour got introduced, then
> > from there the respective upstream stable series changes.
> > 
> > I hope this gives you enough guide already on how to proceed.
> 
> Hmm I guess that would rather be rather be quite a "waste" of time.
> I cannot really test this on our production system, so I'd need to set
> up a test system for bisecting.
> And I have anyway adapted my use cases of this already with a TODO to
> revert after upgrading to trixie.
> 
> My only idea was that we might just leave it open in case someone else
> stumbles over the symptom.
> 
> But perhaps it's indeed best to just close it as wontfix.
> 
> Sorry for the back and forth :-)

No problem, but given that yes I will close it with the known version
fixing the problem and then let the bug go :)

Regards,
Salvatore

Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#1049873: closing 1049873 Christoph Anton Mitterer <calestyo@scientia.org> - 2025-02-11 23:00 +0100
  Bug#1049873: closing 1049873 Salvatore Bonaccorso <carnil@debian.org> - 2025-02-12 09:00 +0100
    Bug#1049873: closing 1049873 Christoph Anton Mitterer <calestyo@scientia.org> - 2025-02-14 01:20 +0100
      Bug#1049873: closing 1049873 Salvatore Bonaccorso <carnil@debian.org> - 2025-02-14 06:50 +0100

csiph-web