{"push_id":982264077,"size":58,"distinct_size":58,"ref":"refs/heads/master","head":"2850713576e81e3b887cd92a9965fba0dd1717c0","before":"65c23c65bee479faceb042a52f5a7278dfa8d972","commits":[{"sha":"3db70a853202c252a8ebefa71ccb088ad149cdd2","author":{"email":"f1431bf4ea962ea2009f7275289c2e0b23d8aceb@oracle.com","name":"Bob Liu"},"message":"xen/blkfront: realloc ring info in blkif_resume\n\nNeed to reallocate ring info in the resume path, because info->rinfo was freed\nin blkif_free(). And 'multi-queue-max-queues' backend reports may have been\nchanged.\n\nSigned-off-by: Bob Liu <bob.liu@oracle.com>\nReported-and-Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>\nSigned-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/3db70a853202c252a8ebefa71ccb088ad149cdd2"},{"sha":"7ddc971f86aa0a4cee9f6886c356a052461957ae","author":{"email":"9a024e2544da0dd1d651d8a76b83357108d77e55@gmail.com","name":"Mike Krinkin"},"message":"block: fix use-after-free in dio_bio_complete\n\nkasan reported the following error when i ran xfstest:\n\n[  701.826854] ==================================================================\n[  701.826864] BUG: KASAN: use-after-free in dio_bio_complete+0x41a/0x600 at addr ffff880080b95f94\n[  701.826870] Read of size 4 by task loop2/3874\n[  701.826879] page:ffffea000202e540 count:0 mapcount:0 mapping:          (null) index:0x0\n[  701.826890] flags: 0x100000000000000()\n[  701.826895] page dumped because: kasan: bad access detected\n[  701.826904] CPU: 3 PID: 3874 Comm: loop2 Tainted: G    B   W    L  4.5.0-rc1-next-20160129 #83\n[  701.826910] Hardware name: LENOVO 23205NG/23205NG, BIOS G2ET95WW (2.55 ) 07/09/2013\n[  701.826917]  ffff88008fadf800 ffff88008fadf758 ffffffff81ca67bb 0000000041b58ab3\n[  701.826941]  ffffffff830d1e74 ffffffff81ca6724 ffff88008fadf748 ffffffff8161c05c\n[  701.826963]  0000000000000282 ffff88008fadf800 ffffed0010172bf2 ffffea000202e540\n[  701.826987] Call Trace:\n[  701.826997]  [<ffffffff81ca67bb>] dump_stack+0x97/0xdc\n[  701.827005]  [<ffffffff81ca6724>] ? _atomic_dec_and_lock+0xc4/0xc4\n[  701.827014]  [<ffffffff8161c05c>] ? __dump_page+0x32c/0x490\n[  701.827023]  [<ffffffff816b0d03>] kasan_report_error+0x5f3/0x8b0\n[  701.827033]  [<ffffffff817c302a>] ? dio_bio_complete+0x41a/0x600\n[  701.827040]  [<ffffffff816b1119>] __asan_report_load4_noabort+0x59/0x80\n[  701.827048]  [<ffffffff817c302a>] ? dio_bio_complete+0x41a/0x600\n[  701.827053]  [<ffffffff817c302a>] dio_bio_complete+0x41a/0x600\n[  701.827057]  [<ffffffff81bd19c8>] ? blk_queue_exit+0x108/0x270\n[  701.827060]  [<ffffffff817c32b0>] dio_bio_end_aio+0xa0/0x4d0\n[  701.827063]  [<ffffffff817c3210>] ? dio_bio_complete+0x600/0x600\n[  701.827067]  [<ffffffff81bd2806>] ? blk_account_io_completion+0x316/0x5d0\n[  701.827070]  [<ffffffff81bafe89>] bio_endio+0x79/0x200\n[  701.827074]  [<ffffffff81bd2c9f>] blk_update_request+0x1df/0xc50\n[  701.827078]  [<ffffffff81c02c27>] blk_mq_end_request+0x57/0x120\n[  701.827081]  [<ffffffff81c03670>] __blk_mq_complete_request+0x310/0x590\n[  701.827084]  [<ffffffff812348d8>] ? set_next_entity+0x2f8/0x2ed0\n[  701.827088]  [<ffffffff8124b34d>] ? put_prev_entity+0x22d/0x2a70\n[  701.827091]  [<ffffffff81c0394b>] blk_mq_complete_request+0x5b/0x80\n[  701.827094]  [<ffffffff821e2a33>] loop_queue_work+0x273/0x19d0\n[  701.827098]  [<ffffffff811f6578>] ? finish_task_switch+0x1c8/0x8e0\n[  701.827101]  [<ffffffff8129d058>] ? trace_hardirqs_on_caller+0x18/0x6c0\n[  701.827104]  [<ffffffff821e27c0>] ? lo_read_simple+0x890/0x890\n[  701.827108]  [<ffffffff8129dd60>] ? debug_check_no_locks_freed+0x350/0x350\n[  701.827111]  [<ffffffff811f63b0>] ? __hrtick_start+0x130/0x130\n[  701.827115]  [<ffffffff82a0c8f6>] ? __schedule+0x936/0x20b0\n[  701.827118]  [<ffffffff811dd6bd>] ? kthread_worker_fn+0x3ed/0x8d0\n[  701.827121]  [<ffffffff811dd4ed>] ? kthread_worker_fn+0x21d/0x8d0\n[  701.827125]  [<ffffffff8129d058>] ? trace_hardirqs_on_caller+0x18/0x6c0\n[  701.827128]  [<ffffffff811dd57f>] kthread_worker_fn+0x2af/0x8d0\n[  701.827132]  [<ffffffff811dd2d0>] ? __init_kthread_worker+0x170/0x170\n[  701.827135]  [<ffffffff82a1ea46>] ? _raw_spin_unlock_irqrestore+0x36/0x60\n[  701.827138]  [<ffffffff811dd2d0>] ? __init_kthread_worker+0x170/0x170\n[  701.827141]  [<ffffffff811dd2d0>] ? __init_kthread_worker+0x170/0x170\n[  701.827144]  [<ffffffff811dd00b>] kthread+0x24b/0x3a0\n[  701.827148]  [<ffffffff811dcdc0>] ? kthread_create_on_node+0x4c0/0x4c0\n[  701.827151]  [<ffffffff8129d70d>] ? trace_hardirqs_on+0xd/0x10\n[  701.827155]  [<ffffffff8116d41d>] ? do_group_exit+0xdd/0x350\n[  701.827158]  [<ffffffff811dcdc0>] ? kthread_create_on_node+0x4c0/0x4c0\n[  701.827161]  [<ffffffff82a1f52f>] ret_from_fork+0x3f/0x70\n[  701.827165]  [<ffffffff811dcdc0>] ? kthread_create_on_node+0x4c0/0x4c0\n[  701.827167] Memory state around the buggy address:\n[  701.827170]  ffff880080b95e80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[  701.827172]  ffff880080b95f00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[  701.827175] >ffff880080b95f80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[  701.827177]                          ^\n[  701.827179]  ffff880080b96000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[  701.827182]  ffff880080b96080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n[  701.827183] ==================================================================\n\nThe problem is that bio_check_pages_dirty calls bio_put, so we must\nnot access bio fields after bio_check_pages_dirty.\n\nFixes: 9b81c842355ac96097ba (\"block: don't access bio->bi_error after bio_put()\").\nSigned-off-by: Mike Krinkin <krinkin.m.u@gmail.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/7ddc971f86aa0a4cee9f6886c356a052461957ae"},{"sha":"ed0ae43c9d5312932e1706e66506b2ba97fa7c93","author":{"email":"cd8c6775e60d6f67a6984377324e5290df3d5358@fb.com","name":"Jens Axboe"},"message":"Merge branch 'stable/for-jens-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen into for-linus","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/ed0ae43c9d5312932e1706e66506b2ba97fa7c93"},{"sha":"a0c80efe5956ccce9fe7ae5c78542578c07bc20a","author":{"email":"ed58f755cc8caaf10c3e8c731a8b86fb8f13d6cb@suse.cz","name":"Jiri Kosina"},"message":"floppy: fix lock_fdc() signal handling\n\nfloppy_revalidate() doesn't perform any error handling on lock_fdc()\nresult. lock_fdc() might actually be interrupted by a signal (it waits for\nfdc becoming non-busy interruptibly). In such case, floppy_revalidate()\nproceeds as if it had claimed the lock, but it fact it doesn't.\n\nIn case of multiple threads trying to open(\"/dev/fdX\"), this leads to\nserious corruptions all over the place, because all of a sudden there is\nno critical section protection (that'd otherwise be guaranteed by locked\nfd) whatsoever.\n\nWhile at this, fix the fact that the 'interruptible' parameter to\nlock_fdc() doesn't make any sense whatsoever, because we always wait\ninterruptibly anyway.\n\nMost of the lock_fdc() callsites do properly handle error (and propagate\nEINTR), but floppy_revalidate() and floppy_check_events() don't. Fix this.\n\nSpotted by 'syzkaller' tool.\n\nReported-by: Dmitry Vyukov <dvyukov@google.com>\nTested-by: Dmitry Vyukov <dvyukov@google.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/a0c80efe5956ccce9fe7ae5c78542578c07bc20a"},{"sha":"90b90d06db0be30aeb89b6b4ab618d644211a85e","author":{"email":"cd8c6775e60d6f67a6984377324e5290df3d5358@fb.com","name":"Jens Axboe"},"message":"Merge branch 'for-4.5/for-jens' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/linux-block into for-linus\n\nLocking fix from Jiri","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/90b90d06db0be30aeb89b6b4ab618d644211a85e"},{"sha":"e502fb8f8801c9561c57397e7fd917187762324e","author":{"email":"10f5d60ce5fa6fe3c789dd71c5d6567abd91f3fa@google.com","name":"Tahsin Erdogan"},"message":"deadline: remove unused struct member\n\ncommit 63de428b139d3d31d86ebe25ae97b33f6540fb7e (\"deadline-iosched:\nallow non-sequential batching\") removed last use of last_sector.\n\nSigned-off-by: Tahsin Erdogan <tahsin@google.com>\nReviewed-by: Jeff Moyer <jmoyer@redhat.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/e502fb8f8801c9561c57397e7fd917187762324e"},{"sha":"16c6d048d7b74249a4387700887e8adb13028866","author":{"email":"b7b23ccda0e17b06db3f8f9fbe3256e03bf19cd0@gmail.com","name":"Wenwei Tao"},"message":"lightnvm: put bio before return\n\nThe bio is not returned if the data page cannot be allocated.\n\nSigned-off-by: Wenwei Tao <ww.tao0320@gmail.com>\nSigned-off-by: Matias Bjørling <m@bjorling.me>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/16c6d048d7b74249a4387700887e8adb13028866"},{"sha":"bba7f40a029c1e2966146e3a021b3deaf5639904","author":{"email":"10f507e71980d391161c979d35809259368b6261@lightnvm.io","name":"Javier González"},"message":"lightnvm: warn if irqs are disabled in lock laddr\n\nAdd a warning if irqs are disabled when locking a new address in rrpc.\nThe typical path to a new request does not disable irqs, but this is not\nguaranteed in the future.\n\nSigned-off-by: Javier González <javier@cnexlabs.com>\nSigned-off-by: Matias Bjørling <m@bjorling.me>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/bba7f40a029c1e2966146e3a021b3deaf5639904"},{"sha":"3704e098cc1a4c2cabcf4e1cfbbff38b4bfb1ea7","author":{"email":"10f507e71980d391161c979d35809259368b6261@lightnvm.io","name":"Javier González"},"message":"lightnvm: fix request intersection locking in rrpc\n\nThis patch fixes an error on the calculation of intersecting logical\naddresses; it contemplates the case where a new request including\nseveral addresses intersects with a single locked address. This case is\ntypical when multiple pages are sent in a new request, while GC - which\nat the moment sends one address at the time - is running.\n\nSigned-off-by: Javier González <javier@cnexlabs.com>\nSigned-off-by: Matias Bjørling <m@bjorling.me>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/3704e098cc1a4c2cabcf4e1cfbbff38b4bfb1ea7"},{"sha":"6dde1d6c9094a7c20a680aa2196ad6d032ec7ded","author":{"email":"6b0d31c0d563223024da45691584643ac78c96e8@bjorling.me","name":"Matias Bjørling"},"message":"lightnvm: check overflow and correct mlc pairs\n\nThe specification currently limits the number of MLC pairs to 886. Make\nsure that a device is unable to be instantiate if more is configured.\n\nAlso, previously the patch had the wrong math for copying MLC pairs, as\nit only copied half of the actual entries.\n\nFixes: ca5927e7ab53 \"lightnvm: introduce mlc lower page table mappings\"\nSigned-off-by: Matias Bjørling <m@bjorling.me>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/6dde1d6c9094a7c20a680aa2196ad6d032ec7ded"},{"sha":"bf64318564c43385ffc3d3dfedab5287bdf3dfdd","author":{"email":"6b0d31c0d563223024da45691584643ac78c96e8@bjorling.me","name":"Matias Bjørling"},"message":"lightnvm: allow to force mm initialization\n\nSystem block allows the device to initialize with its configured media\nmanager. The system blocks is written to disk, and read again when media\nmanager is determined. For this to work, the backend must store the\ndata. Device drivers, such as null_blk, does not have any backend\nstorage. This patch allows the media manager to be initialized without a\nstorage backend.\n\nIt also fix incorrect configuration of capabilities in null_blk, as it\ndoes not support get/set bad block interface.\n\nSigned-off-by: Matias Bjørling <m@bjorling.me>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/bf64318564c43385ffc3d3dfedab5287bdf3dfdd"},{"sha":"09954bad448791ef01202351d437abdd9497a804","author":{"email":"ed58f755cc8caaf10c3e8c731a8b86fb8f13d6cb@suse.cz","name":"Jiri Kosina"},"message":"floppy: refactor open() flags handling\n\nIn case /dev/fdX is open with O_NDELAY / O_NONBLOCK, floppy_open() immediately\nsucceeds, without performing any further media / controller preparations.\nThat's \"correct\" wrt. the NODELAY flag, but is hardly correct wrt. the rest\nof the floppy driver, that is not really O_NONBLOCK ready, at all. Therefore\nit's not too surprising, that subsequent attempts to work with the\nfiledescriptor produce bad results. Namely, syzkaller tool has been able\nto livelock mmap() on the returned fd to keep waiting on the page unlock\nbit forever.\n\nQuite frankly, I have trouble defining what non-blocking behavior would be for\nfloppies. Is waiting ages for the driver to actually succeed reading a sector\nblocking operation? Is waiting for drive motor to start blocking operation? How\nabout in case of virtualized floppies?\n\nOne option would be returning EWOULDBLOCK in case O_NDLEAY / O_NONBLOCK is\nbeing passed to open(). That has a theoretical potential of breaking some\narcane and archaic userspace though.\n\nLet's take a more conservative aproach, and accept the O_NDLEAY flag, and let\nthe driver behave as usual.\n\nWhile at it, clean up a bit handling of !(mode & (FMODE_READ|FMODE_WRITE))\ncase and return EINVAL instead of succeeding as well.\n\nSpotted by syzkaller tool.\n\nReported-by: Dmitry Vyukov <dvyukov@google.com>\nTested-by: Dmitry Vyukov <dvyukov@google.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/09954bad448791ef01202351d437abdd9497a804"},{"sha":"d57d611505d911c6f9f81cd9bd6dbd293d66dd9f","author":{"email":"dd01aaba8a1d2aab66d392335eb1a6c1b73d4fed@linux.intel.com","name":"Stephane Gasparini"},"message":"kernel/fs: fix I/O wait not accounted for RW O_DSYNC\n\n When a process is doing Random Write with O_DSYNC flag\n the I/O wait are not accounted in the kernel (get_cpu_iowait_time_us).\n This is preventing the governor or the cpufreq driver to account for\n I/O wait and thus use the right pstate\n\nSigned-off-by: Stephane Gasparini <stephane.gasparini@linux.intel.com>\nSigned-off-by: Philippe Longepe <philippe.longepe@linux.intel.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/d57d611505d911c6f9f81cd9bd6dbd293d66dd9f"},{"sha":"21d147880e4895e645f890904784b079f1ba76f4","author":{"email":"923f7720577207a44b32e59bbfbea59d27f1ae8e@lst.de","name":"Christoph Hellwig"},"message":"nvme: fix Kconfig description for BLK_DEV_NVME_SCSI\n\nSigned-off-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/21d147880e4895e645f890904784b079f1ba76f4"},{"sha":"39a169b62b415390398291080dafe63aec751e0a","author":{"email":"dbfa0240d5f642b4c1caf29a6c9a7befb57d96a6@profitbricks.com","name":"Roman Pen"},"message":"block: fix module reference leak on put_disk() call for cgroups throttle\n\nget_disk(),get_gendisk() calls have non explicit side effect: they\nincrease the reference on the disk owner module.\n\nThe following is the correct sequence how to get a disk reference and\nto put it:\n\n    disk = get_gendisk(...);\n\n    /* use disk */\n\n    owner = disk->fops->owner;\n    put_disk(disk);\n    module_put(owner);\n\nfs/block_dev.c is aware of this required module_put() call, but f.e.\nblkg_conf_finish(), which is located in block/blk-cgroup.c, does not put\na module reference.  To see a leakage in action cgroups throttle config\ncan be used.  In the following script I'm removing throttle for /dev/ram0\n(actually this is NOP, because throttle was never set for this device):\n\n    # lsmod | grep brd\n    brd                     5175  0\n    # i=100; while [ $i -gt 0 ]; do echo \"1:0 0\" > \\\n        /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); \\\n    done\n    # lsmod | grep brd\n    brd                     5175  100\n\nNow brd module has 100 references.\n\nThe issue is fixed by calling module_put() just right away put_disk().\n\nSigned-off-by: Roman Pen <roman.penyaev@profitbricks.com>\nCc: Gi-Oh Kim <gi-oh.kim@profitbricks.com>\nCc: Tejun Heo <tj@kernel.org>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: linux-block@vger.kernel.org\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/39a169b62b415390398291080dafe63aec751e0a"},{"sha":"a514379b0c77085074abf01c525a850f6d99926e","author":{"email":"6b0d31c0d563223024da45691584643ac78c96e8@bjorling.me","name":"Matias Bjørling"},"message":"null_blk: oops when initializing without lightnvm\n\nIf the LightNVM subsystem is not compiled into the kernel, and the\nnull_blk device driver requests lightnvm to be initialized. The call to\nnvm_register fails and the null_add_dev function cleans up the\ninitialization. However, at this point the null block device has\nalready been added to the nullb_list and thus a second cleanup will\noccur when the function has returned, that leads to a double call to\nblk_cleanup_queue.\n\nSigned-off-by: Matias Bjørling <m@bjorling.me>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/a514379b0c77085074abf01c525a850f6d99926e"},{"sha":"5f009d3f8e6685fe8c6215082c1696a08b411220","author":{"email":"695e2a2c1e39535baaa147c5eb4e5da14054d59f@intel.com","name":"Keith Busch"},"message":"block: Initialize max_dev_sectors to 0\n\nThe new queue limit is not used by the majority of block drivers, and\nshould be initialized to 0 for the driver's requested settings to be used.\n\nSigned-off-by: Keith Busch <keith.busch@intel.com>\nAcked-by: Martin K. Petersen <martin.petersen@oracle.com>\nReviewed-by: Sagi Grimberg <sagig@mellanox.com>\nReviewed-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/5f009d3f8e6685fe8c6215082c1696a08b411220"},{"sha":"a59e0f5795fe52dad42a99c00287e3766153b312","author":{"email":"695e2a2c1e39535baaa147c5eb4e5da14054d59f@intel.com","name":"Keith Busch"},"message":"blk-mq: End unstarted requests on dying queue\n\nGo directly to ending a request if it wasn't started. Previously, completing a\nrequest may invoke a driver callback for a request it didn't initialize.\n\nSigned-off-by: Keith Busch <keith.busch@intel.com>\nReviewed-by: Sagi Grimberg <sagig@mellanox.com>\nReviewed-by: Johannes Thumshirn <jthumshirn at suse.de>\nAcked-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/a59e0f5795fe52dad42a99c00287e3766153b312"},{"sha":"4f76d0e49835d3da33aa54811157421f7061805e","author":{"email":"695e2a2c1e39535baaa147c5eb4e5da14054d59f@intel.com","name":"Keith Busch"},"message":"NVMe: Fix io incapable return values\n\nThe function returns true when the controller can't handle IO.\n\nSigned-off-by: Keith Busch <keith.busch@intel.com>\nReviewed-by: Sagi Grimberg <sagig@mellanox.com>\nReviewed-by: Johannes Thumshirn <jthumshirn@suse.de>\nAcked-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/4f76d0e49835d3da33aa54811157421f7061805e"},{"sha":"ef2d4615c59efb312e531a5e949970f37ca1c841","author":{"email":"695e2a2c1e39535baaa147c5eb4e5da14054d59f@intel.com","name":"Keith Busch"},"message":"NVMe: Allow request merges\n\nIt is generally more efficient to submit larger IO.\n\nSigned-off-by: Keith Busch <keith.busch@intel.com>\nReviewed-by: Johannes Thumshirn <jthumshirn@suse.de>\nReviewed-by: Sagi Grimberg <sagig@mellanox.com>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/ef2d4615c59efb312e531a5e949970f37ca1c841"}]}