On Mon, Feb 15, 2016 at 12:46:51PM -0500, Mike Marshall wrote: > I pushed the list_del up to the kernel.org for-next branch... > > And I've been running tests with the CRUDE bandaid... weird > results... > > No oopses, no WARN_ONs... I was running dbench and ls -R > or find and kill-minus-nining different ones of them with no > perceived resulting problems, so I moved on to signalling > the client-core to abort... it restarted numerous times, > and then stuff wedged up differently than I've seen before. There are other problems with that thing (starting with the fact that retrying readdir/wait_for_direct_io can try to grab a slot despite the bufmap winding down). OK, at that point I think we should try to see if bufmap rewrite works - I've rebased on top of your branch and pushed (head at 8c3bc9a). Bufmap rewrite is really completely untested - it's done pretty much blindly and I'd be surprised as hell if it has no brainos at the first try. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
