Re: [PATCH v4] xfs: check for possible overflow in xfs_ioc

xfs

Re: [PATCH v4] xfs: check for possible overflow in xfs_ioc_trim

To:	Dave Chinner <david@xxxxxxxxxxxxx>
Subject:	Re: [PATCH v4] xfs: check for possible overflow in xfs_ioc_trim
From:	Tomas Racek <tracek@xxxxxxxxxx>
Date:	Wed, 15 Aug 2012 08:23:32 -0400 (EDT)
Cc:	xfs@xxxxxxxxxxx, lczerner@xxxxxxxxxx, Alex Elder <elder@xxxxxxxxxx>, Ben Myers <bpm@xxxxxxx>
In-reply-to:	<20120814213629.GL2877@dastard>

Forwarding to maintainers.

----- Original Message -----
> On Tue, Aug 14, 2012 at 10:35:04AM +0200, Tomas Racek wrote:
> > If range.start or range.minlen is bigger than filesystem size,
> > return
> > invalid value error. This fixes possible overflow in BTOBB macro
> > when
> > passed value was nearly ULLONG_MAX.
> > 
> > Signed-off-by: Tomas Racek <tracek@xxxxxxxxxx>
> 
> looks ok to me.
> 
> Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
> --
> Dave Chinner
> david@xxxxxxxxxxxxx
>

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH v4] xfs: check for possible overflow in xfs_ioc_trim, Tomas Racek Re: [PATCH v4] xfs: check for possible overflow in xfs_ioc_trim, Dave Chinner Re: [PATCH v4] xfs: check for possible overflow in xfs_ioc_trim, Tomas Racek <= Re: [PATCH v4] xfs: check for possible overflow in xfs_ioc_trim, Ben Myers

Previous by Date:	Re: aborted SCSI commands while discarding/unmapping via mkfs.xfs, Stefan Ring
Next by Date:	[PATCH v3] xfstests: Use upstream version of fstrim instead of the local one, Tomas Racek
Previous by Thread:	Re: [PATCH v4] xfs: check for possible overflow in xfs_ioc_trim, Dave Chinner
Next by Thread:	Re: [PATCH v4] xfs: check for possible overflow in xfs_ioc_trim, Ben Myers
Indexes:	[Date] [Thread] [Top] [All Lists]