public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Todd Poynor <tpoynor@mvista.com>
To: "Bill C. Riemers" <docbill@freeshell.org>
Cc: tytso@mit.edu, busybox@mail.codepoet.org, linux-kernel@vger.kernel.org
Subject: Re: [BusyBox] Re: [PATCH] BLKFLSBUF on ramdisks
Date: Fri, 28 May 2004 12:06:30 -0700	[thread overview]
Message-ID: <40B78DB6.1070003@mvista.com> (raw)
In-Reply-To: <003001c444b5$ff72cee0$64fda287@docbill002>

Bill C. Riemers wrote:
> Does this problem also effect the 2.4 kernels?
> 
> I'm just wondering, because it sounds like a possible explination for
> strange errors occurring with /dev/cobd? in coLinux, especially when used as
> swap devices.  Basically /dev/cobd? are simmular to ramdisks, but they
> refere to files mmap'ed under Windows.  They work fairly reliable, until
> someone does something like "swapoff -a;swapon -a".  However, coLinux is
> only used with 2.4 kernels, so if the problem does not effect 2.4 kernels,
> then this is not the cause.

Yes, Matt Porter previously determined that this behavior changed 
sometime after 2.4.2 and on or before 2.4.17, when rd.c was modified to 
perform a truncate_inode_pages() for BLKFLSBUF (could track down the 
date/revision more accurately if you're interested).

-- 
Todd

      reply	other threads:[~2004-05-28 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 23:19 [PATCH] BLKFLSBUF on ramdisks Todd Poynor
2004-05-28 13:06 ` [BusyBox] " Bill C. Riemers
2004-05-28 19:06   ` Todd Poynor [this message]

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=40B78DB6.1070003@mvista.com \
    --to=tpoynor@mvista.com \
    --cc=busybox@mail.codepoet.org \
    --cc=docbill@freeshell.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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