linux-ext4 - RE: ext4 filesystem corruption (resize2fs bug)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID:
 <BN9PR18MB4219716B2A4C6CE5ACB7F46798832@BN9PR18MB4219.namprd18.prod.outlook.com>
Date: Wed, 30 Apr 2025 18:24:25 +0000
From: Andrea Biardi <Andrea.Biardi@...visolutions.com>
To: Theodore Ts'o <tytso@....edu>
CC: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: RE: ext4 filesystem corruption (resize2fs bug)

On Wednesday 30 April 2025 18:00, Theodore Ts'o <tytso@....edu> wrote:

> I've checked my e-mail backlog and I don't seem to see any e-mails
> from you.  What e-mail address did you use?

I might have used a different one, I don't recall myself!

> I saw the ping of the github issue #146 so it's been on my to do list.
> I've noted the patch at https://github.com/viavi-ab/e2fsprogs and I'll
> try to take look at it this week.

Much appreciated (and I'm no C developer, so take the patch with a grain
of salt!)

> In general, though, the best place to send patches or bug reports is
> to send them to linux-ext4@...r.kernel.org mailing list.  [..]

Understood, thanks. I wasn't aware and I thought creating a bug in github
was the right way to go about it. Perhaps it would be useful to explain the
process on github, e.g. in case somebody else finds critical bugs in
e2fsprogs that might need attention.

Cheers,
Andrea.