From: "Stephen C. Tweedie" <sct@redhat.com>
To: linux-kernel@vger.kernel.org, Andrea Arcangeli <andrea@suse.de>
Cc: Ben LaHaise <bcrl@redhat.com>, Stephen Tweedie <sct@redhat.com>,
Tigran Aivazian <tigran@veritas.com>
Subject: Raw IO fixes for 2.4.2-ac8
Date: Fri, 2 Mar 2001 19:38:56 +0000 [thread overview]
Message-ID: <20010302193856.D28854@redhat.com> (raw)
Hi,
I've just uploaded the current raw IO fixes as
kiobuf-2.4.2-ac8-A0.tar.gz on
ftp.uk.linux.org:/pub/linux/sct/fs/raw-io/
and
ftp.*.kernel.org:/pub/linux/kernel/people/sct/raw-io/
This includes:
00-movecode.diff: move kiobuf code from mm/memory.c to fs/iobuf.c
02-faultfix.diff: fixes for faulting and pinning pages
03-unbind.diff: allow unbinding of raw devices
04-pgdirty.diff: use the new SetPageDirty to dirty pages after reads
05-bh-err.diff: fix cleanup of buffer_heads after ENOMEM
06-eio.diff: fix error returned on EIO in first block of IO
The first 3 of these are from the current 2.2 raw patches. The 4th is
the fix for dirtying pages after raw reads, using the new
functionality of the 2.4 VM. The 5th and 6th fix up problems
introduced when brw_kiovec was moved to use submit_bh().
Cheers,
Stephen
reply other threads:[~2001-03-02 19:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010302193856.D28854@redhat.com \
--to=sct@redhat.com \
--cc=andrea@suse.de \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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