On 17/07/18 16:58, Kevin Lyda wrote:
Lastly, my question is about USB but I've noted this affects other
configurations. In spite of that your responses have solely focused on
USB. As I've pointed out you can get this error with dm-crypt
(https://lists.debian.org/debian-kernel/2015/09/msg00033.html) which
includes a link to an as yet not accepted patch to fix this issue
generally (https://www.redhat.com/archives/dm-devel/2012-May/msg00159.html).
And obviously this issue could affect other mixed bus deployments.
Again, if your goals in this project are not reliable, robust storage
but something else (which is totally valid - as I said, you do you),
then feel free to keep trashing USB and ignoring the issue. That's
cool. I'm fine with that. But I operate under the assumption that your
goal is reliable, robust storage and that you'd want feedback on how
to get there. The more limited RAID1 patch I mentioned earlier in this
thread or Overstreet's more general patch might be ways to get there;
to get away from silently, with no direct warning, of corrupting data.
I may be off base here, but wasn't this problem solved in the mainline
kernel back in 2015 starting with :
commit 54efd50bfd873e2dbf784e0b21a8027ba4299a3e
Author: Kent Overstreet <kent.overstreet@xxxxxxxxx>
Date: Thu Apr 23 22:37:18 2015 -0700
block: make generic_make_request handle arbitrarily sized bios
I certainly remember the discussion surrounding these patches and the
desire to get them in to prevent this particular issue.
Regards,
Brad
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
