Re: [PATCH] fuse: fs-verity: aoid out-of-range comparison

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Eric Biggers <ebiggers@xxxxxxxxxx>
Subject: Re: [PATCH] fuse: fs-verity: aoid out-of-range comparison
From: Richard Fung <richardfung@xxxxxxxxxx>
Date: Thu, 1 Aug 2024 10:45:01 -0700
Cc: Arnd Bergmann <arnd@xxxxxxxxxx>, Miklos Szeredi <miklos@xxxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxx>, Nathan Chancellor <nathan@xxxxxxxxxx>, Nick Desaulniers <ndesaulniers@xxxxxxxxxx>, Bill Wendling <morbo@xxxxxxxxxx>, Justin Stitt <justinstitt@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, llvm@xxxxxxxxxxxxxxx
In-reply-to: <20240801010953.GA1835661@google.com>

> I think this was just defensive coding to ensure that the assignment to iov_len can't overflow regardless of the type of digest_size

I agree with this. Removing it sounds good to me

References:
- [PATCH] fuse: fs-verity: aoid out-of-range comparison
  - From: Arnd Bergmann
- Re: [PATCH] fuse: fs-verity: aoid out-of-range comparison
  - From: Eric Biggers

Prev by Date: Re: [PATCH 08/10] fanotify: report file range info with pre-content events
Next by Date: Re: [RFC PATCH] binfmt_elf: Dump smaller VMAs first in ELF cores
Previous by thread: Re: [PATCH] fuse: fs-verity: aoid out-of-range comparison
Next by thread: [PATCH 6.10 765/809] netfs: Fix writeback that needs to go to both server and cache
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux