Re: [PATCH] block: fix q->max_segment_size checking in blk_recalc_rq_segments about VMERGE

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

 



Even if we fix it now, the question is: how long it will stay fixed? Until
someone makes another change to struct device that restricts boundaries on
some wacky hardware.

I'm not sure how the boundary restriction of a device can break
the VMERGE accounting.

Because block layer code doesn't know anything about the device, pci access restrictions and so on.

Someone already broken DaveM's Sparc64 merging by adding boundaries (it was broken even before, but these boundary checks made it worse).

Mikulas
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux