linux-ext4 - Re: [PATCH] ext4: protect i_disksize update by i_data

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]

Date:   Fri, 30 Mar 2018 14:14:02 -0400
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Sasha Levin <Alexander.Levin@...rosoft.com>
Cc:     Ext4 Developers List <linux-ext4@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] ext4: protect i_disksize update by i_data_sem in direct
 write path

On Fri, Mar 30, 2018 at 04:16:10PM +0000, Sasha Levin wrote:
> 
> Here's a mail that would be sent as a result of an autoselection. It
> will note the "score" of the patch, and will run the same tests we
> do for patches tagged for stable.
> 
> As before, please let me know your thoughts on this. Thanks!
> ...
> 
> Please let us know if you'd like to have this patch included in a stable tree.

This patch is in the ext4 tree but has not been integrated into the
mainline kernel.  It will be shortly, once the merge window opens.

How are patches selected for potential autoselection?  If they are in
linux-ext but not yet in mainline, I would assume this would be a
reason not to select it, no?

Regards,

					- Ted