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 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.

              Linus



[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux