From: Christoph Hellwig <hch@infradead.org>
To: Dan Kegel <dank@kegel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: khttpd and tmpfs don't get along?
Date: Wed, 22 May 2002 09:54:40 +0100 [thread overview]
Message-ID: <20020522095440.A13744@infradead.org> (raw)
In-Reply-To: <3CEAF6F2.BB70395D@kegel.com>
On Tue, May 21, 2002 at 06:40:02PM -0700, Dan Kegel wrote:
> I've found that khttpd tends to oops when used with tmpfs.
> The oops tracebacks are not especially informative.
> So far, I've only verified this with ppc, but I should be
> able to verify it with x86 soon.
That's because it abuses do_generic_file_read. It' the same design mistake
that also makes loop fail on tmpfs - do_generic_file_read should never have
been exported from filemap.c..
next prev parent reply other threads:[~2002-05-22 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 1:40 khttpd and tmpfs don't get along? Dan Kegel
2002-05-22 8:54 ` Christoph Hellwig [this message]
2002-05-22 19:20 ` Dan Kegel
2002-05-22 19:33 ` Christoph Hellwig
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=20020522095440.A13744@infradead.org \
--to=hch@infradead.org \
--cc=dank@kegel.com \
--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