From: "Leo Famulari" <leo@famulari.name>
To: "Hilton Chain" <hako@ultrarare.space>,
"Felix Lechner" <felix.lechner@lease-up.com>
Cc: "Christopher Baines via Development of GNU Guix and the GNU
System distribution." <guix-devel@gnu.org>
Subject: Re: Ext4 corruption in some stable kernels
Date: Sun, 10 Dec 2023 19:13:58 -0500 [thread overview]
Message-ID: <42d2662f-ca9f-4e58-8df5-232ebcd494ae@app.fastmail.com> (raw)
In-Reply-To: <87a5qik4bh.wl-hako@ultrarare.space>
Everyone with commit privileges should feel free to push these patches to master if they seem okay. I won't be able to help today.
Leo
On Sun, Dec 10, 2023, at 00:35, Hilton Chain wrote:
> Hi Felix (and Leo, Cc-ed)
>
> On Sun, 10 Dec 2023 11:00:47 +0800,
> Felix Lechner via Development of GNU Guix and the GNU System
> distribution. wrote:
>>
>> Hi,
>>
>> It's possible Guix never shipped the affected "stable" kernels, but a brief
>> pointer seemed appropriate. For details, please see here. [1]
>>
>> Kind regards
>> Felix
>>
>> [1] https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/
>>
>
> From the linked thread and report in Debian[1], 6.1.64 (and maybe 5.10.202 +
> 5.15.140) are affected. Unfortunately we have shipped them for about 1 week.
>
> Leo has sent #67724 yesterday to update kernels, maybe we can merge updates for
> these three versions quicker?
>
> Thanks
> ---
> [1]: https://micronews.debian.org/2023/1702150551.html
next prev parent reply other threads:[~2023-12-11 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 3:00 Ext4 corruption in some stable kernels Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-10 5:35 ` Hilton Chain
2023-12-10 6:53 ` Hilton Chain
2023-12-11 0:13 ` Leo Famulari [this message]
2023-12-11 3:30 ` Hilton Chain
2023-12-11 17:14 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42d2662f-ca9f-4e58-8df5-232ebcd494ae@app.fastmail.com \
--to=leo@famulari.name \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=hako@ultrarare.space \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).