From: Andrew Morton <akpm@linux-foundation.org>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/2] ocfs2: fix ocfs2 corrupt when iputting an inode
Date: Thu, 6 Aug 2020 20:49:38 -0700 [thread overview]
Message-ID: <20200806204938.5f0bab0e265c279c275ce806@linux-foundation.org> (raw)
In-Reply-To: <e24ca852-7c37-f12e-ed38-0fa0ac7c5c93@gmail.com>
On Mon, 1 Jun 2020 17:01:51 +0800 Joseph Qi <jiangqi903@gmail.com> wrote:
>
>
> On 2020/5/26 15:55, Wangyan wrote:
> > In this condition, it will cause an bug on error.
> > ocfs2_mkdir()
> > ->ocfs2_mknod()
> > ->ocfs2_mknod_locked()
> > ->__ocfs2_mknod_locked()
> > //Assume inode->i_generation is genN.
> > ->inode->i_generation = osb->s_next_generation++;
> > // The inode lockres has been initialized.
> > ->ocfs2_populate_inode()
> > ->ocfs2_create_new_inode_locks()
> > ->An error happened, returned value is non-zero
> > // free the start_bit x in bg_blkno
> > ->ocfs2_free_suballoc_bits()
> > ->... /* Another process execute mkdir success in this place,
> > and it occupied the start_bit x in bg_blkno
> > which has been freed before. Its inode->i_generation
> > is genN + 1 */
> > ->iput(inode)
> > ->evict()
> > ->ocfs2_evict_inode()
> > ->ocfs2_delete_inode()
> > ->ocfs2_inode_lock()
> > ->ocfs2_inode_lock_update()
> > /* Bug on here, genN != genN + 1 */
> > ->mlog_bug_on_msg(inode->i_generation !=
> > le32_to_cpu(fe->i_generation))
> >
> > So, we need not to reclaim the inode when the inode->ip_inode_lockres
> > has been initialized. It will be freed in iput().
> >
> > Signed-off-by: Yan Wang <wangyan122@huawei.com>
> > Reviewed-by: Jun Piao <piaojun@huawei.com>
> > ---
> > fs/ocfs2/namei.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c
> > index e61fdd8972ec..5302992d2bee 100644
> > --- a/fs/ocfs2/namei.c
> > +++ b/fs/ocfs2/namei.c
> > @@ -640,7 +640,8 @@ static int ocfs2_mknod_locked(struct ocfs2_super *osb,
> > status = __ocfs2_mknod_locked(dir, inode, dev, new_fe_bh,
> > parent_fe_bh, handle, inode_ac,
> > fe_blkno, suballoc_loc, suballoc_bit);
> > - if (status < 0) {
> > + if (status < 0 && !(OCFS2_I(inode)->ip_inode_lockres.l_flags &
> > + OCFS2_LOCK_INITIALIZED)) {
>
> Each condition in separate line may be better:
>
> if (status < 0 &&
> !(OCFS2_I(inode)->ip_inode_lockres.l_flags & OCFS2_LOCK_INITIALIZED))
>
> And you've missed a fixed tag:
> Fixes: b1529a41f777 ("ocfs2: should reclaim the inode if '__ocfs2_mknod_locked' returns an error")
And to this one?
prev parent reply other threads:[~2020-08-07 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 7:55 [Ocfs2-devel] [PATCH 2/2] ocfs2: fix ocfs2 corrupt when iputting an inode Wangyan
2020-06-01 9:01 ` Joseph Qi
2020-08-07 3:49 ` Andrew Morton [this message]
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=20200806204938.5f0bab0e265c279c275ce806@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ocfs2-devel@oss.oracle.com \
/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).