All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuning Zhang <sunny.s.zhang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH V2 0/2] ocfs2: protect extent tree in the ocfs2_prepare_inode_for_write
Date: Wed, 18 Sep 2019 10:02:53 +0800	[thread overview]
Message-ID: <1568772175-2906-1-git-send-email-sunny.s.zhang@oracle.com> (raw)

I split the patch into 2 patches. A unused function is removed in
the second patch. This will make patches easier to read.

v1->v2:
  - split the patch into 2 patches
  - abstract a pair of function for locking and unlocking
  - remove the function call of ocfs2_prepare_inode_for_refcount

Shuning Zhang (2):
  ocfs2: protect extent tree in the ocfs2_prepare_inode_for_write
  ocfs2: remove unused function ocfs2_prepare_inode_for_refcount

 fs/ocfs2/file.c | 136 +++++++++++++++++++++++++++++++++++++-------------------
 1 file changed, 91 insertions(+), 45 deletions(-)

-- 
2.7.4

             reply	other threads:[~2019-09-18  2:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18  2:02 Shuning Zhang [this message]
2019-09-18  2:02 ` [Ocfs2-devel] [PATCH V2 1/2] ocfs2: protect extent tree in the ocfs2_prepare_inode_for_write Shuning Zhang
2019-09-20 16:57   ` Junxiao Bi
2019-09-25 10:33   ` Gang He
2019-09-27  7:15     ` sunnyZhang
     [not found]       ` <92e25022-9d63-92f5-d3cf-08423c5c97b7@oracle.com>
2019-10-24  2:02         ` Gang He
2019-10-24  4:34           ` sunnyZhang
2019-10-25  0:06             ` Andrew Morton
2019-10-25  0:52               ` sunnyZhang
2019-09-18  2:02 ` [Ocfs2-devel] [PATCH V2 2/2] ocfs2: remove unused function ocfs2_prepare_inode_for_refcount Shuning Zhang
2019-09-20 16:57   ` Junxiao Bi
2019-09-25 10:34   ` 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=1568772175-2906-1-git-send-email-sunny.s.zhang@oracle.com \
    --to=sunny.s.zhang@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.