Re: [PATCH 4/4] ext4: ensure i_size is smaller than maxbytes

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

To: Zhang Yi <yi.zhang@xxxxxxxxxxxxxxx>
Subject: Re: [PATCH 4/4] ext4: ensure i_size is smaller than maxbytes
From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
Date: Wed, 30 Apr 2025 04:20:01 +0100
Cc: linux-ext4@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, tytso@xxxxxxx, adilger.kernel@xxxxxxxxx, jack@xxxxxxx, wanghaichi0403@xxxxxxxxx, yi.zhang@xxxxxxxxxx, libaokun1@xxxxxxxxxx, yukuai3@xxxxxxxxxx, yangerkun@xxxxxxxxxx
In-reply-to: <20250430011301.1106457-4-yi.zhang@huaweicloud.com>
References: <20250430011301.1106457-1-yi.zhang@huaweicloud.com> <20250430011301.1106457-4-yi.zhang@huaweicloud.com>

On Wed, Apr 30, 2025 at 09:13:01AM +0800, Zhang Yi wrote:
> From: Zhang Yi <yi.zhang@xxxxxxxxxx>
> 
> The inode i_size cannot be larger than maxbytes, check it while loading
> inode from the disk.

With this patch, why do we need patch 1?

Follow-Ups:
- Re: [PATCH 4/4] ext4: ensure i_size is smaller than maxbytes
  - From: Zhang Yi

References:
- [PATCH 1/4] ext4: fix out of bounds punch offset
  - From: Zhang Yi
- [PATCH 4/4] ext4: ensure i_size is smaller than maxbytes
  - From: Zhang Yi

Prev by Date: Re: kernel BUG in zero_user_segments
Next by Date: Re: [PATCH 4/4] ext4: ensure i_size is smaller than maxbytes
Previous by thread: [PATCH 4/4] ext4: ensure i_size is smaller than maxbytes
Next by thread: Re: [PATCH 4/4] ext4: ensure i_size is smaller than maxbytes
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux