[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201102111248.GA1558630@PWN>
Date: Mon, 2 Nov 2020 06:12:48 -0500
From: Peilin Ye <yepeilin.cs@...il.com>
To: Daniel Vetter <daniel@...ll.ch>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
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 v2 2/2] tty/vt: Avoid passing struct console_font_op to
con_font_copy()
On Mon, Nov 02, 2020 at 11:10:44AM +0100, Daniel Vetter wrote:
> I'm not sure switching from int to unsigned just here makes much sense.
> All the console code is still using int con to index all the various
> arrays (I just checked fbcon.c code), and using int to index arrays is
> pretty standard. As long as we have the con < 0 check to catch evil
> userspace.
>
> There's still the switch from op to int for con_font_copy, but I think
> that's better done as part of the larger cleanup we already discussed. And
> then maybe also include patch 1 from this series in that rework.
I see. I think at the moment there's not much we can do for
con_font_get/set/default(). _get() and _default() use *op, and _set()
uses all except one field of *op. Maybe we can change the type of *op
from console_font_op to font_desc, after cleaning up everything else?
Peilin
Powered by blists - more mailing lists