lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1488435362749-1381843.post@n7.nabble.com>
Date:   Wed, 1 Mar 2017 23:16:02 -0700 (MST)
From:   Umesh Patel <Umesh.Patel@...t.com>
To:     linux-kernel@...r.kernel.org
Subject: Kernel bio layer is sending bio size more than our block device is
 capable of handling

Hello,

We are registering bio size of our device with linux kernel with below
available kernel API.  blk_queue_max_hw_sectors(dev->osdev.queue,
(dev->aggr_max_size >> KERNEL_SECTOR_SHIFT));.

Max size of bio that our block device can handle is 106496 bytes (104KB) but
linux block device is sending 262144  bytes (256 KB) which is more than we
are registering with kernel.

This issue we are observing in 4.4.0-59-generic kernel version. Until this
we had not seen this issue.
So does anything extra require to tell linux kernel or anything else need to
register ?


Thanks
 



--
View this message in context: http://linux-kernel.2935.n7.nabble.com/Kernel-bio-layer-is-sending-bio-size-more-than-our-block-device-is-capable-of-handling-tp1381843.html
Sent from the Linux Kernel mailing list archive at Nabble.com.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ