From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f66.google.com ([209.85.208.66]:34463 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727046AbeHWBNP (ORCPT ); Wed, 22 Aug 2018 21:13:15 -0400 MIME-Version: 1.0 In-Reply-To: References: <20180724064929.GD19722@shao2-debian> <20180724130155.20641-1-mszeredi@redhat.com> From: Marc Dionne Date: Wed, 22 Aug 2018 18:46:36 -0300 Message-ID: Subject: Re: [PATCH v3] vfs: don't evict uninitialized inode To: Miklos Szeredi Cc: Al Viro , Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Aug 22, 2018 at 4:37 PM, Marc Dionne wrote: > > FYI with this patch (now merged) I'm seeing warnings whenever an > object is created in an overlayfs mount: > > [ 842.152673] list_add double add: new=ffff88017efe03d8, > prev=ffff88015c07ad88, next=ffff88017efe03d8. > [ 842.152687] WARNING: CPU: 4 PID: 7592 at lib/list_debug.c:31 > __list_add_valid+0x6e/0x80 > And I see that's now fixed by 6faf05c2b2b4 ("ovl: set I_CREATING on inode being created"). Marc