* Creating a mailing list, git tree, and patchwork project for fscrypt
@ 2016-12-16 20:37 Theodore Ts'o
2016-12-16 20:39 ` Richard Weinberger
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Theodore Ts'o @ 2016-12-16 20:37 UTC (permalink / raw)
To: linux-fsdevel
Cc: jaegeuk, ebiggers, mhalcrow, richard, linux-ext4, linux-f2fs
I'm thinking about creating a separate mailing list (linux-fscrypt),
git tree and patchwork project, just to make it easier to track the
patches which are coming in.
Does anyone have any objections with that plan?
Cheers,
- Ted
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Creating a mailing list, git tree, and patchwork project for fscrypt
2016-12-16 20:37 Creating a mailing list, git tree, and patchwork project for fscrypt Theodore Ts'o
@ 2016-12-16 20:39 ` Richard Weinberger
2016-12-16 20:53 ` Eric Biggers
2017-03-29 21:14 ` Eric Biggers
2 siblings, 0 replies; 6+ messages in thread
From: Richard Weinberger @ 2016-12-16 20:39 UTC (permalink / raw)
To: Theodore Ts'o, linux-fsdevel
Cc: jaegeuk, ebiggers, mhalcrow, linux-ext4, linux-f2fs
Ted,
On 16.12.2016 21:37, Theodore Ts'o wrote:
> I'm thinking about creating a separate mailing list (linux-fscrypt),
> git tree and patchwork project, just to make it easier to track the
> patches which are coming in.
>
> Does anyone have any objections with that plan?
Please go ahead. Having a fscrypt specific tree/mailing list would be
great!
Thanks,
//richard
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Creating a mailing list, git tree, and patchwork project for fscrypt
2016-12-16 20:37 Creating a mailing list, git tree, and patchwork project for fscrypt Theodore Ts'o
2016-12-16 20:39 ` Richard Weinberger
@ 2016-12-16 20:53 ` Eric Biggers
2016-12-16 22:04 ` Theodore Ts'o
2017-03-29 21:14 ` Eric Biggers
2 siblings, 1 reply; 6+ messages in thread
From: Eric Biggers @ 2016-12-16 20:53 UTC (permalink / raw)
To: Theodore Ts'o
Cc: linux-fsdevel, jaegeuk, ebiggers, mhalcrow, richard, linux-ext4,
linux-f2fs
On Fri, Dec 16, 2016 at 03:37:32PM -0500, Theodore Ts'o wrote:
> I'm thinking about creating a separate mailing list (linux-fscrypt),
> git tree and patchwork project, just to make it easier to track the
> patches which are coming in.
>
> Does anyone have any objections with that plan?
>
Sounds great!
I guess it will be "fscrypt" and not "fscrypto"? There has been some confusion
about which term to use but it seems to be settling on "fscrypt".
Eric
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Creating a mailing list, git tree, and patchwork project for fscrypt
2016-12-16 20:53 ` Eric Biggers
@ 2016-12-16 22:04 ` Theodore Ts'o
2016-12-16 22:25 ` Eric Biggers
0 siblings, 1 reply; 6+ messages in thread
From: Theodore Ts'o @ 2016-12-16 22:04 UTC (permalink / raw)
To: Eric Biggers
Cc: linux-fsdevel, jaegeuk, ebiggers, mhalcrow, richard, linux-ext4,
linux-f2fs
On Fri, Dec 16, 2016 at 12:53:30PM -0800, Eric Biggers wrote:
> Sounds great!
>
> I guess it will be "fscrypt" and not "fscrypto"? There has been some confusion
> about which term to use but it seems to be settling on "fscrypt".
It was originally fscrypt, but then fscrypto crept in when we
refactored the out to the fs/crypto directory from fs/ext4. I was
planning on cleaning that up before we had too many file systems users
of fscrypt that we would need to synchronzie with, but it'll be easier
to do this as a separate git tree. We can either do it at the very
beginning of the merge window (and have all of the file systems pull
the change into fs/crypt), or I can work with Linus to do it right
after the next next merge window closes.
My preferences would be for the former, given where we are in the
development cycle.
Any objections?
- Ted
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Creating a mailing list, git tree, and patchwork project for fscrypt
2016-12-16 22:04 ` Theodore Ts'o
@ 2016-12-16 22:25 ` Eric Biggers
0 siblings, 0 replies; 6+ messages in thread
From: Eric Biggers @ 2016-12-16 22:25 UTC (permalink / raw)
To: Theodore Ts'o
Cc: linux-fsdevel, jaegeuk, ebiggers, mhalcrow, richard, linux-ext4,
linux-f2fs
On Fri, Dec 16, 2016 at 05:04:19PM -0500, Theodore Ts'o wrote:
> On Fri, Dec 16, 2016 at 12:53:30PM -0800, Eric Biggers wrote:
> > Sounds great!
> >
> > I guess it will be "fscrypt" and not "fscrypto"? There has been some confusion
> > about which term to use but it seems to be settling on "fscrypt".
>
> It was originally fscrypt, but then fscrypto crept in when we
> refactored the out to the fs/crypto directory from fs/ext4. I was
> planning on cleaning that up before we had too many file systems users
> of fscrypt that we would need to synchronzie with, but it'll be easier
> to do this as a separate git tree. We can either do it at the very
> beginning of the merge window (and have all of the file systems pull
> the change into fs/crypt), or I can work with Linus to do it right
> after the next next merge window closes.
>
> My preferences would be for the former, given where we are in the
> development cycle.
>
I'm fine with fscrypt. With regards to the cleanup, are you referring to
renaming the header fscrypto.h to fscrypt.h? Fortunately there aren't a lot
places that "fscrypto" actually appears in the tree --- basically just that
header, the module name, a couple log messages, and the MAINTAINERS file:
MAINTAINERS:FS-CRYPTO: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
MAINTAINERS:F: include/linux/fscrypto.h
fs/crypto/Makefile:obj-$(CONFIG_FS_ENCRYPTION) += fscrypto.o
fs/crypto/Makefile:fscrypto-y := crypto.o fname.o policy.o keyinfo.o
fs/crypto/Makefile:fscrypto-$(CONFIG_BLOCK) += bio.o
fs/crypto/fscrypt_private.h:#include <linux/fscrypto.h>
fs/crypto/keyinfo.c: pr_warn_once("fscrypto: unsupported contents encryption mode "
fs/crypto/keyinfo.c: pr_warn_once("fscrypto: unsupported filenames encryption mode "
fs/crypto/keyinfo.c: pr_warn_once("fscrypto: unsupported file type %d for inode %lu\n",
fs/ext4/ext4.h:#include <linux/fscrypto.h>
fs/ext4/page-io.c:#include <linux/fscrypto.h>
fs/f2fs/f2fs.h:#include <linux/fscrypto.h>
fs/ubifs/ubifs.h:#include <linux/fscrypto.h>
include/linux/fscrypto.h:#ifndef _LINUX_FSCRYPTO_H
include/linux/fscrypto.h:#define _LINUX_FSCRYPTO_H
include/linux/fscrypto.h:#endif /* _LINUX_FSCRYPTO_H */
Eric
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Creating a mailing list, git tree, and patchwork project for fscrypt
2016-12-16 20:37 Creating a mailing list, git tree, and patchwork project for fscrypt Theodore Ts'o
2016-12-16 20:39 ` Richard Weinberger
2016-12-16 20:53 ` Eric Biggers
@ 2017-03-29 21:14 ` Eric Biggers
2 siblings, 0 replies; 6+ messages in thread
From: Eric Biggers @ 2017-03-29 21:14 UTC (permalink / raw)
To: Theodore Ts'o
Cc: linux-fsdevel, jaegeuk, ebiggers, mhalcrow, richard, linux-ext4,
linux-f2fs, linux-fscrypt
On Fri, Dec 16, 2016 at 03:37:32PM -0500, Theodore Ts'o wrote:
> I'm thinking about creating a separate mailing list (linux-fscrypt),
> git tree and patchwork project, just to make it easier to track the
> patches which are coming in.
>
> Does anyone have any objections with that plan?
>
> Cheers,
>
This seems to have done for a while now:
* http://vger.kernel.org/vger-lists.html#linux-fscrypt
* https://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git/
* https://patchwork.kernel.org/project/linux-fscrypt/list/
Were you planning to also update the MAINTAINERS file to refer to the new list?
- Eric
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-03-29 21:14 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-12-16 20:37 Creating a mailing list, git tree, and patchwork project for fscrypt Theodore Ts'o
2016-12-16 20:39 ` Richard Weinberger
2016-12-16 20:53 ` Eric Biggers
2016-12-16 22:04 ` Theodore Ts'o
2016-12-16 22:25 ` Eric Biggers
2017-03-29 21:14 ` Eric Biggers
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).