From: Dan Kegel <dank@kegel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"khttpd-users@lists.alt.org" <khttpd-users@alt.org>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: khttpd and tmpfs don't get along?
Date: Wed, 22 May 2002 12:20:55 -0700 [thread overview]
Message-ID: <3CEBEF97.1BEBF36C@kegel.com> (raw)
In-Reply-To: <3CEAF6F2.BB70395D@kegel.com> <20020522095440.A13744@infradead.org>
Christoph Hellwig wrote:
>
> 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..
I see. Guess I should finally test that tmpfs/loop patch, eh? :-)
I just now crashed Red Hat 7.3 on x86 SMP by compiling in khttpd
and serving files out of a tmpfs. It crashed with or without my
earlier patch (http://www.kegel.com/linux/khttpd/khttpd-unbork.patch)
that fixes khttpd crashes with other filesystems.
Guess it wasn't a bug in linuxppc_2_4_devel after all.
I am now switching to ramfs instead of tmpfs to hold my documentroot,
and that should be the end of my khttpd problems.
(There is no disk on the embedded ppc system I'm using, so I have
to use one ram filesystem or another.)
- Dan
next prev parent reply other threads:[~2002-05-22 19:16 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
2002-05-22 19:20 ` Dan Kegel [this message]
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=3CEBEF97.1BEBF36C@kegel.com \
--to=dank@kegel.com \
--cc=hch@infradead.org \
--cc=khttpd-users@alt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@lists.linuxppc.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