[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150917071504.GA12316@nazgul.tnic>
Date: Thu, 17 Sep 2015 09:15:04 +0200
From: Borislav Petkov <bp@...en8.de>
To: Josh Boyer <jwboyer@...oraproject.org>,
Greg KH <gregkh@...uxfoundation.org>
Cc: Philip Müller <philm@...jaro.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
Sudeep Holla <sudeep.holla@....com>,
Guenter Roeck <linux@...ck-us.net>, manjaro-dev@...jaro.org,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Andre Przywara <andre.przywara@....com>,
Borislav Petkov <bp@...e.de>
Subject: Re: [linux41] regression with 'x86/cacheinfo: Move cacheinfo sysfs
code to generic infrastructure' on AMD i686
On Wed, Sep 16, 2015 at 07:52:47PM -0400, Josh Boyer wrote:
> On Sun, Jul 26, 2015 at 10:42 AM, Borislav Petkov <bp@...en8.de> wrote:
> > On Sun, Jul 26, 2015 at 12:54:55PM +0200, Philip Müller wrote:
> >> I can confirm your patch working. However, it might be good to use yours
> >> and Thomas' in combination to solve this properly.
> >
> > Please do not top-post.
> >
> > We could use Thomas' too although from looking at it,
> > detect_cache_attributes() allocates a per-CPU per_cpu_cacheinfo thing
> > for each CPU. By the time we hit cache_shared_cpu_map_remove() in
> > free_cache_attributes(), those per_cpu_cacheinfo(cpu) things are still
> > allocated. We kfree them in the next step only.
> >
> > But I like the moving of the check from the CPU hotplug callback to
> > free_cache_attributes().
> >
> > So I'll merge the two patches and write up a proper commit message,
> > unless someone objects.
> >
> > I'll add your Tested-by too.
>
> Did this actually happen? I don't see either fix in Linus' tree yet,
> the merge window is closed, and the bug happens on 4.1 and 4.2 stable
> kernels..
Greg wanted to pick it up...
Greg, what's up?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists