Re: limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]

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

 



On 4/9/18 5:54 PM, Linus Torvalds wrote:
> On Mon, Apr 9, 2018 at 3:32 PM, Jens Axboe <axboe@xxxxxxxxx> wrote:
>>
>> The resulting min/max and friends would have been trivial to test, but
>> clearly they weren't.
> 
> Well, the min/max macros themselves actually were tested in user space by me.
> 
> It was the interaction with the unrelated "min_not_zero()" that wasn't ;)
> 
> It's easy in hind-sight to say "that's not at all unrelated", but
> within the context of doing min/max, it was.

I guess we should just be thankful that it didn't cause bigger issues
than an oops.

-- 
Jens Axboe

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel



[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux