[dm-devel] [BUG] Oops caused by FEC in 4.10.0

Sami Tolvanen samitolvanen at google.com
Fri Mar 17 15:35:03 UTC 2017


On Fri, Mar 17, 2017 at 12:45:00PM +0100, Milan Broz wrote:
> it still does take at least two minutes and tons of logs until even
> udev scan finishes on a device with incorrect FEC attributes.

If dm-verity is set up with invalid arguments so that the entire partition
is corrupt, it does take a while to determine this with FEC as it attempts
to correct both metadata and data blocks before giving up. It also depends
on the random read performance of the underlying hardware obviously.

> And once it is finished, dm-verity crashes on dm-device removal...

That's interesting, I haven't seen this before. Looks like something goes
wrong at the very end of dm_bufio_client_destroy. I'm not familiar enough
with dm_bufio internals to immediately tell why though.

> Could we please have all crucial fixes upstream?

Sorry, there are no other pending fixes remaining in our tree.

Sami




More information about the dm-devel mailing list