Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp577761ybi; Fri, 24 May 2019 08:11:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqy/fEI20B8DQ0sjYGzyW3ELszezzgzF7Z7temjfOHotoTZ2zVju9n6A1l+X2tcJVLe8Fntq X-Received: by 2002:a65:4544:: with SMTP id x4mr83430898pgr.323.1558710700404; Fri, 24 May 2019 08:11:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558710700; cv=none; d=google.com; s=arc-20160816; b=e2jiM+Z7j6k4C/9sn3CS3DFYLpdyflkmIHEp2BpsWD2djtX5S2uKh2oOEcJUAIzeNo QuvzOkX0F6X3YlG4A0l4b094c+8cBlSGSFXt5n8190f4262J1QEAM15OS9XdsiSQkYsG d46A4GOILCuTpxyWaFBK2zK7dPO92o7ddIHC32GowSFywbK9RjbH/LG59OMo9GqEFBzw 6U3B8NDN7gdKXyANLHokLuc/lynVX6PzJXnKAlGmrCxdV/0FS2bVb8Jg0kGrGIAo7z2+ 6ppit1MMWJ2C9AI1rxkd10v/ybNqcR+yKbm4LZKIKGwY3DM2ZGQ32InNl1FX4G0XswCF 6r8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=32/SYB/lNdj3w8DtQ/qh3sthewtXM9Y44HboqznG/Dk=; b=kzCvRpVUN2b27KdgLk4K1yfY/Zw1K6R0TGwUAx32eDTM37mNwbbw80bfX46jUISleU 1toTUA0r1YIW2O0R4u/BsR7mGG5oEHC83rFMGWAMfsnigkDQNdLTjtkAinMFM6A90zPv qNJdtZqqUlRuwoDjWv7nTFVwyt2rXkoKhRP0xPsXaigIKVyfjaCTsQKegFHpJVA4RDVA auxtJ3RLSe7Y7dLJhqziLXfYl4Gt1VnYhY/fPIpEtplZYxFwS5i/VuiJTIyVxjI02Dsu V5az/y1IGnrR9UHYj4ynjVf/jzT8qXzakJuFg4PU+lXwKbNP5MYVfzG0teFtyJr5P7So jaig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=CS6lansA; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b186si4780539pfa.255.2019.05.24.08.11.23; Fri, 24 May 2019 08:11:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=CS6lansA; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389129AbfEXPIh (ORCPT + 99 others); Fri, 24 May 2019 11:08:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:37260 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389125AbfEXPIg (ORCPT ); Fri, 24 May 2019 11:08:36 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D86E220862; Fri, 24 May 2019 15:08:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558710516; bh=3GrNZFme+cssaRXbUiJnp/vXmmt3iw6xD3QXYdE76Mg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CS6lansAEU9DrKeiKD2en9gdaoys56slkceUSbVE1OzHI0NmNqOrQWVCbFVroGjyK QTtVEIxts08HsgAecaXqC1RWXVaZA9OhGSYND5Nj9s7lly6wegGEVRYsovbCF0DDrs w+qb14gSzU3B49/6wj5uhIj7Q07+JzjX3MF+uqFk= Date: Fri, 24 May 2019 17:08:33 +0200 From: Greg Kroah-Hartman To: Grzegorz Halat Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org, Bartlomiej Zolnierkiewicz , Jiri Slaby , Oleksandr Natalenko Subject: Re: [PATCH] vt/fbcon: deinitialize resources in visual_init() after failed memory allocation Message-ID: <20190524150833.GA10297@kroah.com> References: <20190426145946.26537-1-ghalat@redhat.com> <20190524080602.GA19514@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 24, 2019 at 03:52:31PM +0200, Grzegorz Halat wrote: > On Fri, 24 May 2019 at 10:06, Greg Kroah-Hartman > wrote: > > How? How are you triggering a memory allocation failure in a "normal" > > system? > > Anyway, I'll queue this up, but it really does not seem like anything > > anyone would see "in the wild" > > I've seen this crash twice in ours customer environment under low > memory conditions. > There is a report in Debian bug tracker: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804443 > and LKML bug report: > https://lkml.org/lkml/2017/12/18/591 Ok, now queued up to go to Linus for 5.2-final. thanks, greg k-h