[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201110124946.GF401619@phenom.ffwll.local>
Date: Tue, 10 Nov 2020 13:49:46 +0100
From: Daniel Vetter <daniel@...ll.ch>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Peilin Ye <yepeilin.cs@...il.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Jiri Slaby <jirislaby@...nel.org>,
Thomas Winischhofer <thomas@...ischhofer.net>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Nicolas Pitre <nico@...xnic.net>,
"Gustavo A . R . Silva" <gustavoars@...nel.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
George Kennedy <george.kennedy@...cle.com>,
Nathan Chancellor <natechancellor@...il.com>,
Peter Rosin <peda@...ntia.se>, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-fbdev@...r.kernel.org
Subject: Re: [PATCH 1/2] console: Remove dummy con_font_op() callback
implementations
On Fri, Nov 06, 2020 at 11:50:58AM +0100, Greg Kroah-Hartman wrote:
> On Sat, Oct 31, 2020 at 03:24:41AM -0400, Peilin Ye wrote:
> > `struct console_font` is a UAPI structure, thus ideally should not be
> > used for kernel internal abstraction. Remove some dummy .con_font_set,
> > .con_font_default and .con_font_copy `struct consw` callback
> > implementations, to make it cleaner.
> >
> > Patch "fbcon: Prevent global-out-of-bounds read in fbcon_copy_font()"
> > depends on this patch, so Cc: stable.
> >
> > Cc: stable@...r.kernel.org
> > Suggested-by: Daniel Vetter <daniel@...ll.ch>
> > Signed-off-by: Peilin Ye <yepeilin.cs@...il.com>
> > ---
> > Context: https://lore.kernel.org/lkml/CAKMK7uFY2zv0adjKJ_ORVFT7Zzwn075MaU0rEU7_FuqENLR=UA@mail.gmail.com/
> >
> > drivers/usb/misc/sisusbvga/sisusb_con.c | 21 ---------------------
> > drivers/video/console/dummycon.c | 20 --------------------
> > 2 files changed, 41 deletions(-)
>
> Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Peilin, can you pls resend this together with all the other pending
patches from you? I think that's better than me trying to cherry-pick the
bits we decided to keep from random places.
Greg, ok if I just pull these in through drm-misc-next? It's a pretty bad
hairball anyway and that avoids the tree coordination issues. Only thing
that might get in the way is the vt font_copy removal, but that's in -rc3
so easy to backmerge.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists