LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: stock@stokkie.net, linux-kernel@vger.kernel.org
Subject: Re: ramdisk driver in 2.6.6 has a severe bug
Date: Mon, 17 May 2004 18:03:12 -0700	[thread overview]
Message-ID: <20040517180312.4560e6da.akpm@osdl.org> (raw)
In-Reply-To: <20040518005042.GW17014@parcelfarce.linux.theplanet.co.uk>

viro@parcelfarce.linux.theplanet.co.uk wrote:
>
> > Well in that case perhaps something else broke.  I've seen no such reports
>  > of recent regressions in the ramdisk driver.
>  > 
>  > The two problems of which I am aware are:
>  > 
>  > a) It loses its brains across umount.  Seems that it's very rare that
>  >    anyone actually cares about this, which is why it has not been fixed in
>  >    well over a year.
> 
>  Details, please.  The only case I'm aware of is when you have fs-set
>  block size different from the one we had before mount(2).  And in that
>  case it would lose its brains when the blocksize had been flipped in
>  the first place.  Which would tend to fail mount(2) anyway.

Oh, it's nothing to do with that.  Problem is that files backed by ramdisks
are marked "memory backed" so the writeback code doesn't write them to the
ramdisk inode.  So it's presently functioning as ramfs with ext2 metadata
in the blockdev inode.

I'll fix it up.

  reply	other threads:[~2004-05-18  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 23:02 Robert M. Stockmann
2004-05-17 23:18 ` Valdis.Kletnieks
2004-05-17 23:19 ` Andrew Morton
2004-05-17 23:50   ` Robert M. Stockmann
2004-05-18  0:04     ` Andrew Morton
2004-05-18  0:13       ` Robert M. Stockmann
2004-05-18  0:50       ` viro
2004-05-18  1:03         ` Andrew Morton [this message]
2004-05-17 23:29 Valdis.Kletnieks

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=20040517180312.4560e6da.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stock@stokkie.net \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    --subject='Re: ramdisk driver in 2.6.6 has a severe bug' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).