[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <010001661b631a3e-f398fc0a-127c-4c6e-b6ca-b2bd63bc4a9a-000000@email.amazonses.com>
Date: Thu, 27 Sep 2018 14:16:11 +0000
From: Christopher Lameter <cl@...ux.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
syzbot+87829a10073277282ad1@...kaller.appspotmail.com,
Pekka Enberg <penberg@...nel.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
Henrik Rydberg <rydberg@...math.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Linux-MM <linux-mm@...ck.org>
Subject: Re: WARNING: kmalloc bug in input_mt_init_slots
On Thu, 27 Sep 2018, Dmitry Vyukov wrote:
> On Tue, Sep 25, 2018 at 4:04 PM, Christopher Lameter <cl@...ux.com> wrote:
> > On Tue, 25 Sep 2018, Dmitry Vyukov wrote:
> >
> >> Assuming that the size is large enough to fail in all allocators, is
> >> this warning still useful? How? Should we remove it?
> >
> > Remove it. It does not make sense because we check earlier if possible
> > without the warn.
>
> Mailed "mm: don't warn about large allocations for slab" to remove the warning.
>
Hoe it arrives here at some point.
Powered by blists - more mailing lists