From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f195.google.com ([209.85.216.195]:46503 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732453AbeGLXfV (ORCPT ); Thu, 12 Jul 2018 19:35:21 -0400 Received: by mail-qt0-f195.google.com with SMTP id d4-v6so10168971qtn.13 for ; Thu, 12 Jul 2018 16:23:33 -0700 (PDT) Date: Thu, 12 Jul 2018 20:23:28 -0300 From: Ernesto =?utf-8?Q?A=2E_Fern=C3=A1ndez?= To: Andrew Morton Cc: linux-fsdevel@vger.kernel.org, "Xu, Wen" Subject: Re: [PATCH] hfsplus: fix NULL dereference in hfsplus_lookup() Message-ID: <20180712232327.cs3andnrvpjnknl2@eaf> References: <20180712215344.q44dyrhymm4ajkao@eaf> <20180712153311.71495c0ea5ba0115414f5301@linux-foundation.org> <20180712230750.h55b2sin3a7weqdy@eaf> <20180712161907.c93f4e70e5d406fd3d2d373e@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180712161907.c93f4e70e5d406fd3d2d373e@linux-foundation.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Jul 12, 2018 at 04:19:07PM -0700, Andrew Morton wrote: > On Thu, 12 Jul 2018 20:07:51 -0300 Ernesto A. Fernández wrote: > > > On Thu, Jul 12, 2018 at 03:33:11PM -0700, Andrew Morton wrote: > > > On Thu, 12 Jul 2018 18:53:47 -0300 Ernesto A. Fernández wrote: > > > > > > > Check that the hidden directory is not NULL before using it, instead of > > > > after. > > > > > > > > > > Under what circumstances does the crash happen? Mount of a corrupted fs? > > > > No, when looking up corrupted catalog data (dentry) on a filesystem with > > no metadata directory (this could only ever happen on a read-only mount). > > Wen Xu sent the replication steps in detail to the fsdevel list, here is > > a link: > > > > https://bugzilla.kernel.org/show_bug.cgi?id=200297 > > > > I did not explain this because I think the diff makes it clear that there > > is a bug at least. > > It is important that we know what circumstances lead to the bug being > triggered, so that people can decide whether to backport the fix into > their various kernels. > OK, I'll resend with more details.