mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: syzbot 
	<bot+57840b4d2cc5c46981d5b9e07c9b7b06d5bcf064@syzkaller.appspotmail.com>,
	jslaby@suse.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: kernel panic: n_tty: init_tty
Date: Sun, 5 Nov 2017 14:04:39 -0800	[thread overview]
Message-ID: <20171105220439.GA11631@zzz.localdomain> (raw)
In-Reply-To: <20171105103434.GC1487@kroah.com>

On Sun, Nov 05, 2017 at 11:34:34AM +0100, Greg KH wrote:
> On Sun, Nov 05, 2017 at 01:05:02AM -0800, syzbot wrote:
> > Hello,
> > 
> > syzkaller hit the following crash on
> > b5ac3beb5a9f0ef0ea64cd85faf94c0dc4de0e42
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> > compiler: gcc (GCC) 7.1.1 20170620
> > .config is attached
> > Raw console output is attached.
> 
> And again, this would be nicer to provide something that I could
> reproduce this with...
> 
> thanks,
> 
> greg k-h
> 

I just saw the same crash running syzkaller.  It was preceded by a fault
injection in tty_ldisc_get() here:

        ld = kmalloc(sizeof(struct tty_ldisc), GFP_KERNEL);
        if (ld == NULL) {
                put_ldops(ldops);
                return ERR_PTR(-ENOMEM);
        }

So then it panics at:

        if (IS_ERR(ld))
                panic("n_tty: init_tty");

It seems that syzkaller needs to do a better job reproducing and reporting bugs
that are only reproducible with fault injection.  But either way, this is a bug;
panic() is not an acceptable way of handling kmalloc failure.

Eric

  reply	other threads:[~2017-11-05 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <94eb2c0630b4161a5e055d38a2e3@google.com>
2017-11-05 10:34 ` Greg KH
2017-11-05 22:04   ` Eric Biggers [this message]
2017-11-06 12:14     ` Dmitry Vyukov
2017-11-06 12:37       ` Greg KH
2017-11-06 12:33     ` Greg KH
2017-11-06 17:26       ` Eric Biggers
2017-11-07 10:37         ` Dmitry Vyukov
2017-11-07 17:18         ` Alan Cox
2017-11-06 12:13   ` Dmitry Vyukov
2018-04-05 10:40   ` [PATCH] tty: Don't call panic() at tty_ldisc_init() Tetsuo Handa
2018-04-25 11:04     ` kernel panic: n_tty: init_tty Tetsuo Handa
2017-12-29  8:32 ` syzbot

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=20171105220439.GA11631@zzz.localdomain \
    --to=ebiggers3@gmail.com \
    --cc=bot+57840b4d2cc5c46981d5b9e07c9b7b06d5bcf064@syzkaller.appspotmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@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

all inboxes | Powered by JetHome®