Re: [PATCH] ext4: avoid arithemetic overflow that can trigger a BUG

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

To: Jiri Slaby <jslaby@xxxxxxx>
Subject: Re: [PATCH] ext4: avoid arithemetic overflow that can trigger a BUG
From: "Theodore Y. Ts'o" <tytso@xxxxxxx>
Date: Fri, 31 Aug 2018 22:50:03 -0400
Cc: Ext4 Developers List <linux-ext4@xxxxxxxxxxxxxxx>, stable@xxxxxxxxxxxxxxx
In-reply-to: <27af5487-9579-0950-94b5-0292b80e37c7@suse.cz>
References: <20180831174126.13071-1-tytso@mit.edu> <27af5487-9579-0950-94b5-0292b80e37c7@suse.cz>
User-agent: Mutt/1.10.1 (2018-07-13)

On Fri, Aug 31, 2018 at 09:31:36PM +0200, Jiri Slaby wrote:
> 
> Can't this be just
> 
> map.m_len = min_t(unsigned long, last_block - first_block + 1, UINT_MAX)?

Yes, good point, thanks.

					- Ted

Follow-Ups:
- [PATCH -v2] ext4: avoid arithemetic overflow that can trigger a BUG
  - From: Theodore Ts'o

References:
- [PATCH] ext4: avoid arithemetic overflow that can trigger a BUG
  - From: Theodore Ts'o
- Re: [PATCH] ext4: avoid arithemetic overflow that can trigger a BUG
  - From: Jiri Slaby

Prev by Date: Re: [PATCH] ext4: avoid arithemetic overflow that can trigger a BUG
Next by Date: Re: [PATCH v2] fs: Convert return type int to vm_fault_t
Previous by thread: Re: [PATCH] ext4: avoid arithemetic overflow that can trigger a BUG
Next by thread: [PATCH -v2] ext4: avoid arithemetic overflow that can trigger a BUG
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