summaryrefslogtreecommitdiffstats
path: root/net/can
diff options
context:
space:
mode:
authorTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>2018-04-05 19:40:16 +0900
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-04-23 11:05:52 +0200
commit903f9db10f18f735e62ba447147b6c434b6af003 (patch)
treeb05ae90ca1e626fa743c1edef9fd915378469b1e /net/can
parent598c2d41ff44889dd8eced4f117403e472158d85 (diff)
downloadlinux-stable-903f9db10f18f735e62ba447147b6c434b6af003.tar.gz
linux-stable-903f9db10f18f735e62ba447147b6c434b6af003.tar.bz2
linux-stable-903f9db10f18f735e62ba447147b6c434b6af003.zip
tty: Don't call panic() at tty_ldisc_init()
syzbot is reporting kernel panic [1] triggered by memory allocation failure at tty_ldisc_get() from tty_ldisc_init(). But since both tty_ldisc_get() and caller of tty_ldisc_init() can cleanly handle errors, tty_ldisc_init() does not need to call panic() when tty_ldisc_get() failed. [1] https://syzkaller.appspot.com/bug?id=883431818e036ae6a9981156a64b821110f39187 Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> Reported-by: syzbot <syzkaller@googlegroups.com> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Jiri Slaby <jslaby@suse.com> Cc: stable <stable@vger.kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/can')
0 files changed, 0 insertions, 0 deletions