From: Mike Fedyk <mfedyk@matchmail.com>
To: Theodore Tso <tytso@mit.edu>, David Rees <dbr@greenhydrant.com>,
linux-kernel@vger.kernel.org
Subject: Re: mke2fs (and mkreiserfs) core dumps
Date: Sun, 17 Mar 2002 10:37:52 -0800 [thread overview]
Message-ID: <20020317183752.GB27249@matchmail.com> (raw)
In-Reply-To: <20020313123114.A11658@greenhydrant.com> <20020313205537.GC429@turbolinux.com> <20020313133748.A12472@greenhydrant.com> <20020313215420.GD429@turbolinux.com> <20020315182355.A1123@thunk.org> <20020317072653.GB1150@turbolinux.com>
In-Reply-To: <20020317072653.GB1150@turbolinux.com>
On Sun, Mar 17, 2002 at 12:26:53AM -0700, Andreas Dilger wrote:
> On Mar 15, 2002 18:23 -0500, Theodore Tso wrote:
> > There's also the question
> > whether or not filesize limits should really apply to device files,
> > since the original point of filesize limits were as a simple-minded
> > quota control mechanism, and there seems to be little point to causing
> > attempts to access block deivces to fail --- under what circumstances
> > would this *ever* be considered a useful thing?
>
> Yes, I have always considered this a kernel bug (introduced in 2.4.10),
> but my (admittedly feeble) attempts to get it fixed were not accepted.
> At one point I thought a fix went into 2.4.18-pre[12] or so, but I
> guess not. I haven't tried in a while, so maybe I should make another
> attempt.
>
Was that part of the 2.4.10-pre11 -aa VM merge, or was it from another
seperate patch?
next prev parent reply other threads:[~2002-03-17 18:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 20:31 mke2fs (and mkreiserfs) core dumps David Rees
2002-03-13 20:55 ` Andreas Dilger
2002-03-13 21:37 ` David Rees
2002-03-13 21:54 ` Andreas Dilger
2002-03-15 23:23 ` Theodore Tso
2002-03-17 7:26 ` Andreas Dilger
2002-03-17 18:37 ` Mike Fedyk [this message]
2002-03-18 3:03 ` Andreas Dilger
2002-03-18 5:10 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2002-03-14 18:27 Thunder from the hill
2002-06-11 2:01 cnliou
2002-06-11 5:02 ` Andreas Dilger
2002-06-11 10:32 cnliou
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=20020317183752.GB27249@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=dbr@greenhydrant.com \
--cc=linux-kernel@vger.kernel.org \
--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