Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp482926ybi; Fri, 24 May 2019 06:55:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqxaBm0rdOz+Cy/9aKVtaqx+VrAHoa4PXBxkHK775o6pikqNd/6PLxoqDWDHFJ8gx8uFPsKX X-Received: by 2002:a63:184:: with SMTP id 126mr79140418pgb.420.1558706113444; Fri, 24 May 2019 06:55:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558706113; cv=none; d=google.com; s=arc-20160816; b=qP+XeOWAWvMQBZWH91YulXiRQABMrdEQqWcZK9MKLCpkM1Uf6BTQdbJtREkEyk0AVe NC5OPGYiAE/7RUXBxqQJT7uhucls7M9a47Olb4tAqp7v9Rjw91eR2Rc3Y1+9IU7ld0DG TYONe8fdXiXgETzXIYyGrDlN7+ybcgai9QczS9Yv2tE+JUTmbxk8lp3ulp4wLpY1S7YQ 6khi+51A4N8Y4RqRF4J9TMWit8ueLxzNtWS+f/OF+tCFzn/ez6C3K38Ub2E2mpEnCLzY 71npXxU3GVn3DA4rre8zTlb2PEkFr1OwBgPGjOWMWg1Fku9iM0YGThzQ5xcdIbxecuVk wyuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=9wkXuNyY+BPK06cBRjiKGUSp8g87URqk4aYlZC7CDaI=; b=Kun2i+IS/yjyrfEKhoXhYVcjAHh16L0jK+LyW+T2OM0ktnzMHhqYJv/HlmLLSq9Qft PRqXmxYPpUUVdBbjkCT2Ue3GVyGZkJJuv9VflYxCae1r0tOw04KroTw0owQFmbtHkiJ2 erK+GzT4FoYEKF9MokjmXSPwPSTRO5jnimSvr+0qkfUxkP4a+geWYkGQ7r4E5ryItDIz urJN7AizG2QxOKEznGsWk0ZErTPwfWAaUjNS6Iye767wgjvics5Jj6nsvCedfzYx8iTs GEqSSghFRq/8wrJaApwSmlhOWB43SlGitlh4cvQCecynRW8qhb3BSFeZ+Kc7P1qCZbSO s38w== ARC-Authentication-Results: i=1; mx.google.com; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y7si414876pgp.299.2019.05.24.06.54.57; Fri, 24 May 2019 06:55:13 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2403933AbfEXNwo (ORCPT + 99 others); Fri, 24 May 2019 09:52:44 -0400 Received: from mail-vs1-f68.google.com ([209.85.217.68]:41207 "EHLO mail-vs1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2403909AbfEXNwn (ORCPT ); Fri, 24 May 2019 09:52:43 -0400 Received: by mail-vs1-f68.google.com with SMTP id w19so5787261vsw.8 for ; Fri, 24 May 2019 06:52:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9wkXuNyY+BPK06cBRjiKGUSp8g87URqk4aYlZC7CDaI=; b=OtHQxq9gk5UZAxWRfA4bx/PHjvDCXzWHE5SA3YupxsuhhDg+DyobzbYHynIQedcUt2 BnbKu1Jyzp4W5B7aDw1StWOCw9RZAyBvCurQqa5vQUMNcCBW4F2A5QkxX1CzNG0sLfGO BC16fFGMYeicRsYQYQzAOLMfn49b/q/FG7qPwJPyplOe69hLFXSkIfkAPvw4dljnvUeq PG7NJWjXqH8cQj56IFyGLL5lJXsajl56LpdmUvW6CvOEwRD98fPnLWL9Uh7TtLt7+FtK 9GCcpr3Ns0SZZK8NGP7MR3p87JHWZF9xAvHcRvluPzI3feUWqPUDD2ABFkGlq47KuzLm Jwdg== X-Gm-Message-State: APjAAAWhZcI8fvnSjDu860lCYsW4D5OAC+cmkHR78yVOHGOnkvhITeXT 8ZZe4iByxmCrwIxG+kcaVE5iiQkkNPW7FVcTCgu98w== X-Received: by 2002:a67:f309:: with SMTP id p9mr50802170vsf.216.1558705962670; Fri, 24 May 2019 06:52:42 -0700 (PDT) MIME-Version: 1.0 References: <20190426145946.26537-1-ghalat@redhat.com> <20190524080602.GA19514@kroah.com> In-Reply-To: <20190524080602.GA19514@kroah.com> From: Grzegorz Halat Date: Fri, 24 May 2019 15:52:31 +0200 Message-ID: Subject: Re: [PATCH] vt/fbcon: deinitialize resources in visual_init() after failed memory allocation To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org, Bartlomiej Zolnierkiewicz , Jiri Slaby , Oleksandr Natalenko Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 -- Grzegorz