On Mon, Mar 21, 2016 at 7:24 PM, Chris Mason <[email protected]> wrote: > > Hmmm, rereading my answer I realized I didn't actually answer. I really > think this is fixed. I left the warning only because I originally > expected something much more exotic.
Ok. It's more that you said the top commit fixes a problem, and the
only case where the top commit makes a difference it will also do that
WARN_ON_ONCE.
But it's pulled, test-built, and pushed out now.
Linus
