From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: torvalds@transmeta.com (Linus Torvalds)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
adam@yggdrasil.com (Adam J. Richter),
parsley@roanoke.edu, linux-kernel@vger.kernel.org
Subject: Re: Patch (repost): cramfs memory corruption fix
Date: Sun, 7 Jan 2001 19:42:25 +0000 (GMT) [thread overview]
Message-ID: <E14FLi2-0003Cy-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.10.10101071124540.27944-100000@penguin.transmeta.com> from "Linus Torvalds" at Jan 07, 2001 11:26:29 AM
> > I'll take a look at the ramfs one. I may have broken something else when fixing
> > everything else with ramfs (like unlink) crashing
>
> Ehh.. Plain 2.4.0 ramfs is fine, assuming you add a "UnlockPage()" to
> ramfs_writepage(). So what do you mean by "fixing everything else"?
-ac has the rather extended ramfs with resource limits and stuff. That one
also has rather more extended bugs 8). AFAIK none of those are in the vanilla
ramfs code
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-07 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 6:41 Adam J. Richter
2001-01-07 13:53 ` Alan Cox
2001-01-07 19:26 ` Linus Torvalds
2001-01-07 19:42 ` Alan Cox [this message]
2001-01-07 19:56 ` Linus Torvalds
2001-01-07 21:11 ` Rik van Riel
2001-01-07 21:20 ` Alan Cox
2001-01-08 6:56 ` Eric W. Biederman
2001-01-07 21:54 ` Chris Wedgwood
2001-01-08 13:37 ` Christoph Rohland
2001-01-08 14:19 ` Christoph Hellwig
2001-01-08 14:43 ` Christoph Rohland
2001-01-08 14:42 ` Alan Cox
2001-01-08 14:49 ` Christoph Rohland
2001-01-07 20:39 ` David L. Parsley
2001-01-08 18:27 ` Linus Torvalds
2001-01-08 3:46 ` Linus Torvalds
2001-01-08 13:11 ` David Woodhouse
2001-01-08 12:30 ` Shane Nay
2001-01-08 14:34 ` David Woodhouse
2001-01-10 23:30 ` [PATCH] one-liner fix for bforget() honoring BH_Protected; was: " David L. Parsley
2001-01-11 4:23 ` Linus Torvalds
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=E14FLi2-0003Cy-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parsley@roanoke.edu \
--cc=torvalds@transmeta.com \
/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®