mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: adam@yggdrasil.com (Adam J. Richter)
Cc: parsley@roanoke.edu, linux-kernel@vger.kernel.org,
	torvalds@transmeta.com
Subject: Re: Patch (repost): cramfs memory corruption fix
Date: Sun, 7 Jan 2001 13:53:17 +0000 (GMT)	[thread overview]
Message-ID: <E14FGG7-0002ff-00@the-village.bc.nu> (raw)
In-Reply-To: <20010106224109.A1601@adam.yggdrasil.com> from "Adam J. Richter" at Jan 06, 2001 10:41:09 PM

> >ramfs croaks with 'kernel BUG in filemap.c line 2559' anytime I make a
> >file in ac2 and ac3.  Works fine in 2.4.0 vanilla.  Should be quite
> >repeatable...

I'll take a look at the ramfs one. I may have broken something else when fixing
everything else with ramfs (like unlink) crashing

> 	This sounds like a bug that I posted a fix for a long time ago.
> cramfs calls bforget on the superblock area, destroying that block of
> the ramdisk, even when the ramdisk does not contain a cramfs file system.
> Normally, bforget is called on block that really can be trashed,
> such as blocks release by truncate or unlink.  If it worked for
> you before, you were just getting lucky.  Here is the patch.
> 
> 	Linus, please consider applying this.  Thank you.

This isnt the fix. If -ac also fails well it contains this cramfs fix. So
there must be other problems

Alan

-
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/

  reply	other threads:[~2001-01-07 13:52 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 [this message]
2001-01-07 19:26   ` Linus Torvalds
2001-01-07 19:42     ` Alan Cox
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=E14FGG7-0002ff-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®