linux-kernel - Re: [PATCH] auxdisplay: img-ascii-lcd: add missing sentinel entry in img_ascii_lcd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 6 Mar 2017 11:40:51 -0800
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     Javier Martinez Canillas <javier@....samsung.com>
Cc:     Paul Burton <paul.burton@...tec.com>,
        Ralf Baechle <ralf@...ux-mips.org>,
        James Hogan <james.hogan@...tec.com>,
        Miguel Ojeda Sandonis <miguel.ojeda.sandonis@...il.com>,
        linux-kernel@...r.kernel.org,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] auxdisplay: img-ascii-lcd: add missing sentinel entry in
 img_ascii_lcd_matches

On Mon, Mar 06, 2017 at 03:58:04PM -0300, Javier Martinez Canillas wrote:
> Hello Paul,
> 
> On 03/06/2017 03:54 PM, Paul Burton wrote:
> > Hi Javier,
> > 
> > On Monday, 6 March 2017 10:09:09 PST Javier Martinez Canillas wrote:
> >> On 02/24/2017 06:56 PM, Paul Burton wrote:
> >>> On Monday, 20 February 2017 21:39:11 PST Dmitry Torokhov wrote:
> >>>> The OF device table must be terminated, otherwise we'll be walking past
> >>>> it and into areas unknown.
> >>>>
> >>>> This causes KASAN errors reported by 0day kernel testing robot.
> >>>>
> >>>> Reported-by: Fengguang Wu <fengguang.wu@...el.com>
> >>>> Tested-by: Fengguang Wu <fengguang.wu@...el.com>
> >>>> Fixes: 0cad855fbd08 ("auxdisplay: img-ascii-lcd: driver for simple
> >>>> ASCII...") Cc: stable@...r.kernel.org
> >>>> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@...il.com>
> >>>
> >>> An essentially identical patch was already submitted over here:
> >>>
> >>> https://patchwork.kernel.org/patch/9493973/
> >>>
> >>> I'm not sure how it ought to get into mainline - since the driver went
> >>> through the MIPS tree perhaps this fix can too?
> >>
> >> Do you know who should I ping about it? It has been posted a couple of
> >> months ago.
> > 
> > If it can go through the MIPS tree that would be Ralf (who I copied 
> > previously). If not then it's Miguel as auxdisplay maintainer.
> >
> 
> Ok, Thanks for your help. I just asked in case MAINTAINERS wasn't up-to-date
> since the patches were posted a long time ago and had no feedback.

Maybe we could get akpm pick it up?

Thanks.

-- 
Dmitry