From: Dmitry Vyukov <dvyukov@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.com>, LKML <linux-kernel@vger.kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: tty: panic in tty_ldisc_restore
Date: Fri, 3 Mar 2017 08:36:13 +0100 [thread overview]
Message-ID: <CACT4Y+YA2eku6j3q31hkKiTix-qjMyE4NFRgYmQ9_7uMD5uk9A@mail.gmail.com> (raw)
In-Reply-To: <20170302193743.GA20640@kroah.com>
On Thu, Mar 2, 2017 at 8:37 PM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>> >> This is hurting us badly.
>> >
>> > Really? How? Are you hitting this a lot? Why now and never before?
>> > Are you really out of memory?
>>
>>
>> This crashes our test bots a lot.
>> Why now... I don't have exact answer. Probably a combination of fuzzer
>> figuring out some magic sequences of syscalls and increased memory
>> consumption due to something (again maybe due to fuzzer figuring out
>> how to eat more memory).
>
> If the fuzzer is suddenly eating more memory, you should be seeing lots
> of other problems right? This can't be the only thing that has issues
> with memory allocation failures?
I remember 2 or 3 that started happenning roughly at the same time:
https://groups.google.com/forum/#!msg/syzkaller/tIx42qCVklk/fh0qjUboBgAJ
https://groups.google.com/forum/#!msg/syzkaller/vp1neyeoA8A/Is8aPdrpBgAJ
Both were quickly fixed.
There is strong bias towards failing larger, multi-page allocations.
so it's not that we are failing _all_ allocations in kernel code.
next prev parent reply other threads:[~2017-03-03 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 17:48 tty: panic in tty_ldisc_restore Dmitry Vyukov
2017-02-02 17:55 ` Greg Kroah-Hartman
2017-02-02 18:03 ` Dmitry Vyukov
2017-02-02 18:23 ` Greg Kroah-Hartman
2017-02-07 10:24 ` Dmitry Vyukov
2017-02-07 10:43 ` Greg Kroah-Hartman
2017-02-07 10:51 ` Dmitry Vyukov
2017-02-17 21:51 ` Dmitry Vyukov
2017-02-28 18:11 ` Dmitry Vyukov
2017-03-02 18:27 ` Dmitry Vyukov
2017-03-02 19:27 ` Greg Kroah-Hartman
2017-03-02 19:30 ` Dmitry Vyukov
2017-03-02 19:37 ` Greg Kroah-Hartman
2017-03-03 7:36 ` Dmitry Vyukov [this message]
2017-03-04 13:04 ` Dmitry Vyukov
2017-03-13 10:15 ` Dmitry Vyukov
2017-03-17 5:08 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACT4Y+YA2eku6j3q31hkKiTix-qjMyE4NFRgYmQ9_7uMD5uk9A@mail.gmail.com \
--to=dvyukov@google.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=syzkaller@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).