From: Dominique Martinet <asmadeus@codewreck.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
Kees Cook <kees@kernel.org>,
stable@vger.kernel.org
Subject: Re: please revert backport of 44c76825d6eefee9eb7ce06c38e1a6632ac7eb7d
Date: Fri, 6 Dec 2024 21:04:39 +0900 [thread overview]
Message-ID: <Z1LoVw0ei1rm9MTO@codewreck.org> (raw)
In-Reply-To: <dbc8f688-46db-427c-8177-ab7c26233eaf@tls.msk.ru>
Hi mjt,
Michael Tokarev wrote on Thu, Dec 05, 2024 at 10:35:26AM +0300:
> It would be great to fix this in debian, yes. It's a debian matter
> anyway, for details there's no need to bother kernel people.
> Please see #1088273. Fixed qemu release should come together with
> the updated kernel in debian -- if it will be next point release,
> so be it, but if the kernel goes before, we should pick qemu too,
> because else we'll re-introduce #1087822.
The kernel aleady shipped in debian a while ago, hence the bug
reports :)
More precisely, the "bad" commit b0cde867b80 (in 6.1 tree) made it in
6.1.107, and debian stable has been shipping it since the 6.1.112 update
on the 3rd of October[1][2], so we've been here for a while now
[1] https://tracker.debian.org/pkg/linux-signed-amd64
[2] https://tracker.debian.org/news/1571617/accepted-linux-signed-amd64-611121-source-into-stable-security/
Cheers,
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2024-12-06 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 14:33 please revert backport of 44c76825d6eefee9eb7ce06c38e1a6632ac7eb7d Kees Cook
2024-11-25 7:26 ` Michael Tokarev
2024-12-05 6:54 ` Salvatore Bonaccorso
2024-12-05 7:07 ` Greg KH
2024-12-05 7:22 ` Salvatore Bonaccorso
2024-12-05 7:35 ` Michael Tokarev
2024-12-06 12:04 ` Dominique Martinet [this message]
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=Z1LoVw0ei1rm9MTO@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=carnil@debian.org \
--cc=kees@kernel.org \
--cc=mjt@tls.msk.ru \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.