From: Gang He <ghe@suse.com>
To: mfasheh@versity.com, jlbec@evilplan.org
Cc: Gang He <ghe@suse.com>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
akpm@linux-foundation.org
Subject: [PATCH v2 0/4] ocfs2: use kobject for online file check
Date: Wed, 21 Dec 2016 16:20:57 +0800 [thread overview]
Message-ID: <1482308461-12964-1-git-send-email-ghe@suse.com> (raw)
Use embedded kobject mechanism for online file check feature,
this will avoid to use a global list to save/search per-device
online file check related data. The changed code is based on
Goldwyn Rodrigues's patches and ext4 fs code, there is not
any new features added, except some very small fixes during
this code refactoring. Second, the code change does not affect
the underlying file check code.
Thank Goldwyn very much.
Compare with first version, split the code change into four
patches, make sure each patch will not bring ocfs2 kernel
modules compiling errors.
Gang He (4):
ocfs2: move some definitions to header file
ocfs2: fix some small problems
ocfs2: add kobject for online file check
ocfs2: add duplicative ino number check
fs/ocfs2/filecheck.c | 357 ++++++++++++++++++++-------------------------------
fs/ocfs2/filecheck.h | 29 ++++-
fs/ocfs2/ocfs2.h | 8 ++
fs/ocfs2/super.c | 27 +++-
4 files changed, 194 insertions(+), 227 deletions(-)
--
1.8.5.6
next reply other threads:[~2016-12-21 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 8:20 Gang He [this message]
2016-12-21 8:20 ` [PATCH v2 1/4] ocfs2: move some definitions to header file Gang He
2016-12-21 8:20 ` [PATCH v2 2/4] ocfs2: fix some small problems Gang He
2016-12-28 22:34 ` Mark Fasheh
2016-12-29 2:54 ` Gang He
2016-12-21 8:21 ` [PATCH v2 3/4] ocfs2: add kobject for online file check Gang He
2016-12-21 8:21 ` [PATCH v2 4/4] ocfs2: add duplicative ino number check Gang He
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=1482308461-12964-1-git-send-email-ghe@suse.com \
--to=ghe@suse.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@versity.com \
--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).