mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Theodore Tso <tytso@mit.edu>
Cc: Andrew Morton <akpm@zip.com.au>, "H . J . Lu" <hjl@lucon.org>,
	linux-mips@oss.sgi.com,
	linux kernel <linux-kernel@vger.kernel.org>,
	GNU C Library <libc-alpha@sources.redhat.com>
Subject: Re: Does e2fsprogs-1.26 work on mips?
Date: Tue, 26 Mar 2002 21:51:56 +1100 (EST)	[thread overview]
Message-ID: <15520.21196.511499.316840@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20020326015440.A12162@thunk.org>

Theodore Tso writes:

> 3)  RLIMIT_FILESIZE should not apply to block devices!!!

Absolutely.

I would go further and say that it should only apply to writes to a
regular file that would extend the file past the filesize limit.  At
the moment the check in generic_file_write is simply whether the file
offset is greater than the limit, or would be greater than the limit
after the write.  This doesn't seem right to me.  If, for example, my
RLIMIT_FILESIZE is 1MB, and I have write access to an existing 100MB
file, I think I should be able to write anywhere in that file as long
as I don't try to extend it.

If we did that then the block device case would fall out, since you
can't extend block devices (not by writing past the end of them
anyway).

Paul.

  reply	other threads:[~2002-03-26 11:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020323140728.A4306@lucon.org>
     [not found] ` <3C9D1C1D.E30B9B4B@zip.com.au>
     [not found]   ` <20020323221627.A10953@lucon.org>
     [not found]     ` <3C9D7A42.B106C62D@zip.com.au>
2002-03-24  9:28       ` H . J . Lu
2002-03-25  5:31         ` Theodore Tso
2002-03-25  5:43           ` Andrew Morton
2002-03-26  6:54             ` Theodore Tso
2002-03-26 10:51               ` Paul Mackerras [this message]
2002-03-25 17:17           ` H . J . Lu
2002-03-25 10:52 Peter Hartley
2002-03-25 17:07 ` H . J . Lu
2002-03-25 19:00 Peter Hartley
2002-03-25 19:11 ` H . J . Lu

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=15520.21196.511499.316840@argo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=akpm@zip.com.au \
    --cc=hjl@lucon.org \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=tytso@mit.edu \
    /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®