From: Chao Yu <chao2.yu@samsung.com>
To: 'Jaegeuk Kim' <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH 4/5] f2fs: go out for insert_inode_locked failure
Date: Thu, 20 Aug 2015 17:11:08 +0800 [thread overview]
Message-ID: <01ba01d0db28$41a19e30$c4e4da90$@samsung.com> (raw)
In-Reply-To: <1439887589-35190-4-git-send-email-jaegeuk@kernel.org>
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Tuesday, August 18, 2015 4:46 PM
> To: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org;
> linux-f2fs-devel@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 4/5] f2fs: go out for insert_inode_locked failure
>
> We should not call unlock_new_inode when insert_inode_locked failed.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
next prev parent reply other threads:[~2015-08-20 9:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 8:46 [PATCH 1/5] f2fs: reuse nids more aggressively Jaegeuk Kim
2015-08-18 8:46 ` [PATCH 2/5] f2fs: fix to cover lock_op for update_inode_page Jaegeuk Kim
2015-08-18 8:46 ` Jaegeuk Kim
2015-08-20 9:09 ` Chao Yu
2015-08-20 9:09 ` [f2fs-dev] " Chao Yu
2015-08-18 8:46 ` [PATCH 3/5] f2fs: retry gc if one section is not successfully reclaimed Jaegeuk Kim
2015-08-18 8:46 ` Jaegeuk Kim
2015-08-18 8:46 ` [PATCH 4/5] f2fs: go out for insert_inode_locked failure Jaegeuk Kim
2015-08-18 8:46 ` Jaegeuk Kim
2015-08-20 9:11 ` Chao Yu [this message]
2015-08-18 8:46 ` [PATCH 5/5] f2fs: check the node block address of newly allocated nid Jaegeuk Kim
2015-08-20 9:12 ` Chao Yu
2015-08-20 9:12 ` [f2fs-dev] " Chao Yu
2015-08-20 15:35 ` Jaegeuk Kim
2015-08-20 15:35 ` [f2fs-dev] " Jaegeuk Kim
2015-08-21 12:48 ` Chao Yu
2015-08-21 14:59 ` Chao Yu
2015-08-21 14:59 ` [f2fs-dev] " Chao Yu
2015-08-24 9:38 ` Chao Yu
2015-08-20 9:01 ` [f2fs-dev] [PATCH 1/5] f2fs: reuse nids more aggressively Chao Yu
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='01ba01d0db28$41a19e30$c4e4da90$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.