[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ykysm3EJd3XLrzyr@phenom.ffwll.local>
Date: Tue, 5 Apr 2022 22:54:51 +0200
From: Daniel Vetter <daniel@...ll.ch>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: Daniel Vetter <daniel.vetter@...ll.ch>,
DRI Development <dri-devel@...ts.freedesktop.org>,
Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
linux-fbdev@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Daniel Vetter <daniel.vetter@...el.com>,
Daniel Vetter <daniel@...ll.ch>,
Claudio Suarez <cssk@...-c.es>, Du Cheng <ducheng2@...il.com>,
Thomas Zimmermann <tzimmermann@...e.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2 06/19] fbcon: Use delayed work for cursor
On Thu, Feb 10, 2022 at 08:43:36PM +0900, Tetsuo Handa wrote:
> On 2022/02/09 6:08, Daniel Vetter wrote:
> > @@ -714,6 +700,8 @@ static int con2fb_acquire_newinfo(struct vc_data *vc, struct fb_info *info,
> > ops = kzalloc(sizeof(struct fbcon_ops), GFP_KERNEL);
> > if (!ops)
> > err = -ENOMEM;
> > +
> > + INIT_DELAYED_WORK(&ops->cursor_work, fb_flashcursor);
> > }
> >
> > if (!err) {
>
> Memory allocation fault injection will hit NULL pointer dereference.
The error handling here is convoluted and I got this wrong, but a later
patch to extract an fbcon_open() helper fixes it. I'll fix this small
bisect issue for v3 anyway, thanks for taking a look at the patches.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists