From: "Stephen C. Tweedie" <sct@redhat.com>
To: Chuck Lever <cel@monkey.org>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-mm@kvack.org
Subject: Re: [PATCHES]
Date: Sat, 29 May 1999 02:24:38 +0100 (BST) [thread overview]
Message-ID: <14159.16854.992122.731801@dukat.scot.redhat.com> (raw)
In-Reply-To: <Pine.BSF.4.03.9905280125360.18892-100000@funky.monkey.org>
Hi,
On Fri, 28 May 1999 01:30:58 -0400 (EDT), Chuck Lever <cel@monkey.org> said:
> On Fri, 28 May 1999, Stephen C. Tweedie wrote:
>> Fixed patch for 2.2.9 is at
>>
>> ftp://ftp.uk.linux.org/pub/linux/sct/fs/misc/fsync-2.2.9-a.diff
> oops... one more thing. invalidate_buffers() and set_blocksize() both
> need to call remove_inode_queue() for each reclaimed buffer,
Quite right --- done. I've now checked that there aren't any other
places where we clear BH_Dirty. Updated patch in the usual place.
> and create_buffers() should set b_inode to NULL on all the new buffers
> on a page, for cleanliness. IMHO.
New buffer_heads are preinitialised to all-zeros anyway (search buffer.c
for "memset").
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-05-29 1:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-23 3:36 [PATCHES] Eric W. Biederman
1999-05-23 6:03 ` [PATCHES] Linus Torvalds
1999-05-23 14:54 ` [PATCHES] Eric W. Biederman
1999-05-23 15:49 ` [PATCHES] Ingo Molnar
1999-05-23 18:34 ` [PATCHES] Eric W. Biederman
1999-05-27 6:24 ` [PATCHES] Stephen C. Tweedie
1999-05-27 19:55 ` [PATCHES] Chuck Lever
1999-05-27 23:39 ` [PATCHES] Stephen C. Tweedie
1999-05-28 5:30 ` [PATCHES] Chuck Lever
1999-05-29 1:24 ` Stephen C. Tweedie [this message]
1999-05-30 17:01 ` [PATCHES] Eric W. Biederman
1999-05-27 6:25 ` [PATCHES] Stephen C. Tweedie
1999-05-24 17:20 ` [PATCHES] Manfred Spraul
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=14159.16854.992122.731801@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=cel@monkey.org \
--cc=linux-mm@kvack.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