[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+aDFD6O48nV5J9UpXLiNpTPuSFoBQ4HVC+Kg1tM_KFEiQ@mail.gmail.com>
Date: Thu, 27 Sep 2018 17:29:11 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Christopher Lameter <cl@...ux.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, Sep 27, 2018 at 5:22 PM, Christopher Lameter <cl@...ux.com> wrote:
> On Thu, 27 Sep 2018, Dmitry Vyukov wrote:
>
>> On Thu, Sep 27, 2018 at 4:16 PM, Christopher Lameter <cl@...ux.com> wrote:
>> > 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.
>>
>> It's here:
>> https://lore.kernel.org/patchwork/patch/992660/
>>
>
> Please post on the mailing list
It is on the mailing lists:
https://lkml.org/lkml/2018/9/27/802
> and NAK to the patch. Testing against
> KMALLOC_MAX_CACHE_SIZE is not ok.
Why?
Powered by blists - more mailing lists