On Tue, Aug 1, 2017 at 8:40 PM, Kees Cook <keescook@xxxxxxxxxxxx> wrote:
>>
>> I don't know why this has turned up now. I have just left it broken
>> for now and would appreciate any fix.
>
> Thanks for the heads-up! I'm not sure why this suddenly appeared
> either, but Arnd has sent a patch for this now.
The main difference I see that can impact gcc's optimization steps is the
unreachable() that was there in BUG() but is absent in WARN().
It's possible that the compiler decided that the entire code path leading
up to the unreachable() couldn't happen, so it dropped the
__read_overflow2() call as well.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
