mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Marineau" <mike@marineau.org>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH, RESEND] tmpfs: fix mounts when size is less than the page size
Date: Sun, 4 Nov 2007 11:12:22 -0700	[thread overview]
Message-ID: <c0526ddf0711041012x7b41269x12a05ddb6e03a04d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711041202260.4631@blonde.wat.veritas.com>

On 11/4/07, Hugh Dickins <hugh@veritas.com> wrote:
> Fair enough, that does match the documentation of "size=0" better.
> Though either way, someone who typos is going to get one kind of surprise
> or another.  Do you mind if we do it slightly differently, achieving the
> same effect without a special case, by rounding up instead of down?

Sounds reasonable to me. I didn't know about DIV_ROUND_UP :-)

>
>
> From: Michael Marineau <mike@marineau.org>
>
> When tmpfs is mounted with a size less than one page, the number of blocks
> is set to 0 which makes the tmpfs mount unlimited. This can lead to a quick
> and surprising death if someone typos a tmpfs mount command and writes too
> much.
>
> tmpfs can still be mounted as unlimited if size or nr_blocks is exactly 0,
> as Documentation/filesystems/tmpfs.txt says.
>
> Hugh: do this by rounding size up instead of down in all cases: which
> slightly expands other odd-sized tmpfs mounts, but in a consistent way.
>
> Signed-off-by: Michael Marineau <mike@marineau.org>
> Signed-off-by: Hugh Dickins <hugh@veritas.com>
> ---
>
>  mm/shmem.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- 2.6.24-rc1-git/mm/shmem.c   2007-10-31 06:18:05.000000000 +0000
> +++ linux/mm/shmem.c    2007-11-04 11:46:09.000000000 +0000
> @@ -2137,7 +2137,7 @@ static int shmem_parse_options(char *opt
>                         }
>                         if (*rest)
>                                 goto bad_val;
> -                       *blocks = size >> PAGE_CACHE_SHIFT;
> +                       *blocks = DIV_ROUND_UP(size, PAGE_CACHE_SIZE);
>                 } else if (!strcmp(this_char,"nr_blocks")) {
>                         *blocks = memparse(value,&rest);
>                         if (*rest)
>


-- 
Michael Marineau
Oregon State University
mike@marineau.org

  reply	other threads:[~2007-11-04 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 22:11 [PATCH] " Michael Marineau
2007-11-03 23:46 ` [PATCH, RESEND] " Michael Marineau
2007-11-04 12:19   ` Hugh Dickins
2007-11-04 18:12     ` Michael Marineau [this message]
2007-11-04 18:29       ` Hugh Dickins

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=c0526ddf0711041012x7b41269x12a05ddb6e03a04d@mail.gmail.com \
    --to=mike@marineau.org \
    --cc=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@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

all inboxes | Powered by JetHome®