linux-ext4 - Re: Suggested change for superblock journal hint

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191114172754.GB4579@mit.edu>
Date:   Thu, 14 Nov 2019 12:27:54 -0500
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Jesse Grodman <jgrodman@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: Suggested change for superblock journal hint

On Thu, Nov 14, 2019 at 05:05:06PM +0200, Jesse Grodman wrote:
> Hi,
> 
> I encountered the scenario that a full fsck check was being run
> unnecessarily when the major / minor number of my external journal was
> being fixed by fsck. This PR changes that so that this change does
> trigger the full fsck run: github.com/tytso/e2fsprogs/pull/26

Hi Jessie,

It's preferable that patches e2fsprogs be sent to the linux-ext4 list,
so they can get reviewed by the full ext4 community.  That being said,
I will accept minor patches sent via a pull request if they full meet
the requirements for kernel patches:

https://www.kernel.org/doc/html/latest/process/submitting-patches.html

Note in particular the requirements for the Developer's Certification
of Origin (aka the Signed-off-by tag).  That has specific legal
meanings (for example, you are certifying that your employer allows
you to contribute to open source projects, or at least, *this* open
source project), so please take a close look at that.

Cheers,

					- Ted