Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"

To: Krzysztof Kozlowski <krzk@xxxxxxxxxx>, Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>, Andreas Dilger <adilger.kernel@xxxxxxxxx>, Jaegeuk Kim <jaegeuk@xxxxxxxxxx>, Chao Yu <yuchao0@xxxxxxxxxx>, Eric Biggers <ebiggers@xxxxxxxxxx>, linux-ext4@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx, linux-fscrypt@xxxxxxxxxxxxxxx
Subject: Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
Date: Tue, 11 Dec 2018 21:55:25 -0500
In-reply-to: <20181211222721.GC4464@thunk.org>
Mail-followup-to: "Theodore Y. Ts'o" <tytso@xxxxxxx>, Krzysztof Kozlowski <krzk@xxxxxxxxxx>, Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>, Andreas Dilger <adilger.kernel@xxxxxxxxx>, Jaegeuk Kim <jaegeuk@xxxxxxxxxx>, Chao Yu <yuchao0@xxxxxxxxxx>, Eric Biggers <ebiggers@xxxxxxxxxx>, linux-ext4@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx, linux-fscrypt@xxxxxxxxxxxxxxx
References: <CAJKOXPdNS+Qs6t1GwrgYhWT5EbtORJwYMzSrDPf8oAxv7ndNBg@mail.gmail.com> <20181211222721.GC4464@thunk.org>
User-agent: Mutt/1.10.1 (2018-07-13)

The fscrypt.git tree has been updated with for the problem.  Apologies
for not testing the !CONFIG_FS_VERITY case.

							- Ted

References:
- [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
  - From: Krzysztof Kozlowski
- Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
  - From: Theodore Y. Ts'o