From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao2.yu@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 4/4] f2fs: avoid wrong f2fs_bug_on when truncating inline_data
Date: Wed, 18 Mar 2015 10:57:50 -0700 [thread overview]
Message-ID: <20150318175750.GB7461@jaegeuk-mac02> (raw)
In-Reply-To: <006d01d06118$a3a23390$eae69ab0$@samsung.com>
Hi,
On Wed, Mar 18, 2015 at 09:12:00AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -----Original Message-----
> > From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> > Sent: Wednesday, March 18, 2015 12:58 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 4/4] f2fs: avoid wrong f2fs_bug_on when truncating inline_data
> >
> > This patch removes wrong f2fs_bug_on in truncate_inline_inode.
> >
> > When there is no space, it can happen a corner case where i_isze is over
> > MAX_INLINE_SIZE while its inode is still inline_data.
> >
> > The scenario is
> > 1. write small data into file #A.
> > 2. fill the whole partition to 100%.
> > 3. truncate 4096 on file #A.
>
> If we truncate size over MAX_INLINE_DATA, we will convert inline data in
> f2fs_truncate rather than write_begin below. isn't it?
But, it fails to convert that due to -ENOSPC. :)
Thanks,
>
> Thanks,
>
> > 4. write data at 8192 offset.
> > --> f2fs_write_begin
> > -> -ENOSPC = f2fs_convert_inline_page
> > -> f2fs_write_failed
> > -> truncate_blocks
> > -> truncate_inline_inode
> > BUG_ON, since i_size is 4096.
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > ---
> > fs/f2fs/inline.c | 7 -------
> > 1 file changed, 7 deletions(-)
> >
> > diff --git a/fs/f2fs/inline.c b/fs/f2fs/inline.c
> > index 153c5e7..d3e0599 100644
> > --- a/fs/f2fs/inline.c
> > +++ b/fs/f2fs/inline.c
> > @@ -54,13 +54,6 @@ bool truncate_inline_inode(struct page *ipage, u64 from)
> > {
> > void *addr;
> >
> > - /*
> > - * we should never truncate inline data past max inline data size,
> > - * because we always convert inline inode to normal one before
> > - * truncating real data if new size is past max inline data size.
> > - */
> > - f2fs_bug_on(F2FS_P_SB(ipage), from > MAX_INLINE_DATA);
> > -
> > if (from >= MAX_INLINE_DATA)
> > return false;
> >
> > --
> > 2.1.1
> >
> >
> > ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> > by Intel and developed in partnership with Slashdot Media, is your hub for all
> > things parallel software development, from weekly thought leadership blogs to
> > news, videos, case studies, tutorials and more. Take a look and join the
> > conversation now. http://goparallel.sourceforge.net/
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2015-03-18 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 16:57 [PATCH 1/4] f2fs: fix to cover sentry_lock for block allocation Jaegeuk Kim
2015-03-17 16:57 ` [PATCH 2/4] f2fs: set buffer_new when new blocks are allocated Jaegeuk Kim
2015-03-18 2:24 ` [f2fs-dev] " Chao Yu
2015-03-18 17:57 ` [f2fs-dev] [PATCH 2/4 v2] " Jaegeuk Kim
2015-03-19 11:18 ` Chao Yu
2015-03-17 16:57 ` [PATCH 3/4] f2fs: enhance multi-threads performance Jaegeuk Kim
2015-03-17 16:57 ` [PATCH 4/4] f2fs: avoid wrong f2fs_bug_on when truncating inline_data Jaegeuk Kim
2015-03-18 1:12 ` [f2fs-dev] " Chao Yu
2015-03-18 17:57 ` Jaegeuk Kim [this message]
2015-03-19 11:19 ` 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=20150318175750.GB7461@jaegeuk-mac02 \
--to=jaegeuk@kernel.org \
--cc=chao2.yu@samsung.com \
--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 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).