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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 23 May 2020 16:52:16 +0100
From:   Al Viro <>
To:     Christoph Hellwig <>
Subject: Re: fiemap cleanups v4

On Sat, May 23, 2020 at 09:30:07AM +0200, Christoph Hellwig wrote:
> Hi all,
> This series cleans up the fiemap support in ext4 and in general.
> Ted or Al, can one of you pick this up?  It touches both ext4 and core
> code, so either tree could work.
> Changes since v3:
>  - dropped the fixes that have been merged int mainline
> Changes since v2:
>  - commit message typo
>  - doc updates
>  - use d_inode in cifs
>  - add a missing return statement in cifs
>  - remove the filemap_write_and_wait call from ext4_ioctl_get_es_cache
> Changes since v1:
>  - rename fiemap_validate to fiemap_prep
>  - lift FIEMAP_FLAG_SYNC handling to common code
>  - add a new linux/fiemap.h header
>  - remove __generic_block_fiemap
>  - remove access_ok calls from fiemap and ext4

Hmmm...  I can do an immutable shared branch, no problem.  What would
you prefer for a branchpoint for that one?

Powered by blists - more mailing lists