linux-ext4 - Re: [f2fs-dev] [PATCH] fscrypt: remove filesystem specific build config option

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]

Date:   Thu, 24 Jan 2019 00:03:37 -0500
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     Eric Biggers <ebiggers@...nel.org>
CC:     Guenter Roeck <linux@...ck-us.net>,
        Chandan Rajendra <chandan@...ux.vnet.ibm.com>,
        <linux-ext4@...r.kernel.org>,
        <linux-f2fs-devel@...ts.sourceforge.net>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [f2fs-dev] [PATCH] fscrypt: remove filesystem specific build
 config option

On Thu, Jan 10, 2019 at 05:01:17PM -0800, Eric Biggers wrote:
> 
> Indeed, Chandan Rajendra sent out a new version of the patch which fixes the
> problem (by removing the 'select BLOCK' from fs/ubifs/Kconfig), but it never
> made it into the fscrypt tree and hence never made it into linux-next.
> 
> Ted, what you are planning to do with the fscrypt tree following the fsverity
> discussion?  IMO, we should keep the fsverity stuff in its own branch, separate
> from any fscrypt changes.  As a suggestion, in the branch "fscrypt" of my
> linux.git repo [1], I applied just these four patches on top of v5.0-rc1 and
> resolved the conflicts with them no longer being on top of fsverity...

Sorry, I was on vacation last week and I've been catching up on things
this week.  I've reset the master branch on my fscrypt.git tree so
that it has what you have on your fscrypt branch, rebased to 5.0-rc3.

Also, as we had talked about earlier, it probably makes sense to set
up jointly maintained git tree for fscrypt and fsverity.  My proposal
is that we set up a new fscrypt.git tree, at
/pub/scm/fs/fscrypt/fscrypt.git, that would be owned by the "FSCRYPT
group", with group membership being ebiggers, jaeguk, and tytso.
We'll have to figure out ways that we can jointly update the git tree
without stepping on each other, probably using a group chat.  Does
that sound good to you?

					- Ted