From: Eric Biggers <ebiggers@kernel.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
Krzysztof Kozlowski <krzk@kernel.org>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org
Subject: Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
Date: Tue, 11 Dec 2018 14:36:20 -0800 [thread overview]
Message-ID: <20181211223619.GF221175@gmail.com> (raw)
In-Reply-To: <20181211222721.GC4464@thunk.org>
On Tue, Dec 11, 2018 at 05:27:21PM -0500, Theodore Y. Ts'o wrote:
> On Tue, Dec 11, 2018 at 03:15:53PM +0100, Krzysztof Kozlowski wrote:
> > Hi,
> >
> > Bisect from today's next pointed me to:
> > commit 4de97efb578a094e8fbf279522d41eb9ece1e3e0
> > Author: Chandan Rajendra <chandan@linux.vnet.ibm.com>
> > Date: Sat Dec 8 12:21:43 2018 +0530
> > fsverity: Move verity status check to fsverity_file_open
> >
> > as a reason of "Operation not supported" when reading any file from
> > mounted ext4fs (from SD card). Rootfs from nfsroot works but reading
> > from /home with ext4fs fails.
>
> Can you send me an compressed e2image of your sdcard?
>
> e2image -Q /dev/mmcblk0p2 sdcard.qcow2
> bzip2 -z sdcard.qcow2
>
> Thanks!
>
> - Ted
I don't think that's necessary. Due to the bug, ext4_file_open() and
ext4_setattr() always return -EOPNOTSUPP when !CONFIG_FS_VERITY.
I'm working on a fixed version of the two patches to replace the ones currently
in the fscrypt tree. Will send out soon.
- Eric
next prev parent reply other threads:[~2018-12-11 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 14:15 [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open" Krzysztof Kozlowski
2018-12-11 17:41 ` Eric Biggers
2018-12-12 4:11 ` Chandan Rajendra
2018-12-11 22:27 ` Theodore Y. Ts'o
2018-12-11 22:36 ` Eric Biggers [this message]
2018-12-12 2:55 ` Theodore Y. Ts'o
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=20181211223619.GF221175@gmail.com \
--to=ebiggers@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=chandan@linux.vnet.ibm.com \
--cc=jaegeuk@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yuchao0@huawei.com \
/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 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).