linux-kernel - Re: [v4.14-rc8 ghes_copy_tofrom_phys] BUG: sleeping function called from invalid context at lib/ioremap.c:165

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CA+55aFzvuFK3X9xwanyE=4DAuHnjHF9YNB2q2c2r1z+c9aWO_A@mail.gmail.com>
Date:   Mon, 6 Nov 2017 14:57:20 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Fengguang Wu <fengguang.wu@...el.com>,
        James Morse <james.morse@....com>
Cc:     Tyler Baicar <tbaicar@...eaurora.org>,
        Borislav Petkov <bp@...e.de>, Len Brown <lenb@...nel.org>,
        Tony Luck <tony.luck@...el.com>,
        Huang Ying <ying.huang@...el.com>,
        Chen Gong <gong.chen@...ux.intel.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Will Deacon <will.deacon@....com>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Linux ACPI <linux-acpi@...r.kernel.org>,
        Timur Tabi <timur@...eaurora.org>,
        Mark Rutland <mark.rutland@....com>
Subject: Re: [v4.14-rc8 ghes_copy_tofrom_phys] BUG: sleeping function called
 from invalid context at lib/ioremap.c:165

On Mon, Nov 6, 2017 at 2:46 PM, Fengguang Wu <fengguang.wu@...el.com> wrote:
>
> I can see that in RC8, too:

James Morse posted a new version of his series to fix this, and it's
gotten a few tests, but not a lot. Since you clearly have GHES support
on at least some of your machines, it might be worth adding that
series from James to 0day testing.

The patches look good to me, and I assume I'll be be getting it
through Rafael from the ACPI tree (which is how the other ghes code
reaches me), but maybe by now for 4.15 with a stable backport.

The actual problem is definitely not new. Only the warning message.

So the code should work as well as it ever has, which may or may not
be saying a lot. It might be worth fixing for 4.14 just to not scare
people too much with messages, but at the same time it's not a
_functional_ regression.

            Linus