From: Chao Yu <chao@kernel.org>
To: Hyeong-Jun Kim <hj514.kim@samsung.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] F2FS: invalidate META_MAPPING before IPU/DIO write
Date: Tue, 2 Nov 2021 11:37:31 +0800 [thread overview]
Message-ID: <228a7789-4b38-f08c-ecdf-584ef491ea7a@kernel.org> (raw)
In-Reply-To: <20211101084634.38727-1-hj514.kim@samsung.com>
On 2021/11/1 16:46, Hyeong-Jun Kim wrote:
> Encrypted pages during GC are read and cached in META_MAPPING.
> However, due to cached pages in META_MAPPING, there is an issue where
> newly written pages are lost by IPU or DIO writes.
>
> Thread A - f2fs_gc() Thread B
> /* phase 3 */
> down_write(i_gc_rwsem)
> ra_data_block() ---- (a)
> up_write(i_gc_rwsem)
> f2fs_direct_IO() :
> - down_read(i_gc_rwsem)
> - __blockdev_direct_io()
> - get_data_block_dio_write()
> - f2fs_dio_submit_bio() ---- (b)
> - up_read(i_gc_rwsem)
> /* phase 4 */
> down_write(i_gc_rwsem)
> move_data_block() ---- (c)
> up_write(i_gc_rwsem)
>
> (a) In phase 3 of f2fs_gc(), up-to-date page is read from storage and
> cached in META_MAPPING.
> (b) In thread B, writing new data by IPU or DIO write on same blkaddr as
> read in (a). cached page in META_MAPPING become out-dated.
> (c) In phase 4 of f2fs_gc(), out-dated page in META_MAPPING is copied to
> new blkaddr. In conclusion, the newly written data in (b) is lost.
>
> To address this issue, invalidating pages in META_MAPPING before IPU or
> DIO write.
>
> Fixes: 6aa58d8ad20a ("f2fs: readahead encrypted block during GC")
> Signed-off-by: Hyeong-Jun Kim <hj514.kim@samsung.com>
> ---
> fs/f2fs/data.c | 2 ++
> fs/f2fs/segment.c | 3 +++
> 2 files changed, 5 insertions(+)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 74e1a350c1d8..9f754aaef558 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -1708,6 +1708,8 @@ int f2fs_map_blocks(struct inode *inode, struct f2fs_map_blocks *map,
> */
> f2fs_wait_on_block_writeback_range(inode,
> map->m_pblk, map->m_len);
> + invalidate_mapping_pages(META_MAPPING(sbi),
> + map->m_pblk, map->m_pblk);
>
> if (map->m_multidev_dio) {
> block_t blk_addr = map->m_pblk;
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 526423fe84ce..f57c55190f9e 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -3652,6 +3652,9 @@ int f2fs_inplace_write_data(struct f2fs_io_info *fio)
> goto drop_bio;
> }
>
> + invalidate_mapping_pages(META_MAPPING(fio->sbi),
There is one more comment from Weichao:
Use sbi instead of fio->sbi?
Thanks,
> + fio->new_blkaddr, fio->new_blkaddr);
> +
> stat_inc_inplace_blocks(fio->sbi);
>
> if (fio->bio && !(SM_I(sbi)->ipu_policy & (1 << F2FS_IPU_NOCACHE)))
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2021-11-02 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20211101084637epcas1p3a17850a8a437488649be9b41ffa889e2@epcas1p3.samsung.com>
2021-11-01 8:46 ` [f2fs-dev] [PATCH v2] F2FS: invalidate META_MAPPING before IPU/DIO write Hyeong-Jun Kim
2021-11-02 1:28 ` Chao Yu
2021-11-02 3:37 ` Chao Yu [this message]
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=228a7789-4b38-f08c-ecdf-584ef491ea7a@kernel.org \
--to=chao@kernel.org \
--cc=hj514.kim@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 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).