On Thu, Nov 10, 2016 at 3:19 PM, Richard Weinberger <[email protected]> wrote: > Can you please reply to Sebastian's patch series and explain him how you > trigger > that error? > I don't have a gcc broken by Debian on my machine right now.
I'm not sure how to reply to his patch series directly since I'm not subscribed to lkml (I imagine I can set headers manually, such that things get appropriately threaded, but for now let me just reply here). I don't think there's much to it. It seems like any use of `current_text_addr()` in `ARCH=um` build will cause this problem, there's just not very many such uses in the code base. I believe this particular problem should be reproducible as long as CONFIG_INET is set for an `ARCH=um` build.
