Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #82589 > unrolled thread

Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

Started byLuca Boccassi <bluca@debian.org>
First post2024-05-27 14:10 +0200
Last post2024-08-22 20:20 +0200
Articles 12 — 7 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Luca Boccassi <bluca@debian.org> - 2024-05-27 14:10 +0200
    Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Luca Boccassi <bluca@debian.org> - 2024-05-27 23:00 +0200
      Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Salvatore Bonaccorso <carnil@debian.org> - 2024-05-28 06:00 +0200
        Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Luca Boccassi <bluca@debian.org> - 2024-05-28 11:00 +0200
    Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Emanuele Rocca <ema@debian.org> - 2024-05-29 23:20 +0200
      Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Thorsten Leemhuis <regressions@leemhuis.info> - 2024-05-30 12:10 +0200
        Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Emanuele Rocca <ema@debian.org> - 2024-05-30 21:40 +0200
    Bug#1072004: Possible fix for 9p change breaking autopkgtest-build-qemu Luca Boccassi <bluca@debian.org> - 2024-06-16 18:20 +0200
    Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Tj <tj.iam.tj@proton.me> - 2024-07-14 18:40 +0200
    Processed: Re: linux: regression in the 9p protocol in 6.8 breaks  autopkgtest qemu jobs (affecting debci) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-08-14 21:10 +0200
    Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci) Ben Hutchings <ben@decadent.org.uk> - 2024-08-14 21:10 +0200
    Bug#1072004: marked as done (linux: regression in the 9p protocol  in 6.8 breaks autopkgtest qemu jobs (affecting debci)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-08-22 20:20 +0200

#82589 — Bug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

FromLuca Boccassi <bluca@debian.org>
Date2024-05-27 14:10 +0200
SubjectBug#1072004: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)
Message-ID<IIHkR-gbvS-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Source: linux
Version: 6.8.9-1
Severity: grave
Justification: breaks autopkgtest jobs running in qemu, breaking amd64 debci
X-Debbugs-CC: elbrus@debian.org, mjt@tls.msk.ru

Hi,

Kernel 6.8 includes this change:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80105ed2fd2715fb09a8fdb0655a8bdc86c120db

This has been bisected by Canonical and found to be breaking
qemu+autopkgtest. Tests just hang while waiting for input.

This is reliably reproducible, and has already started affecting debci
amd64 jobs in unstable, so filing with high severity to avoid
migration, that would break migration debci autopkgtest jobs. Example:

https://ci.debian.net/packages/s/systemd/unstable/amd64/47041978/

The launchpad ticket has more details:

https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461

-- 
Kind regards,
Luca Boccassi

[toc] | [next] | [standalone]


#82598

FromLuca Boccassi <bluca@debian.org>
Date2024-05-27 23:00 +0200
Message-ID<IIPBL-gghZ-3@gated-at.bofh.it>
In reply to#82589

[Multipart message — attachments visible in raw view] — view raw

On Mon, 27 May 2024 14:31:37 +0200 Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
> On 27.05.24 14:22, Luca Boccassi wrote:
> >> https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461
> > 
> > This has been reported upstream 3 weeks ago, but so far it seems no
> > action has been taken:
> > 
> > https://lore.kernel.org/all/Zj0ErxVBE3DYT2Ea@gpd/
> 
> Hmmm, that thread is strange, why are David's replies not where they
are
> supposed to be? Whatever. The last thing from just a few days ago
seems
> to be a inquiry from David to Andrea that was not yet answered
afaics:
> https://lore.kernel.org/all/531994.1716450257@warthog.procyon.org.uk/
> 
> Would also help a lot to know if this is a 6.8.y only thing, or
happens
> with 6.9 and mainline as well, as 6.8.y will likely be EOLed soon.

That's not available anywhere (in a usable form) so it's a question for
kernel maintainers.

Salvatore, what's the moreinfo for? Were you not able to reproduce it?
Just try to run any isolation-machine autopkgtest (eg: src:dpdk) in a
qem image (eg: built with autopkgtest-build-qemu) and compare unstable
vs testing.

-- 
Kind regards,
Luca Boccassi

[toc] | [prev] | [next] | [standalone]


#82600

FromSalvatore Bonaccorso <carnil@debian.org>
Date2024-05-28 06:00 +0200
Message-ID<IIWad-gkoL-1@gated-at.bofh.it>
In reply to#82598
Hi Luca,

On Mon, May 27, 2024 at 09:49:47PM +0100, Luca Boccassi wrote:
> On Mon, 27 May 2024 14:31:37 +0200 Thorsten Leemhuis
> <regressions@leemhuis.info> wrote:
> > On 27.05.24 14:22, Luca Boccassi wrote:
> > >> https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461
> > > 
> > > This has been reported upstream 3 weeks ago, but so far it seems no
> > > action has been taken:
> > > 
> > > https://lore.kernel.org/all/Zj0ErxVBE3DYT2Ea@gpd/
> > 
> > Hmmm, that thread is strange, why are David's replies not where they
> are
> > supposed to be? Whatever. The last thing from just a few days ago
> seems
> > to be a inquiry from David to Andrea that was not yet answered
> afaics:
> > https://lore.kernel.org/all/531994.1716450257@warthog.procyon.org.uk/
> > 
> > Would also help a lot to know if this is a 6.8.y only thing, or
> happens
> > with 6.9 and mainline as well, as 6.8.y will likely be EOLed soon.
> 
> That's not available anywhere (in a usable form) so it's a question for
> kernel maintainers.
> 
> Salvatore, what's the moreinfo for? Were you not able to reproduce it?
> Just try to run any isolation-machine autopkgtest (eg: src:dpdk) in a
> qem image (eg: built with autopkgtest-build-qemu) and compare unstable
> vs testing.

The aim for the moreinfo tag is to gather more information on which if
we know it's fixed with 6.9.y or mainline to have an idea why the
above thread might have stalled upstream.

I think I would ideally have first one 6.8.y version going to testing
and Diederik did work on rebasing already for 6.9.y, so we might move
then to that one with 6.8.y going EOL.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]


#82602

FromLuca Boccassi <bluca@debian.org>
Date2024-05-28 11:00 +0200
Message-ID<IJ0Qx-gngc-1@gated-at.bofh.it>
In reply to#82600
On Tue, 28 May 2024 at 04:47, Salvatore Bonaccorso <carnil@debian.org> wrote:
>
> Hi Luca,
>
> On Mon, May 27, 2024 at 09:49:47PM +0100, Luca Boccassi wrote:
> > On Mon, 27 May 2024 14:31:37 +0200 Thorsten Leemhuis
> > <regressions@leemhuis.info> wrote:
> > > On 27.05.24 14:22, Luca Boccassi wrote:
> > > >> https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461
> > > >
> > > > This has been reported upstream 3 weeks ago, but so far it seems no
> > > > action has been taken:
> > > >
> > > > https://lore.kernel.org/all/Zj0ErxVBE3DYT2Ea@gpd/
> > >
> > > Hmmm, that thread is strange, why are David's replies not where they
> > are
> > > supposed to be? Whatever. The last thing from just a few days ago
> > seems
> > > to be a inquiry from David to Andrea that was not yet answered
> > afaics:
> > > https://lore.kernel.org/all/531994.1716450257@warthog.procyon.org.uk/
> > >
> > > Would also help a lot to know if this is a 6.8.y only thing, or
> > happens
> > > with 6.9 and mainline as well, as 6.8.y will likely be EOLed soon.
> >
> > That's not available anywhere (in a usable form) so it's a question for
> > kernel maintainers.
> >
> > Salvatore, what's the moreinfo for? Were you not able to reproduce it?
> > Just try to run any isolation-machine autopkgtest (eg: src:dpdk) in a
> > qem image (eg: built with autopkgtest-build-qemu) and compare unstable
> > vs testing.
>
> The aim for the moreinfo tag is to gather more information on which if
> we know it's fixed with 6.9.y or mainline to have an idea why the
> above thread might have stalled upstream.
>
> I think I would ideally have first one 6.8.y version going to testing
> and Diederik did work on rebasing already for 6.9.y, so we might move
> then to that one with 6.8.y going EOL.

If 6.8 migrates to testing, it will break amd64 debci for unrelated
packages for migration tests too. I don't think that's something we
want? Paul, wouldn't that qualify as RC?

[toc] | [prev] | [next] | [standalone]


#82622

FromEmanuele Rocca <ema@debian.org>
Date2024-05-29 23:20 +0200
Message-ID<IJySe-gIyU-1@gated-at.bofh.it>
In reply to#82589
Hello Thorsten,

On 2024-05-27 02:31, Thorsten Leemhuis wrote:
> Would also help a lot to know if this is a 6.8.y only thing, or happens
> with 6.9 and mainline as well, as 6.8.y will likely be EOLed soon.

I could reproduce the issue with 6.9.2 too, will try mainline tomorrow.

FTR the procedure is quite simple. To build a sid qemu testbed:

 autopkgtest-build-qemu unstable /tmp/sid.img

Run the autopkgtest:

 autopkgtest -ddd -B dpdk -- autopkgtest-virt-qemu --debug --show-boot /tmp/sid.img

After a while the test hangs with:

 autopkgtest-virt-qemu: DBG: executing copydown /tmp/alog/tests-tree/ /tmp/autopkgtest.uG6tsJ/build.6QA/src/
 [...]
 autopkgtest-virt-qemu: DBG:  +>?

Then one can build a new kernel with:

 make oldconfig
 scripts/config --disable DEBUG_INFO
 scripts/config --disable DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT
 make -j`nproc` bindeb-pkg

Boot the QCOW image:

 qemu-system-x86_64 -cpu host -machine accel=kvm -drive file=sid.img,format=qcow2 -m 4G -smp `nproc`

Upgrade the kernel, and run the autopkgtest again as above.

  Emanuele

[toc] | [prev] | [next] | [standalone]


#82625

FromThorsten Leemhuis <regressions@leemhuis.info>
Date2024-05-30 12:10 +0200
Message-ID<IJKTn-gSdv-1@gated-at.bofh.it>
In reply to#82622
On 29.05.24 23:12, Emanuele Rocca wrote:
> On 2024-05-27 02:31, Thorsten Leemhuis wrote:
>> Would also help a lot to know if this is a 6.8.y only thing, or happens
>> with 6.9 and mainline as well, as 6.8.y will likely be EOLed soon.
> 
> I could reproduce the issue with 6.9.2 too, will try mainline tomorrow.

Good to know, thx!

> FTR the procedure is quite simple. [...]

Don't tell me (I'm just a man-in-the-middle for triaging here and not a
developer for that code), tell David in a reply to
https://lore.kernel.org/all/531994.1716450257@warthog.procyon.org.uk/ –
ideally while answering his question. He needs to know about this.

Ciao, Thorsten

[toc] | [prev] | [next] | [standalone]


#82630

FromEmanuele Rocca <ema@debian.org>
Date2024-05-30 21:40 +0200
Message-ID<IJTMZ-gXF5-3@gated-at.bofh.it>
In reply to#82625
Hi,

On 2024-05-30 12:00, Thorsten Leemhuis wrote:
> On 29.05.24 23:12, Emanuele Rocca wrote:
> > On 2024-05-27 02:31, Thorsten Leemhuis wrote:
> >> Would also help a lot to know if this is a 6.8.y only thing, or happens
> >> with 6.9 and mainline as well, as 6.8.y will likely be EOLed soon.
> > 
> > I could reproduce the issue with 6.9.2 too, will try mainline tomorrow.
> 
> Good to know, thx!

Mainline is affected too.

> > FTR the procedure is quite simple. [...]
> 
> Don't tell me (I'm just a man-in-the-middle for triaging here and not a
> developer for that code), tell David in a reply to
> https://lore.kernel.org/all/531994.1716450257@warthog.procyon.org.uk/ –
> ideally while answering his question. He needs to know about this.

Done.

[toc] | [prev] | [next] | [standalone]


#82732 — Bug#1072004: Possible fix for 9p change breaking autopkgtest-build-qemu

FromLuca Boccassi <bluca@debian.org>
Date2024-06-16 18:20 +0200
SubjectBug#1072004: Possible fix for 9p change breaking autopkgtest-build-qemu
Message-ID<IQ0LL-3nwF-7@gated-at.bofh.it>
In reply to#82589

[Multipart message — attachments visible in raw view] — view raw

On Sun, 16 Jun 2024 17:24:15 +0200 Christian Kastner <ckk@debian.org>
wrote:
> FYI, a contributor has submitted a patch to the kernel Bugzilla [1]
and
> it indeed fixed the issue for the packages where I was seeing this.
> 
> Let's hope it gets recognized and accepted soon.
> 
> Best,
> Christian
> 
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218916

By and large, kernel developers and maintainers just ignore
bugzilla.kernel.org, so if you have a fix, it would be better to just
send it to the appropriate mailing list, cc'ing the maintainer.
Otherwise it's unlikely anything will happen.

-- 
Kind regards,
Luca Boccassi

[toc] | [prev] | [next] | [standalone]


#82988

FromTj <tj.iam.tj@proton.me>
Date2024-07-14 18:40 +0200
Message-ID<J0aqu-25NE-17@gated-at.bofh.it>
In reply to#82589
Package: linux-image-6.9.7+debian+tj
Followup-For: Bug #1072004
X-Debbugs-Cc: tj.iam.tj@proton.me

I've completed 10 successful passes of the autopkgtest reproducer with the proposed
patch in the kernel bugzilla from Dominique Martinet on current
mainline, so with luck that might squeeze in to 6.10.

[toc] | [prev] | [next] | [standalone]


#83497 — Processed: Re: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-08-14 21:10 +0200
SubjectProcessed: Re: linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)
Message-ID<JbrxD-513f-1@gated-at.bofh.it>
In reply to#82589
Processing control commands:

> tag -1 - moreinfo
Bug #1072004 [src:linux] linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)
Removed tag(s) moreinfo.
> tag -1 fixed-upstream
Bug #1072004 [src:linux] linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)
Added tag(s) fixed-upstream.

-- 
1072004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072004
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#83498

FromBen Hutchings <ben@decadent.org.uk>
Date2024-08-14 21:10 +0200
Message-ID<JbrxD-513f-3@gated-at.bofh.it>
In reply to#82589

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 - moreinfo
Control: tag -1 fixed-upstream

This is claimed to be fixed upstream by:

commit e3786b29c54cdae3490b07180a54e2461f42144c
Author: Dominique Martinet <asmadeus@codewreck.org>
Date:   Thu Aug 8 14:29:38 2024 +0100

    9p: Fix DIO read through netfs

which is now in Linus's tree and will be part of 6.11-rc4.

Ben.

-- 
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.

[toc] | [prev] | [next] | [standalone]


#83622 — Bug#1072004: marked as done (linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci))

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-08-22 20:20 +0200
SubjectBug#1072004: marked as done (linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci))
Message-ID<JekzD-6Qf2-13@gated-at.bofh.it>
In reply to#82589

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 22 Aug 2024 18:07:00 +0000
with message-id <E1shCD6-001rdi-B4@fasolo.debian.org>
and subject line Bug#1072004: fixed in linux 6.11~rc4-1~exp1
has caused the Debian Bug report #1072004,
regarding linux: regression in the 9p protocol in 6.8 breaks autopkgtest qemu jobs (affecting debci)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1072004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072004
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web