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


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

Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

Started byFlorian Lehner <dev@der-flo.net>
First post2023-03-25 16:10 +0100
Last post2023-06-07 21:40 +0200
Articles 4 — 3 participants

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+ Florian Lehner <dev@der-flo.net> - 2023-03-25 16:10 +0100
    Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+ Diederik de Haas <didi.debian@cknow.org> - 2023-03-25 17:10 +0100
      Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+ Florian Lehner <dev@der-flo.net> - 2023-06-05 21:10 +0200
        Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+ Salvatore Bonaccorso <carnil@debian.org> - 2023-06-07 21:40 +0200

#78595 — Bug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+

FromFlorian Lehner <dev@der-flo.net>
Date2023-03-25 16:10 +0100
SubjectBug#1033398: linux-image-amd64: reproducible kernel freeze on 5.19+
Message-ID<GddGN-f0Se-5@gated-at.bofh.it>
On Fri, 24 Mar 2023 13:50:15 +0100 Diederik de Haas 
<didi.debian@cknow.org> wrote:
> On Friday, 24 March 2023 12:44:33 CET Tim Rühsen wrote:
> > Package: linux-image-amd64
> > Version: 6.1.20-1
> > 
> > We run a priviledged eBPF based tool with a communication between kernel and
> > user space. It runs without issues on kernels 4.15 to 5.18.
> > On kernels 5.19+, the whole system freezes after a few minutes.
> 
> Via https://snapshot.debian.org/binary/linux-image-amd64/ you can easily test 
> various kernel versions. Could you try whether 5.19~rc4-1~exp1 indeed produces 
> the problem?

Yes - I can reproduce the total system freeze with 5.19~rc4-1~exp1 
(2022-07-01) from 
https://snapshot.debian.org/package/linux-signed-amd64/5.19~rc4%2B1~exp1/.

> 
> > Since the running program is rather complex, it is not easily possible to
> > carve out a small reproducer. We can provide gdb backtraces from freezes
> > inside qemu.
> 
> Someone else would have to chime in for the backtraces; that's beyond my skill 
> set.

I just learned about 
https://lore.kernel.org/bpf/20230118051443.78988-1-alexei.starovoitov@gmail.com/. 
With the provided patch applied I no longer mange to freeze the system.

- florian

[toc] | [next] | [standalone]


#78599

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-03-25 17:10 +0100
Message-ID<GdeCR-f1sd-7@gated-at.bofh.it>
In reply to#78595

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

Control: found -1 5.19~rc4-1~exp1
Control: forwarded -1 https://lore.kernel.org/bpf/20230118051443.78988-1-alexei.starovoitov@gmail.com/

On Saturday, 25 March 2023 16:00:47 CET Florian Lehner wrote:
> > Via https://snapshot.debian.org/binary/linux-image-amd64/ you can easily
> > test various kernel versions. Could you try whether 5.19~rc4-1~exp1
> > indeed produces the problem?
> 
> Yes - I can reproduce the total system freeze with 5.19~rc4-1~exp1

Thanks. Then the most likely case was that it was introduced in
the 5.19 merge window and thus also present in 5.19-rc1, but there isn't a 
prebuild kernel to verify.

> > > Since the running program is rather complex, it is not easily possible
> > > to carve out a small reproducer. We can provide gdb backtraces from
> > > freezes inside qemu.
> > 
> > Someone else would have to chime in for the backtraces; that's beyond my
> > skill set.
> 
> I just learned about
> https://lore.kernel.org/bpf/20230118051443.78988-1-alexei.starovoitov@gmail.
> com/. With the provided patch applied I no longer mange to freeze the
> system.

I see you already responded to that thread, excellent :-)
Hopefully they'll read this whole bug report, but mentioning that your actual
problem was NOT triggered till 5.18, but did trigger from 5.19-rc4 and later,
could be useful. I may not fully understand what upstream talked about, but I
only saw a reference to a 6.0.0 kernel.

Thanks for testing and reporting back :-)

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


#79226

FromFlorian Lehner <dev@der-flo.net>
Date2023-06-05 21:10 +0200
Message-ID<GDnKx-dToA-1@gated-at.bofh.it>
In reply to#78599
Hi all,

the fix was merged upstream with 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/mm/maccess.c?id=d319f344561de23e810515d109c7278919bff7b0

- florian

On 3/25/23 16:58, Diederik de Haas wrote:
> Control: found -1 5.19~rc4-1~exp1
> Control: forwarded -1 https://lore.kernel.org/bpf/20230118051443.78988-1-alexei.starovoitov@gmail.com/
> 
> On Saturday, 25 March 2023 16:00:47 CET Florian Lehner wrote:
>>> Via https://snapshot.debian.org/binary/linux-image-amd64/ you can easily
>>> test various kernel versions. Could you try whether 5.19~rc4-1~exp1
>>> indeed produces the problem?
>>
>> Yes - I can reproduce the total system freeze with 5.19~rc4-1~exp1
> 
> Thanks. Then the most likely case was that it was introduced in
> the 5.19 merge window and thus also present in 5.19-rc1, but there isn't a
> prebuild kernel to verify.
> 
>>>> Since the running program is rather complex, it is not easily possible
>>>> to carve out a small reproducer. We can provide gdb backtraces from
>>>> freezes inside qemu.
>>>
>>> Someone else would have to chime in for the backtraces; that's beyond my
>>> skill set.
>>
>> I just learned about
>> https://lore.kernel.org/bpf/20230118051443.78988-1-alexei.starovoitov@gmail.
>> com/. With the provided patch applied I no longer mange to freeze the
>> system.
> 
> I see you already responded to that thread, excellent :-)
> Hopefully they'll read this whole bug report, but mentioning that your actual
> problem was NOT triggered till 5.18, but did trigger from 5.19-rc4 and later,
> could be useful. I may not fully understand what upstream talked about, but I
> only saw a reference to a 6.0.0 kernel.
> 
> Thanks for testing and reporting back :-)

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


#79240

FromSalvatore Bonaccorso <carnil@debian.org>
Date2023-06-07 21:40 +0200
Message-ID<GE7aF-elt9-3@gated-at.bofh.it>
In reply to#79226
Hi Florian,

On Mon, Jun 05, 2023 at 08:49:25PM +0200, Florian Lehner wrote:
> Hi all,
> 
> the fix was merged upstream with https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/mm/maccess.c?id=d319f344561de23e810515d109c7278919bff7b0

And so landed in 6.4-rc1.

Great thanks! Would you mind proposing the change as well for
inclusion in the relevant stable versions? Make sure to CC the
relevant maintainers in the request for stable?

Regards,
Salvatore

[toc] | [prev] | [standalone]


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


csiph-web