From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Paul Crowley <paulcrowley@google.com>,
Paul Lawrence <paullawrence@google.com>,
keyrings@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org,
David Howells <dhowells@redhat.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
Ondrej Kozina <okozina@redhat.com>
Subject: Re: [PATCH] fscrypt: support passing a keyring key to FS_IOC_ADD_ENCRYPTION_KEY
Date: Mon, 18 Nov 2019 18:01:02 +0000 [thread overview]
Message-ID: <20191118180102.GB5984@linux.intel.com> (raw)
In-Reply-To: <20191115230430.GA217050@gmail.com>
On Fri, Nov 15, 2019 at 03:04:31PM -0800, Eric Biggers wrote:
> On Sat, Nov 16, 2019 at 12:53:19AM +0200, Jarkko Sakkinen wrote:
> >
> > > I'm working on an xfstest for this:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/xfstests-dev.git/commit/?h=fscrypt-provisioning&id$ab6abb7cf6a80be44b7c72b73f0519ccaa5a97
> > >
> > > It's not quite ready, though. I'll post it for review when it is.
> > >
> > > Someone is also planning to update Android userspace to use this. So if there
> > > are any issues from that, I'll hear about it.
> >
> > Cool. Can you combine this patch and matching test (once it is done) to
> > a patch set?
> >
>
> xfstests is developed separately from the kernel (different git repo and
> maintainer), so combining kernel and xfstests patches into the same patchset
> doesn't make sense. I can certainly send them out at the same time, though.
Is there instructions somewhere how to build and run these tests?
For me it is sufficient if you point a branch and have some kind
of instructions somewhere.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Paul Crowley <paulcrowley@google.com>,
Paul Lawrence <paullawrence@google.com>,
keyrings@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org,
David Howells <dhowells@redhat.com>,
Ondrej Mosnacek <omosnace@redhat.com>,
Ondrej Kozina <okozina@redhat.com>
Subject: Re: [PATCH] fscrypt: support passing a keyring key to FS_IOC_ADD_ENCRYPTION_KEY
Date: Mon, 18 Nov 2019 20:01:02 +0200 [thread overview]
Message-ID: <20191118180102.GB5984@linux.intel.com> (raw)
In-Reply-To: <20191115230430.GA217050@gmail.com>
On Fri, Nov 15, 2019 at 03:04:31PM -0800, Eric Biggers wrote:
> On Sat, Nov 16, 2019 at 12:53:19AM +0200, Jarkko Sakkinen wrote:
> >
> > > I'm working on an xfstest for this:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/xfstests-dev.git/commit/?h=fscrypt-provisioning&id=24ab6abb7cf6a80be44b7c72b73f0519ccaa5a97
> > >
> > > It's not quite ready, though. I'll post it for review when it is.
> > >
> > > Someone is also planning to update Android userspace to use this. So if there
> > > are any issues from that, I'll hear about it.
> >
> > Cool. Can you combine this patch and matching test (once it is done) to
> > a patch set?
> >
>
> xfstests is developed separately from the kernel (different git repo and
> maintainer), so combining kernel and xfstests patches into the same patchset
> doesn't make sense. I can certainly send them out at the same time, though.
Is there instructions somewhere how to build and run these tests?
For me it is sufficient if you point a branch and have some kind
of instructions somewhere.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Ondrej Mosnacek <omosnace@redhat.com>,
linux-f2fs-devel@lists.sourceforge.net,
Paul Lawrence <paullawrence@google.com>,
linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org,
linux-mtd@lists.infradead.org, Ondrej Kozina <okozina@redhat.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org, Paul Crowley <paulcrowley@google.com>
Subject: Re: [f2fs-dev] [PATCH] fscrypt: support passing a keyring key to FS_IOC_ADD_ENCRYPTION_KEY
Date: Mon, 18 Nov 2019 20:01:02 +0200 [thread overview]
Message-ID: <20191118180102.GB5984@linux.intel.com> (raw)
In-Reply-To: <20191115230430.GA217050@gmail.com>
On Fri, Nov 15, 2019 at 03:04:31PM -0800, Eric Biggers wrote:
> On Sat, Nov 16, 2019 at 12:53:19AM +0200, Jarkko Sakkinen wrote:
> >
> > > I'm working on an xfstest for this:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/xfstests-dev.git/commit/?h=fscrypt-provisioning&id=24ab6abb7cf6a80be44b7c72b73f0519ccaa5a97
> > >
> > > It's not quite ready, though. I'll post it for review when it is.
> > >
> > > Someone is also planning to update Android userspace to use this. So if there
> > > are any issues from that, I'll hear about it.
> >
> > Cool. Can you combine this patch and matching test (once it is done) to
> > a patch set?
> >
>
> xfstests is developed separately from the kernel (different git repo and
> maintainer), so combining kernel and xfstests patches into the same patchset
> doesn't make sense. I can certainly send them out at the same time, though.
Is there instructions somewhere how to build and run these tests?
For me it is sufficient if you point a branch and have some kind
of instructions somewhere.
/Jarkko
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Ondrej Mosnacek <omosnace@redhat.com>,
linux-f2fs-devel@lists.sourceforge.net,
Paul Lawrence <paullawrence@google.com>,
linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org,
linux-mtd@lists.infradead.org, Ondrej Kozina <okozina@redhat.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org, Paul Crowley <paulcrowley@google.com>
Subject: Re: [PATCH] fscrypt: support passing a keyring key to FS_IOC_ADD_ENCRYPTION_KEY
Date: Mon, 18 Nov 2019 20:01:02 +0200 [thread overview]
Message-ID: <20191118180102.GB5984@linux.intel.com> (raw)
In-Reply-To: <20191115230430.GA217050@gmail.com>
On Fri, Nov 15, 2019 at 03:04:31PM -0800, Eric Biggers wrote:
> On Sat, Nov 16, 2019 at 12:53:19AM +0200, Jarkko Sakkinen wrote:
> >
> > > I'm working on an xfstest for this:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/xfstests-dev.git/commit/?h=fscrypt-provisioning&id=24ab6abb7cf6a80be44b7c72b73f0519ccaa5a97
> > >
> > > It's not quite ready, though. I'll post it for review when it is.
> > >
> > > Someone is also planning to update Android userspace to use this. So if there
> > > are any issues from that, I'll hear about it.
> >
> > Cool. Can you combine this patch and matching test (once it is done) to
> > a patch set?
> >
>
> xfstests is developed separately from the kernel (different git repo and
> maintainer), so combining kernel and xfstests patches into the same patchset
> doesn't make sense. I can certainly send them out at the same time, though.
Is there instructions somewhere how to build and run these tests?
For me it is sufficient if you point a branch and have some kind
of instructions somewhere.
/Jarkko
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-11-18 18:01 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 0:12 [PATCH] fscrypt: support passing a keyring key to FS_IOC_ADD_ENCRYPTION_KEY Eric Biggers
2019-11-07 0:12 ` Eric Biggers
2019-11-07 0:12 ` [f2fs-dev] " Eric Biggers
2019-11-07 0:12 ` Eric Biggers
2019-11-13 20:35 ` Eric Biggers
2019-11-13 20:35 ` Eric Biggers
2019-11-13 20:35 ` [f2fs-dev] " Eric Biggers
2019-11-13 20:35 ` Eric Biggers
2019-11-15 17:29 ` Jarkko Sakkinen
2019-11-15 17:29 ` Jarkko Sakkinen
2019-11-15 17:29 ` [f2fs-dev] " Jarkko Sakkinen
2019-11-15 17:29 ` Jarkko Sakkinen
2019-11-15 17:28 ` Jarkko Sakkinen
2019-11-15 17:28 ` Jarkko Sakkinen
2019-11-15 17:28 ` [f2fs-dev] " Jarkko Sakkinen
2019-11-15 17:28 ` Jarkko Sakkinen
2019-11-15 19:22 ` Eric Biggers
2019-11-15 19:22 ` Eric Biggers
2019-11-15 19:22 ` [f2fs-dev] " Eric Biggers
2019-11-15 19:22 ` Eric Biggers
2019-11-15 22:53 ` Jarkko Sakkinen
2019-11-15 22:53 ` Jarkko Sakkinen
2019-11-15 22:53 ` [f2fs-dev] " Jarkko Sakkinen
2019-11-15 22:53 ` Jarkko Sakkinen
2019-11-15 23:04 ` Eric Biggers
2019-11-15 23:04 ` Eric Biggers
2019-11-15 23:04 ` [f2fs-dev] " Eric Biggers
2019-11-15 23:04 ` Eric Biggers
2019-11-18 18:01 ` Jarkko Sakkinen [this message]
2019-11-18 18:01 ` Jarkko Sakkinen
2019-11-18 18:01 ` [f2fs-dev] " Jarkko Sakkinen
2019-11-18 18:01 ` Jarkko Sakkinen
2019-11-18 18:14 ` Eric Biggers
2019-11-18 18:14 ` Eric Biggers
2019-11-18 18:14 ` [f2fs-dev] " Eric Biggers
2019-11-18 18:14 ` Eric Biggers
2019-11-16 0:01 ` Theodore Y. Ts'o
2019-11-16 0:01 ` Theodore Y. Ts'o
2019-11-16 0:01 ` [f2fs-dev] " Theodore Y. Ts'o
2019-11-16 0:01 ` Theodore Y. Ts'o
2019-11-17 21:44 ` Darrick J. Wong
2019-11-17 21:44 ` Darrick J. Wong
2019-11-17 21:44 ` [f2fs-dev] " Darrick J. Wong
2019-11-17 21:44 ` Darrick J. Wong
2019-11-18 18:02 ` Jarkko Sakkinen
2019-11-18 18:02 ` Jarkko Sakkinen
2019-11-18 18:02 ` [f2fs-dev] " Jarkko Sakkinen
2019-11-18 18:02 ` Jarkko Sakkinen
2019-11-18 18:05 ` Jarkko Sakkinen
2019-11-18 18:05 ` Jarkko Sakkinen
2019-11-18 18:05 ` [f2fs-dev] " Jarkko Sakkinen
2019-11-18 18:05 ` Jarkko Sakkinen
2019-11-18 18:27 ` Eric Biggers
2019-11-18 18:27 ` Eric Biggers
2019-11-18 18:27 ` [f2fs-dev] " Eric Biggers
2019-11-18 18:27 ` Eric Biggers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191118180102.GB5984@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=okozina@redhat.com \
--cc=omosnace@redhat.com \
--cc=paulcrowley@google.com \
--cc=paullawrence@google.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.