From: Matthew Wilcox <willy@infradead.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: helpdesk@kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
stable@kernel.org
Subject: Re: rename ext4 corrupting kernels on kernel.org?
Date: Sat, 6 Jan 2024 18:58:17 +0000 [thread overview]
Message-ID: <ZZmiyTedKJJVuMot@casper.infradead.org> (raw)
In-Reply-To: <CACVxJT9Qn4+cjbEQd=ske+Ch6TG+meY0F8RuhLSVH3+bY7Gg_g@mail.gmail.com>
On Sat, Jan 06, 2024 at 08:54:35PM +0300, Alexey Dobriyan wrote:
> I remember 2.4.11 was fs corrupting and official tarballs were renamed:
> https://mirrors.edge.kernel.org/pub/linux/kernel/v2.4/linux-2.4.11-dontuse.tar.bz2
>
> I'm not ext4 guy but which versions were affected recently?
>
> This comment mentions "6.1.64 and 6.1.65": https://lwn.net/Articles/954321/
That would seem like an overreaction. You've got to do some pretty rare
actions to corrupt your filesystem (iirc it was O_SYNC, O_DIRECT writes
that extend the file?)
prev parent reply other threads:[~2024-01-06 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 17:54 rename ext4 corrupting kernels on kernel.org? Alexey Dobriyan
2024-01-06 18:58 ` Matthew Wilcox [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=ZZmiyTedKJJVuMot@casper.infradead.org \
--to=willy@infradead.org \
--cc=adobriyan@gmail.com \
--cc=helpdesk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox