From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752238AbdCBGkv (ORCPT ); Thu, 2 Mar 2017 01:40:51 -0500 Received: from mwork.nabble.com ([162.253.133.43]:57654 "EHLO mwork.nabble.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751114AbdCBGku (ORCPT ); Thu, 2 Mar 2017 01:40:50 -0500 X-Greylist: delayed 1465 seconds by postgrey-1.27 at vger.kernel.org; Thu, 02 Mar 2017 01:40:50 EST Date: Wed, 1 Mar 2017 23:16:02 -0700 (MST) From: Umesh Patel To: linux-kernel@vger.kernel.org Message-ID: <1488435362749-1381843.post@n7.nabble.com> Subject: Kernel bio layer is sending bio size more than our block device is capable of handling MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.