On 06/02/15 11:49, Peter Lieven wrote:
Am 03.02.2015 um 16:33 schrieb Denis V. Lunev:
On 03/02/15 17:30, Peter Lieven wrote:
Am 03.02.2015 um 14:29 schrieb Denis V. Lunev:
On 03/02/15 15:12, Peter Lieven wrote:
we check and adjust request sizes at several places with
sometimes inconsistent ch
Am 03.02.2015 um 16:33 schrieb Denis V. Lunev:
> On 03/02/15 17:30, Peter Lieven wrote:
>> Am 03.02.2015 um 14:29 schrieb Denis V. Lunev:
>>> On 03/02/15 15:12, Peter Lieven wrote:
we check and adjust request sizes at several places with
sometimes inconsistent checks or default values:
>>
On 03/02/15 17:30, Peter Lieven wrote:
Am 03.02.2015 um 14:29 schrieb Denis V. Lunev:
On 03/02/15 15:12, Peter Lieven wrote:
we check and adjust request sizes at several places with
sometimes inconsistent checks or default values:
INT_MAX
INT_MAX >> BDRV_SECTOR_BITS
UINT_MAX >> BDRV_SECTO
Am 03.02.2015 um 14:29 schrieb Denis V. Lunev:
On 03/02/15 15:12, Peter Lieven wrote:
we check and adjust request sizes at several places with
sometimes inconsistent checks or default values:
INT_MAX
INT_MAX >> BDRV_SECTOR_BITS
UINT_MAX >> BDRV_SECTOR_BITS
SIZE_MAX >> BDRV_SECTOR_BITS
T
On 03/02/15 15:12, Peter Lieven wrote:
we check and adjust request sizes at several places with
sometimes inconsistent checks or default values:
INT_MAX
INT_MAX >> BDRV_SECTOR_BITS
UINT_MAX >> BDRV_SECTOR_BITS
SIZE_MAX >> BDRV_SECTOR_BITS
This patches introdocues a macro for the maximal
we check and adjust request sizes at several places with
sometimes inconsistent checks or default values:
INT_MAX
INT_MAX >> BDRV_SECTOR_BITS
UINT_MAX >> BDRV_SECTOR_BITS
SIZE_MAX >> BDRV_SECTOR_BITS
This patches introdocues a macro for the maximal allowed sectors
per request and uses it at se
