mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: NWFS broken on 2.4.3 -- someone removed WRITERAW
Date: Mon, 23 Apr 2001 17:01:58 -0600	[thread overview]
Message-ID: <20010423170158.A1543@vger.timpanogas.org> (raw)
In-Reply-To: <20010423163725.C1131@vger.timpanogas.org> <20010424005809.Y9357@suse.de>
In-Reply-To: <20010424005809.Y9357@suse.de>; from axboe@suse.de on Tue, Apr 24, 2001 at 12:58:09AM +0200

On Tue, Apr 24, 2001 at 12:58:09AM +0200, Jens Axboe wrote:
> On Mon, Apr 23 2001, Jeff V. Merkey wrote:
> > 
> > 
> > Hey guys,
> > 
> > Whomever removed WRITERAW has broken NWFS.  WRITE requests call
> > _refile_buffer() after the I/O request and take my locally created 
> > buffer heads and munge them back into the linux buffer cache, causing
> > massive memory corruption in the system.  These buffers don't belong 
> > in Linus' buffer cache, they are owned by my LRU and ll_rw_block 
> > should not be blindly filing them back into the buffer cache.
> > 
> > Please put something back in to allow me to write without the buffer
> > heads always getting filed into Linus' buffer cache.  This has 
> > broken NWFS on 2.4.3 and above.
> 
> 	bh->b_end_io = my_end_io_handler;
> 	submit_bh(WRITE, bh);


Jens,

Bless you.  I'll code the fix, test it, and get it out.  

Jeff

> 
> Be a happy camper.
> 
> -- 
> Jens Axboe
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2001-04-23 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 22:37 Jeff V. Merkey
2001-04-23 22:58 ` Jens Axboe
2001-04-23 23:01   ` Jeff V. Merkey [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=20010423170158.A1543@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=axboe@suse.de \
    --cc=jmerkey@timpanogas.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®