linux-kernel - Re: [PATCH] um: Fix compile failure due to current_text

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABV8kRzxbmZrdBwky1=VHyPgH4eB9CZpLHgRMTxOhfsp6ETdGQ@mail.gmail.com>
Date:   Thu, 10 Nov 2016 15:46:01 -0500
From:   Keno Fischer <keno@...iacomputing.com>
To:     Richard Weinberger <richard@....at>
Cc:     linux-kernel@...r.kernel.org, jdike@...toit.com,
        user-mode-linux-devel@...ts.sourceforge.net,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [PATCH] um: Fix compile failure due to current_text_address() definition

On Thu, Nov 10, 2016 at 3:19 PM, Richard Weinberger <richard@....at> 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.