linux-kernel - Re: [PATCH] acpi: drop support for force

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-prev] [day] [month] [year] [list]

Message-ID: <13091724.qdDQ4T8Luo@aspire.rjw.lan>
Date:   Sat, 15 Apr 2017 00:33:06 +0200
From:   "Rafael J. Wysocki" <rjw@...ysocki.net>
To:     "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     Michal Hocko <mhocko@...nel.org>, Joey Lee <jlee@...e.com>,
        Jiri Kosina <jkosina@...e.cz>,
        Kani Toshimitsu <toshi.kani@....com>,
        Len Brown <lenb@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        linux-api@...r.kernel.org
Subject: Re: [PATCH] acpi: drop support for force_remove

On Tuesday, April 11, 2017 03:54:43 PM Rafael J. Wysocki wrote:
> On Tue, Apr 11, 2017 at 3:52 PM, Michal Hocko <mhocko@...nel.org> wrote:
> > On Tue 11-04-17 15:48:04, Rafael J. Wysocki wrote:
> >> On Tue, Apr 11, 2017 at 2:20 PM, Michal Hocko <mhocko@...nel.org> wrote:
> >> > On Tue 11-04-17 00:15:42, Rafael J. Wysocki wrote:
> > [...]
> >> >> I'll apply it if nobody has any problems with it.
> >> >
> >> > It is definitely your call but how long are we going to wait
> >> > (considering that the current behavior is obviously broken wrt memory
> >> > hotplug)?
> >>
> >> A couple of days more?  Surely not going to push it into 4.11 at this
> >> stage as it is an ABI change.
> >
> > Ohh, I didn't want to push it to 4.11 this late but having it in
> > linux-next might help to catch some users who are not following the
> > mailing list. Going to 4.12 would be really great but I wouldn't really
> > object even 4.13...
> 
> 4.12 is probably fine.  I don't see a compelling reason to sit on this
> for a whole cycle, FWIW.

It should hit linux-next next week.

Thanks,
Rafael