From: Eric Biggers <ebiggers@kernel.org>
To: Richard Weinberger <richard@nod.at>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-fscrypt@vger.kernel.org, tytso <tytso@mit.edu>,
kernel <kernel@pengutronix.de>
Subject: Re: [PATCH 1/2] ubifs: Remove #ifdef around CONFIG_FS_ENCRYPTION
Date: Mon, 13 May 2019 12:56:53 -0700 [thread overview]
Message-ID: <20190513195652.GB142816@gmail.com> (raw)
In-Reply-To: <1170873772.48849.1557298158182.JavaMail.zimbra@nod.at>
On Wed, May 08, 2019 at 08:49:18AM +0200, Richard Weinberger wrote:
> Eric,
>
> ----- Urspr�ngliche Mail -----
> > Von: "Eric Biggers" <ebiggers@kernel.org>
> > An: "Sascha Hauer" <s.hauer@pengutronix.de>, "richard" <richard@nod.at>
> > CC: "linux-mtd" <linux-mtd@lists.infradead.org>, linux-fscrypt@vger.kernel.org, "tytso" <tytso@mit.edu>, "kernel"
> > <kernel@pengutronix.de>
> > Gesendet: Mittwoch, 8. Mai 2019 05:19:55
> > Betreff: Re: [PATCH 1/2] ubifs: Remove #ifdef around CONFIG_FS_ENCRYPTION
>
> > On Tue, Mar 26, 2019 at 08:52:31AM +0100, Sascha Hauer wrote:
> >> ifdefs reduce readablity and compile coverage. This removes the ifdefs
> >> around CONFIG_FS_ENCRYPTION by using IS_ENABLED and relying on static
> >> inline wrappers. A new static inline wrapper for setting sb->s_cop is
> >> introduced to allow filesystems to unconditionally compile in their
> >> s_cop operations.
> >>
> >> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> >> ---
> >> fs/ubifs/ioctl.c | 11 +----------
> >> fs/ubifs/sb.c | 7 ++++---
> >> fs/ubifs/super.c | 4 +---
> >> include/linux/fscrypt.h | 11 +++++++++++
> >> 4 files changed, 17 insertions(+), 16 deletions(-)
> >>
> >> diff --git a/fs/ubifs/ioctl.c b/fs/ubifs/ioctl.c
> >> index 82e4e6a30b04..6b05b3ec500e 100644
> >> --- a/fs/ubifs/ioctl.c
> >> +++ b/fs/ubifs/ioctl.c
> >> @@ -193,7 +193,6 @@ long ubifs_ioctl(struct file *file, unsigned int cmd,
> >> unsigned long arg)
> >> return err;
> >> }
> >> case FS_IOC_SET_ENCRYPTION_POLICY: {
> >> -#ifdef CONFIG_FS_ENCRYPTION
> >> struct ubifs_info *c = inode->i_sb->s_fs_info;
> >>
> >> err = ubifs_enable_encryption(c);
> >> @@ -201,17 +200,9 @@ long ubifs_ioctl(struct file *file, unsigned int cmd,
> >> unsigned long arg)
> >> return err;
> >>
> >> return fscrypt_ioctl_set_policy(file, (const void __user *)arg);
> >> -#else
> >> - return -EOPNOTSUPP;
> >> -#endif
> >> }
> >> - case FS_IOC_GET_ENCRYPTION_POLICY: {
> >> -#ifdef CONFIG_FS_ENCRYPTION
> >> + case FS_IOC_GET_ENCRYPTION_POLICY:
> >> return fscrypt_ioctl_get_policy(file, (void __user *)arg);
> >> -#else
> >> - return -EOPNOTSUPP;
> >> -#endif
> >> - }
> >>
> >> default:
> >> return -ENOTTY;
> >> diff --git a/fs/ubifs/sb.c b/fs/ubifs/sb.c
> >> index 67fac1e8adfb..2afc8b1d4c3b 100644
> >> --- a/fs/ubifs/sb.c
> >> +++ b/fs/ubifs/sb.c
> >> @@ -748,14 +748,12 @@ int ubifs_read_superblock(struct ubifs_info *c)
> >> goto out;
> >> }
> >>
> >> -#ifndef CONFIG_FS_ENCRYPTION
> >> - if (c->encrypted) {
> >> + if (!IS_ENABLED(CONFIG_UBIFS_FS_ENCRYPTION) && c->encrypted) {
> >> ubifs_err(c, "file system contains encrypted files but UBIFS"
> >> " was built without crypto support.");
> >> err = -EINVAL;
> >> goto out;
> >> }
> >
> > A bit late, but I noticed this in ubifs/linux-next. This needs to use
> > CONFIG_FS_ENCRYPTION here, not CONFIG_UBIFS_FS_ENCRYPTION, as the latter no
> > longer exists.
>
> Thanks for spotting. I'll fit it myself in -next.
>
> Thanks,
> //richard
This was merged to mainline and it's still broken. This breaks UBIFS encryption
entirely, BTW. Do you not run xfstests before sending pull requests?
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Richard Weinberger <richard@nod.at>
Cc: tytso <tytso@mit.edu>, Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-fscrypt@vger.kernel.org, kernel <kernel@pengutronix.de>
Subject: Re: [PATCH 1/2] ubifs: Remove #ifdef around CONFIG_FS_ENCRYPTION
Date: Mon, 13 May 2019 12:56:53 -0700 [thread overview]
Message-ID: <20190513195652.GB142816@gmail.com> (raw)
In-Reply-To: <1170873772.48849.1557298158182.JavaMail.zimbra@nod.at>
On Wed, May 08, 2019 at 08:49:18AM +0200, Richard Weinberger wrote:
> Eric,
>
> ----- Ursprüngliche Mail -----
> > Von: "Eric Biggers" <ebiggers@kernel.org>
> > An: "Sascha Hauer" <s.hauer@pengutronix.de>, "richard" <richard@nod.at>
> > CC: "linux-mtd" <linux-mtd@lists.infradead.org>, linux-fscrypt@vger.kernel.org, "tytso" <tytso@mit.edu>, "kernel"
> > <kernel@pengutronix.de>
> > Gesendet: Mittwoch, 8. Mai 2019 05:19:55
> > Betreff: Re: [PATCH 1/2] ubifs: Remove #ifdef around CONFIG_FS_ENCRYPTION
>
> > On Tue, Mar 26, 2019 at 08:52:31AM +0100, Sascha Hauer wrote:
> >> ifdefs reduce readablity and compile coverage. This removes the ifdefs
> >> around CONFIG_FS_ENCRYPTION by using IS_ENABLED and relying on static
> >> inline wrappers. A new static inline wrapper for setting sb->s_cop is
> >> introduced to allow filesystems to unconditionally compile in their
> >> s_cop operations.
> >>
> >> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> >> ---
> >> fs/ubifs/ioctl.c | 11 +----------
> >> fs/ubifs/sb.c | 7 ++++---
> >> fs/ubifs/super.c | 4 +---
> >> include/linux/fscrypt.h | 11 +++++++++++
> >> 4 files changed, 17 insertions(+), 16 deletions(-)
> >>
> >> diff --git a/fs/ubifs/ioctl.c b/fs/ubifs/ioctl.c
> >> index 82e4e6a30b04..6b05b3ec500e 100644
> >> --- a/fs/ubifs/ioctl.c
> >> +++ b/fs/ubifs/ioctl.c
> >> @@ -193,7 +193,6 @@ long ubifs_ioctl(struct file *file, unsigned int cmd,
> >> unsigned long arg)
> >> return err;
> >> }
> >> case FS_IOC_SET_ENCRYPTION_POLICY: {
> >> -#ifdef CONFIG_FS_ENCRYPTION
> >> struct ubifs_info *c = inode->i_sb->s_fs_info;
> >>
> >> err = ubifs_enable_encryption(c);
> >> @@ -201,17 +200,9 @@ long ubifs_ioctl(struct file *file, unsigned int cmd,
> >> unsigned long arg)
> >> return err;
> >>
> >> return fscrypt_ioctl_set_policy(file, (const void __user *)arg);
> >> -#else
> >> - return -EOPNOTSUPP;
> >> -#endif
> >> }
> >> - case FS_IOC_GET_ENCRYPTION_POLICY: {
> >> -#ifdef CONFIG_FS_ENCRYPTION
> >> + case FS_IOC_GET_ENCRYPTION_POLICY:
> >> return fscrypt_ioctl_get_policy(file, (void __user *)arg);
> >> -#else
> >> - return -EOPNOTSUPP;
> >> -#endif
> >> - }
> >>
> >> default:
> >> return -ENOTTY;
> >> diff --git a/fs/ubifs/sb.c b/fs/ubifs/sb.c
> >> index 67fac1e8adfb..2afc8b1d4c3b 100644
> >> --- a/fs/ubifs/sb.c
> >> +++ b/fs/ubifs/sb.c
> >> @@ -748,14 +748,12 @@ int ubifs_read_superblock(struct ubifs_info *c)
> >> goto out;
> >> }
> >>
> >> -#ifndef CONFIG_FS_ENCRYPTION
> >> - if (c->encrypted) {
> >> + if (!IS_ENABLED(CONFIG_UBIFS_FS_ENCRYPTION) && c->encrypted) {
> >> ubifs_err(c, "file system contains encrypted files but UBIFS"
> >> " was built without crypto support.");
> >> err = -EINVAL;
> >> goto out;
> >> }
> >
> > A bit late, but I noticed this in ubifs/linux-next. This needs to use
> > CONFIG_FS_ENCRYPTION here, not CONFIG_UBIFS_FS_ENCRYPTION, as the latter no
> > longer exists.
>
> Thanks for spotting. I'll fit it myself in -next.
>
> Thanks,
> //richard
This was merged to mainline and it's still broken. This breaks UBIFS encryption
entirely, BTW. Do you not run xfstests before sending pull requests?
- Eric
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-05-13 19:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 7:52 [PATCH 0/2] ubifs: Get rid of some ifdefs Sascha Hauer
2019-03-26 7:52 ` Sascha Hauer
2019-03-26 7:52 ` [PATCH 1/2] ubifs: Remove #ifdef around CONFIG_FS_ENCRYPTION Sascha Hauer
2019-03-26 7:52 ` Sascha Hauer
2019-05-08 3:19 ` Eric Biggers
2019-05-08 3:19 ` Eric Biggers
2019-05-08 6:49 ` Richard Weinberger
2019-05-08 6:49 ` Richard Weinberger
2019-05-13 19:56 ` Eric Biggers [this message]
2019-05-13 19:56 ` Eric Biggers
2019-05-13 21:39 ` Richard Weinberger
2019-05-13 21:39 ` Richard Weinberger
2019-03-26 7:52 ` [PATCH 2/2] ubifs: Remove ifdefs around CONFIG_UBIFS_ATIME_SUPPORT Sascha Hauer
2019-03-26 7:52 ` Sascha Hauer
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=20190513195652.GB142816@gmail.com \
--to=ebiggers@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
--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.