From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: Regression in next-20181211 with fsverity changes
Date: Wed, 12 Dec 2018 09:46:27 +0530 [thread overview]
Message-ID: <3171217.2PqYythArb@localhost.localdomain> (raw)
In-Reply-To: <20181211191220.GW6707@atomide.com>
On Wednesday, December 12, 2018 12:42:20 AM IST Tony Lindgren wrote:
> Hi,
>
> Looks like commit 4de97efb578a ("fsverity: Move verity status check
> to fsverity_file_open") causes a boot regression for me with root
> on ext4 SDIO card, see below.
>
fsverity_file_open() used to incorrectly return -EOPNOTSUPP for non-fsverity
files on kernels built without fsverity support. This bug has been fixed in
the V4 patchset <https://marc.info/?l=linux-ext4&m=154458767124953&w=2>.
--
chandan
WARNING: multiple messages have this Message-ID (diff)
From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: Regression in next-20181211 with fsverity changes
Date: Wed, 12 Dec 2018 09:46:27 +0530 [thread overview]
Message-ID: <3171217.2PqYythArb@localhost.localdomain> (raw)
In-Reply-To: <20181211191220.GW6707@atomide.com>
On Wednesday, December 12, 2018 12:42:20 AM IST Tony Lindgren wrote:
> Hi,
>
> Looks like commit 4de97efb578a ("fsverity: Move verity status check
> to fsverity_file_open") causes a boot regression for me with root
> on ext4 SDIO card, see below.
>
fsverity_file_open() used to incorrectly return -EOPNOTSUPP for non-fsverity
files on kernels built without fsverity support. This bug has been fixed in
the V4 patchset <https://marc.info/?l=linux-ext4&m=154458767124953&w=2>.
--
chandan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-12 4:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 19:12 Regression in next-20181211 with fsverity changes Tony Lindgren
2018-12-11 19:12 ` Tony Lindgren
2018-12-12 4:16 ` Chandan Rajendra [this message]
2018-12-12 4:16 ` Chandan Rajendra
2018-12-12 14:59 ` Tony Lindgren
2018-12-12 14:59 ` Tony Lindgren
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=3171217.2PqYythArb@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.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.