[ +cc's, intentional top post ] Hello linux-raid list, please see below: A problem where bio_trim() dereferences a NULL pointer via bio->bi_iter.bi_size (0+0x28) has been reported at least three times when passing DISCARDs into raid1's. I could be wrong here, but I'm guessing the cause of these three reports are the same: [2014-02-04] https://bugzilla.redhat.com/show_bug.cgi?id=1061339 [2016-01-13] http://www.spinics.net/lists/linux-bcache/msg03335.html https://bugzilla.kernel.org/show_bug.cgi?id=110771 [2016-03-25] http://thread.gmane.org/gmane.linux.kernel.bcache.devel/3607 [this thread] https://bugzilla.kernel.org/show_bug.cgi?id=114871 Is there something that needs to be done differently with DISCARD bio's, perhaps related to splitting? We added BUG_ON(!bio) in bcache's prio_io() function (see backtrace below) and didn't trip, so we know that bcache isn't passing null bio pointers. Perhaps there is an issue in either of blk_queue_split() or md_make_request() even before it gets to raid1_make_request()? Please add Cc's for anyone who might be able to help solve this problem. Thanks you for your help! -- Eric Wheeler On Fri, 25 Mar 2016, Sebastian Roesner wrote: > Hi Eric, > > Am 25.03.2016 um 05:18 schrieb Eric Wheeler: > > Please send this output: > > > > tail /sys/block/md2/queue/discard_* > > # tail /sys/block/md2/queue/discard_* > ==> /sys/block/md2/queue/discard_granularity <== > 4096 > > ==> /sys/block/md2/queue/discard_max_bytes <== > 2147450880 > > ==> /sys/block/md2/queue/discard_max_hw_bytes <== > 2147450880 > > ==> /sys/block/md2/queue/discard_zeroes_data <== > 0 > > root@gropius:/home/sroesner# echo /dev/md2 > /sys/fs/bcache/register > sroesner@gropius:~$ > > -> it killed my bash. > > Trace with patches and BUG_ON patch: > > [ 172.660142] BUG: unable to handle kernel NULL pointer dereference at > 0000000000000028 > [ 172.660229] IP: [<ffffffff811e53b4>] bio_trim+0xf/0x2a > [ 172.660289] PGD 7faf3e067 PUD 7f9279067 PMD 0 > [ 172.660399] Oops: 0000 [#1] SMP > [...] > [ 172.664780] Call Trace: > [ 172.664813] [<ffffffffa007f3be>] ? raid1_make_request+0x2e8/0xad7 [raid1] > [ 172.664846] [<ffffffff811f07da>] ? blk_queue_split+0x377/0x3d4 > [ 172.664880] [<ffffffffa005fb5f>] ? md_make_request+0xf6/0x1e9 [md_mod] > [ 172.664912] [<ffffffff811eb860>] ? generic_make_request+0xb5/0x155 > [ 172.664947] [<ffffffffa0445c89>] ? prio_io+0x85/0x95 [bcache] > [ 172.664981] [<ffffffffa0448252>] ? register_cache_set+0x355/0x8d0 [bcache] > [ 172.665016] [<ffffffffa04497d3>] ? register_bcache+0x1006/0x1174 [bcache] > > See http://pastebin.com/6CHtky2x for complete traces. > > Sebastian > -- > To unsubscribe from this list: send the line "unsubscribe linux-bcache" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html