lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 25 Apr 2018 15:00:39 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc:     syzbot <syzbot+40b7287c2dc987c48c81@...kaller.appspotmail.com>,
        syzkaller-bugs@...glegroups.com, Michal Hocko <mhocko@...e.com>,
        linux-kernel@...r.kernel.org,
        Vegard Nossum <vegard.nossum@...il.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        Jiri Slaby <jslaby@...e.com>,
        Peter Hurley <peter@...leysoftware.com>,
        One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] tty: Use __GFP_NOFAIL for tty_ldisc_get()

On Wed, Apr 25, 2018 at 08:12:31PM +0900, Tetsuo Handa wrote:
> From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
> 
> syzbot is reporting crashes triggered by memory allocation fault injection
> at tty_ldisc_get() [1]. As an attempt to handle OOM in a graceful way, we
> have tried commit 5362544bebe85071 ("tty: don't panic on OOM in
> tty_set_ldisc()"). But we reverted that attempt by commit a8983d01f9b7d600
> ("Revert "tty: don't panic on OOM in tty_set_ldisc()"") due to reproducible
> crash. We should spend resource for finding and fixing race condition bugs
> rather than complicate error paths for 2 * sizeof(void *) bytes allocation
> failure.
> 
> [1] https://syzkaller.appspot.com/bug?id=489d33fa386453859ead58ff5171d43772b13aa3
> 
> Signed-off-by: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
> Reported-by: syzbot <syzbot+40b7287c2dc987c48c81@...kaller.appspotmail.com>
> Cc: Michal Hocko <mhocko@...e.com>
> Cc: Vegard Nossum <vegard.nossum@...il.com>
> Cc: Dmitry Vyukov <dvyukov@...gle.com>
> Cc: Jiri Slaby <jslaby@...e.com>
> Cc: Peter Hurley <peter@...leysoftware.com>
> Cc: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
> Cc: Linus Torvalds <torvalds@...ux-foundation.org>
> Cc: stable <stable@...r.kernel.org>
> ---
>  drivers/tty/tty_ldisc.c | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c
> index 050f4d6..971a37e 100644
> --- a/drivers/tty/tty_ldisc.c
> +++ b/drivers/tty/tty_ldisc.c
> @@ -176,12 +176,11 @@ static struct tty_ldisc *tty_ldisc_get(struct tty_struct *tty, int disc)
>  			return ERR_CAST(ldops);
>  	}
>  
> -	ld = kmalloc(sizeof(struct tty_ldisc), GFP_KERNEL);
> -	if (ld == NULL) {
> -		put_ldops(ldops);
> -		return ERR_PTR(-ENOMEM);
> -	}
> -
> +	/*
> +	 * There is no way to handle allocation failure of only 16 bytes.
> +	 * Let's simplify error handling and save more memory.
> +	 */
> +	ld = kmalloc(sizeof(struct tty_ldisc), GFP_KERNEL | __GFP_NOFAIL);
>  	ld->ops = ldops;
>  	ld->tty = tty;
>  

Yes, this is the thing to do, thanks, I'll go queue this up now.

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ