From: Richard Weinberger <richard@nod.at>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-fscrypt <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 23:39:04 +0200 (CEST) [thread overview]
Message-ID: <1886500245.56511.1557783544203.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20190513195652.GB142816@gmail.com>
----- Ursprüngliche Mail -----
> 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?
The simple answer is, not this time because my Laptops' filesystem broke
and I was kind of busy with recovery.
The issue is known, we have a patch and fixup will be sent to Linus
very soon. Nobody got hurt.
Thanks,
//richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Eric Biggers <ebiggers@kernel.org>
Cc: tytso <tytso@mit.edu>, Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd <linux-mtd@lists.infradead.org>,
linux-fscrypt <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 23:39:04 +0200 (CEST) [thread overview]
Message-ID: <1886500245.56511.1557783544203.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20190513195652.GB142816@gmail.com>
----- Ursprüngliche Mail -----
> 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?
The simple answer is, not this time because my Laptops' filesystem broke
and I was kind of busy with recovery.
The issue is known, we have a patch and fixup will be sent to Linus
very soon. Nobody got hurt.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-05-13 21:39 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
2019-05-13 19:56 ` Eric Biggers
2019-05-13 21:39 ` Richard Weinberger [this message]
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=1886500245.56511.1557783544203.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=ebiggers@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--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.