linux-kernel - Re: Kernel bio layer is sending bio size more than our block device is capable of handling

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 3 Mar 2017 00:14:36 -0700 (MST)
From:   Umesh Patel <Umesh.Patel@...t.com>
To:     linux-kernel@...r.kernel.org
Subject: Re: Kernel bio layer is sending bio size more than our block device
 is capable of handling

>From the kernel source code i came to know below things.

4.1 kernel version onward 
*""nr_pages = min(sdio->pages_in_io, bio_get_nr_vecs(map_bh->b_bdev))""*
line has been removed which was considering max_sectors_kb of queue. 

Now new code is something like this* "nr_pages = min(sdio->pages_in_io,
BIO_MAX_PAGES)"*, which is sending 256 bytes of data to our device which we
are not supporting.

Please let me know is there any other place where i can register my
max_sectors_kb to kernel.

--
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-tp1381843p1381844.html
Sent from the Linux Kernel mailing list archive at Nabble.com.