* Re: Patch "x86/fpu: Don't export __kernel_fpu_{begin,end}()" has been added to the 4.19-stable tree
[not found] ` <20190502080204.GA2832@kroah.com>
@ 2019-05-02 14:42 ` Andy Lutomirski
2019-05-02 14:54 ` Greg KH
0 siblings, 1 reply; 2+ messages in thread
From: Andy Lutomirski @ 2019-05-02 14:42 UTC (permalink / raw)
To: Greg KH, LKML
Cc: Andy Lutomirski, 20181129150210.2k4mawt37ow6c2vq,
Jason A. Donenfeld, Ard Biesheuvel, Sebastian Andrzej Siewior,
Borislav Petkov, Dave Hansen, H. Peter Anvin, Ingo Molnar,
Nicolai Stange, Paolo Bonzini, Rik van Riel, Radim Krcmar,
Thomas Gleixner, X86 ML, stable-commits
On Thu, May 2, 2019 at 1:02 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Wed, May 01, 2019 at 10:47:07AM -0700, Andy Lutomirski wrote:
> > On Mon, Apr 29, 2019 at 6:36 AM <gregkh@linuxfoundation.org> wrote:
> > >
> > >
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > x86/fpu: Don't export __kernel_fpu_{begin,end}()
> > >
> > > to the 4.19-stable tree which can be found at:
> > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > Why? ISTM the only possible effect is to break out-of-tree modules.
> > I have no objection to breaking such modules if we need to, but, in
> > this case, I don't see the benefit.
>
> The "benefit" is that people keep complaining that newer kernels do not
> have this api for some reason and that it is a "regression", which
> completely does not understand how the kernel handles internal apis.
I suppose that's a reasonable point. But maybe we should actually
give these modules a credible alternative first? I just send a patch.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Patch "x86/fpu: Don't export __kernel_fpu_{begin,end}()" has been added to the 4.19-stable tree
2019-05-02 14:42 ` Patch "x86/fpu: Don't export __kernel_fpu_{begin,end}()" has been added to the 4.19-stable tree Andy Lutomirski
@ 2019-05-02 14:54 ` Greg KH
0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2019-05-02 14:54 UTC (permalink / raw)
To: Andy Lutomirski
Cc: LKML, 20181129150210.2k4mawt37ow6c2vq, Jason A. Donenfeld,
Ard Biesheuvel, Sebastian Andrzej Siewior, Borislav Petkov,
Dave Hansen, H. Peter Anvin, Ingo Molnar, Nicolai Stange,
Paolo Bonzini, Rik van Riel, Radim Krcmar, Thomas Gleixner,
X86 ML, stable-commits
On Thu, May 02, 2019 at 07:42:21AM -0700, Andy Lutomirski wrote:
> On Thu, May 2, 2019 at 1:02 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, May 01, 2019 at 10:47:07AM -0700, Andy Lutomirski wrote:
> > > On Mon, Apr 29, 2019 at 6:36 AM <gregkh@linuxfoundation.org> wrote:
> > > >
> > > >
> > > > This is a note to let you know that I've just added the patch titled
> > > >
> > > > x86/fpu: Don't export __kernel_fpu_{begin,end}()
> > > >
> > > > to the 4.19-stable tree which can be found at:
> > > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > Why? ISTM the only possible effect is to break out-of-tree modules.
> > > I have no objection to breaking such modules if we need to, but, in
> > > this case, I don't see the benefit.
> >
> > The "benefit" is that people keep complaining that newer kernels do not
> > have this api for some reason and that it is a "regression", which
> > completely does not understand how the kernel handles internal apis.
>
> I suppose that's a reasonable point. But maybe we should actually
> give these modules a credible alternative first? I just send a patch.
That's your call, it's your code :)
thanks,
greg k-h
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-05-02 14:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1556544977149154@kroah.com>
[not found] ` <CALCETrVjhVXYA4B6zFzbH14wBXZcNMAeM8YxdRh3RLHxVVde_g@mail.gmail.com>
[not found] ` <20190502080204.GA2832@kroah.com>
2019-05-02 14:42 ` Patch "x86/fpu: Don't export __kernel_fpu_{begin,end}()" has been added to the 4.19-stable tree Andy Lutomirski
2019-05-02 14:54 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox