From: Chao Yu <chao2.yu@samsung.com>
To: "'Jaegeuk Kim'" <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH 02/12] f2fs: avoid to use failed inode immediately
Date: Tue, 30 Jun 2015 10:54:21 +0800 [thread overview]
Message-ID: <00e301d0b2e0$34a7b950$9df72bf0$@samsung.com> (raw)
In-Reply-To: <1435603176-63219-2-git-send-email-jaegeuk@kernel.org>
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Tuesday, June 30, 2015 2:39 AM
> To: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org;
> linux-f2fs-devel@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 02/12] f2fs: avoid to use failed inode immediately
>
> Before iput is called, the inode number used by a bad inode can be reassigned
> to other new inode, resulting in any abnormal behaviors on the new inode.
> This should not happen for the new inode.
Nice catch!
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
next prev parent reply other threads:[~2015-06-30 2:55 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 18:39 [PATCH 01/12] f2fs: avoid freed stat information Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-06-29 18:39 ` [PATCH 02/12] f2fs: avoid to use failed inode immediately Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-06-30 2:54 ` Chao Yu [this message]
2015-06-29 18:39 ` [PATCH 03/12] f2fs: convert inline_data for various fallocate Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-06-30 2:58 ` [f2fs-dev] " Chao Yu
2015-06-29 18:39 ` [PATCH 04/12] f2fs: remove wrong f2fs_bug_on when merging extents Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-06-30 3:00 ` [f2fs-dev] " Chao Yu
2015-06-30 3:00 ` Chao Yu
2015-07-01 1:02 ` [f2fs-dev] " Jaegeuk Kim
2015-06-29 18:39 ` [PATCH 05/12] f2fs: fix wrong block address calculation for a split extent Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-06-30 3:08 ` [f2fs-dev] " Chao Yu
2015-06-30 3:08 ` Chao Yu
2015-06-29 18:39 ` [PATCH 06/12] f2fs: update on-disk extents even under extent_cache Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-06-30 3:10 ` [f2fs-dev] " Chao Yu
2015-06-29 18:39 ` [PATCH 07/12] f2fs: set cached_en after checking finally Jaegeuk Kim
2015-06-30 3:26 ` [f2fs-dev] " Chao Yu
2015-06-30 3:26 ` Chao Yu
2015-06-29 18:39 ` [PATCH 08/12] f2fs: introduce a shrinker for mounted fs Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-06-30 3:43 ` [f2fs-dev] " Chao Yu
2015-06-30 3:43 ` Chao Yu
2015-07-01 1:28 ` [f2fs-dev] " Jaegeuk Kim
2015-07-02 12:32 ` Chao Yu
2015-07-02 12:32 ` Chao Yu
2015-07-04 4:51 ` [f2fs-dev] " Jaegeuk Kim
2015-07-04 4:51 ` Jaegeuk Kim
2015-06-29 18:39 ` [PATCH 09/12] f2fs: shrink nat_cache entries Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-07-02 12:33 ` [f2fs-dev] " Chao Yu
2015-07-02 12:33 ` Chao Yu
2015-06-29 18:39 ` [PATCH 10/12] f2fs: shrink extent_cache entries Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-07-02 12:34 ` [f2fs-dev] " Chao Yu
2015-07-02 12:34 ` Chao Yu
2015-06-29 18:39 ` [PATCH 11/12] f2fs: add noextent_cache mount option Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-07-02 12:35 ` [f2fs-dev] " Chao Yu
2015-07-02 12:35 ` Chao Yu
2015-07-02 12:35 ` Chao Yu
2015-07-04 4:57 ` [f2fs-dev] " Jaegeuk Kim
2015-07-04 4:57 ` Jaegeuk Kim
2015-06-29 18:39 ` [PATCH 12/12] f2fs: use extent_cache by default Jaegeuk Kim
2015-06-29 18:39 ` Jaegeuk Kim
2015-07-02 12:36 ` [f2fs-dev] " Chao Yu
2015-07-02 12:36 ` Chao Yu
2015-07-04 5:16 ` [f2fs-dev] " Jaegeuk Kim
2015-07-04 5:16 ` Jaegeuk Kim
2015-07-04 6:30 ` [f2fs-dev] " Chao Yu
2015-07-04 6:30 ` Chao Yu
2015-07-06 12:26 ` [f2fs-dev] " Chao Yu
2015-06-30 2:45 ` [f2fs-dev] [PATCH 01/12] f2fs: avoid freed stat information Chao Yu
2015-06-30 2:45 ` 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='00e301d0b2e0$34a7b950$9df72bf0$@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.