From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Eric Biggers <ebiggers@google.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs crash when filling up small filesystem
Date: Mon, 28 Nov 2016 16:26:23 -0800 [thread overview]
Message-ID: <20161129002623.GC4624@jaegeuk> (raw)
In-Reply-To: <20161128234146.GB145516@google.com>
Hello,
On Mon, Nov 28, 2016 at 03:41:46PM -0800, Eric Biggers wrote:
> On Mon, Nov 28, 2016 at 02:30:52PM -0800, Jaegeuk Kim wrote:
> > Thanks Eric.
> >
> > It seems 32MB was too small, so that mkfs.f2fs couldn't get overprovision space
> > which will be used for GC at runtime.
> > I attached a patch to resolve this issue.
> >
>
> Hi Jaegeuk,
>
> The patch seems effective at preventing mkfs.f2fs from a filesystem that's too
> small, but shouldn't there also be a kernel patch to make the kernel robust if
> userspace nevertheless attempts to mount a too-small filesystem?
Yup, I'll take a look at that as well. ;)
> By the way, I included the test which encounters this problem in the encryption
> xfstests patches which I Cc'ed to you --- it's generic/403 ("generic: test for
> weaknesses in filesystem encryption"). If f2fs doesn't support a 32 MB
> filesystem then I'll need to bump up the filesystem size to 64 MB, or disable
> the test on f2fs. Or maybe people will say the test is too weird and should
> just be deleted, but I think it's an important test :P
Oh, could you please increase the partition size to 64MB? It seems 64MB or even
128MB would not be a big deal, IIUC.
BTW, thank you so much for writing these patches. ;)
>
> Eric
------------------------------------------------------------------------------
next prev parent reply other threads:[~2016-11-29 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 4:39 f2fs crash when filling up small filesystem Eric Biggers
[not found] ` <20161128223052.GB4624@jaegeuk>
2016-11-28 23:41 ` Eric Biggers
2016-11-29 0:26 ` Jaegeuk Kim [this message]
2016-12-05 19:30 ` Eric Biggers
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=20161129002623.GC4624@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=ebiggers@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).