linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	David Hildenbrand <david@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [PATCH 0/3] nilfs2 lockdep warning fixes
Date: Mon, 21 Mar 2022 21:57:04 +0900	[thread overview]
Message-ID: <1647867427-30498-1-git-send-email-konishi.ryusuke@gmail.com> (raw)

Hi Andrew,

please consider applying the following changes to -mm tree.

Ryusuke Konishi (3):
  nilfs2: fix lockdep warnings in page operations for btree nodes
  nilfs2: fix lockdep warnings during disk space reclamation
  nilfs2: get rid of nilfs_mapping_init()

The first two are to resolve the lockdep warning issue, and the last
one is the accompanying cleanup and low priority.

The merge window is already open, but this is for the reported issues,
so I'll send it without waiting at this point when tests have passed.

Based on your comment, this series solves the issue by separating
inode object as needed.  Since I was worried about the impact of the
object composition changes, I tested the series carefully not to cause
regressions especially for delicate functions such like disk space
reclamation and snapshots.


Thanks,
Ryusuke Konishi
--
 fs/nilfs2/btnode.c  |  23 +++++++-
 fs/nilfs2/btnode.h  |   1 +
 fs/nilfs2/btree.c   |  27 ++++++---
 fs/nilfs2/dat.c     |   4 +-
 fs/nilfs2/gcinode.c |   7 ++-
 fs/nilfs2/inode.c   | 159 +++++++++++++++++++++++++++++++++++++++++++++++-----
 fs/nilfs2/mdt.c     |  43 +++++++++-----
 fs/nilfs2/mdt.h     |   6 +-
 fs/nilfs2/nilfs.h   |  16 +++---
 fs/nilfs2/page.c    |  16 +-----
 fs/nilfs2/page.h    |   1 -
 fs/nilfs2/segment.c |   9 ++-
 fs/nilfs2/super.c   |   5 +-
 13 files changed, 241 insertions(+), 76 deletions(-)

-- 
1.8.3.1



             reply	other threads:[~2022-03-21 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 12:57 Ryusuke Konishi [this message]
2022-03-21 12:57 ` [PATCH 1/3] nilfs2: fix lockdep warnings in page operations for btree nodes Ryusuke Konishi
2022-03-21 12:57 ` [PATCH 2/3] nilfs2: fix lockdep warnings during disk space reclamation Ryusuke Konishi
2022-03-21 12:57 ` [PATCH 3/3] nilfs2: get rid of nilfs_mapping_init() 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=1647867427-30498-1-git-send-email-konishi.ryusuke@gmail.com \
    --to=konishi.ryusuke@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=willy@infradead.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