On Thu, 2017-02-02 at 13:59 +0100, Dmitry Vyukov wrote:

Right, I can confirm that this is not happening on net-next tip
(62e13097c46c69dbd7544ab2cd585ccf48f360a4).
I reproduced it on a random month old commit on net-next, though
(23a8ed4a624324dc696c328f09bd502c4a3816f0). Let's consider that this
is accidentally fixed by something in that range.

This also might depend on the .config 

I tried 23a8ed4a624324dc696c328f09bd502c4a3816f0 and could not trigger
the warning .

Thanks.