From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 686EDC072B5 for ; Fri, 24 May 2019 15:08:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2E58B2175B for ; Fri, 24 May 2019 15:08:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558710518; bh=3GrNZFme+cssaRXbUiJnp/vXmmt3iw6xD3QXYdE76Mg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=HcyrgUhR7agrRgu4M6qE6hyweUJM3im8tQI1AtYepJKQUedTPeCoNAXnX3FEQJ0YF KIXQBCZhoiso8YoCHtbDFKX/5HMyrn/HQ1V4VQi8avS6ruz5Zkklbn/PTrDct/8qWB 6nNiHQatMEc+JdrPGM9P1eND0W0jbewoWYIEwCw0= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389407AbfEXPIh (ORCPT ); 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Date: Fri, 24 May 2019 15:08:33 +0000 Subject: Re: [PATCH] vt/fbcon: deinitialize resources in visual_init() after failed memory allocation Message-Id: <20190524150833.GA10297@kroah.com> List-Id: References: <20190426145946.26537-1-ghalat@redhat.com> <20190524080602.GA19514@kroah.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: Grzegorz Halat Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org, Bartlomiej Zolnierkiewicz , Jiri Slaby , Oleksandr Natalenko 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" >=20 > 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