From: Eric Biggers <ebiggers@kernel.org>
To: linux-nilfs@vger.kernel.org, Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nilfs2: only call unlock_new_inode() if I_NEW
Date: Mon, 27 Jul 2020 09:50:00 -0700 [thread overview]
Message-ID: <20200727165000.GH1138@sol.localdomain> (raw)
In-Reply-To: <20200628070152.820311-1-ebiggers@kernel.org>
On Sun, Jun 28, 2020 at 12:01:52AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> unlock_new_inode() is only meant to be called after a new inode has
> already been inserted into the hash table. But nilfs_new_inode() can
> call it even before it has inserted the inode, triggering the WARNING in
> unlock_new_inode(). Fix this by only calling unlock_new_inode() if the
> inode has the I_NEW flag set, indicating that it's in the table.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Ping. Ryusuke, any interest in taking this patch?
- Eric
next prev parent reply other threads:[~2020-07-27 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 7:01 [PATCH] nilfs2: only call unlock_new_inode() if I_NEW Eric Biggers
2020-07-27 16:50 ` Eric Biggers [this message]
2020-07-27 16:59 ` Ryusuke Konishi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200727165000.GH1138@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).