summaryrefslogtreecommitdiffstats
path: root/fs/cachefiles/io.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-12-12 20:06:35 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2022-12-12 20:06:35 -0800
commitad0d9da164cb52e62637e427517b2060dc956a2d (patch)
tree38883fca586da266024357ae86f296b5478b13a4 /fs/cachefiles/io.c
parent8129bac60f30936d2339535841db5b66d0520a67 (diff)
parenta4bbf53d88c728da9ff6c316b1e4ded63a8f3940 (diff)
downloadlinux-stable-ad0d9da164cb52e62637e427517b2060dc956a2d.tar.gz
linux-stable-ad0d9da164cb52e62637e427517b2060dc956a2d.tar.bz2
linux-stable-ad0d9da164cb52e62637e427517b2060dc956a2d.zip
Merge tag 'fsverity-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt
Pull fsverity updates from Eric Biggers: "The main change this cycle is to stop using the PG_error flag to track verity failures, and instead just track failures at the bio level. This follows a similar fscrypt change that went into 6.1, and it is a step towards freeing up PG_error for other uses. There's also one other small cleanup" * tag 'fsverity-for-linus' of git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt: fsverity: simplify fsverity_get_digest() fsverity: stop using PG_error to track error status
Diffstat (limited to 'fs/cachefiles/io.c')
0 files changed, 0 insertions, 0 deletions