Re: [GIT PULL] fsverity fix for 5.15-rc4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Eric Biggers <ebiggers@xxxxxxxxxx>
- Subject: Re: [GIT PULL] fsverity fix for 5.15-rc4
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 28 Sep 2021 07:59:32 -0700
- In-reply-to: <YVK0jzJ/lt97xowQ@sol.localdomain>
- References: <YVK0jzJ/lt97xowQ@sol.localdomain>
On Mon, Sep 27, 2021 at 11:22 PM Eric Biggers <ebiggers@xxxxxxxxxx> wrote:
>
> Fix an integer overflow when computing the Merkle tree layout of
> extremely large files, exposed by btrfs adding support for fs-verity.
I wonder if 'i_size' should be u64. I'm not convinced people think
about 'loff_t' being signed - but while that's required for negative
lseek() offsets, I'm not sure it makes tons of sense for an inode
size.
Same goes for f_pos, for that matter.
But who knows what games people have played with magic numbers (ie
"-1") internally, or where they _want_ signed compares. So it's
certainly not some obvious trivial fix.
Pulled.
Linus
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[IETF Sipping]
[Info Cyrus]
[ALSA User]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite News]
[Deep Creek Hot Springs]
[Yosemite Campsites]
[ISDN Cause Codes]