public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: bmarzins@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/gfs-kernel/src/gfs incore.h log.c ops_ ...
Date: Thu, 28 Apr 2005 22:14:00 -0000 [thread overview]
Message-ID: <20050428221404.11238.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4U1
Changes by: bmarzins@sourceware.org 2005-04-28 22:14:04
Modified files:
gfs-kernel/src/gfs: incore.h log.c ops_fstype.c
Log message:
This is theoretically a fix for bz #155597 (which I have never been able to
reproduce, and thus test this fix against). GFS was able to overwrite
space on the ondisk journal that was still needed, causing journal corruption
that was noticeable if the machine crashed at the wrong time. This fixes
that. This fix involves allocating memory while holding the log lock. There
is a possibility that this could cause lockups in low memory situations.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/incore.h.diff?cvsroot=cluster&only_with_tag=RHEL4U1&r1=1.17.2.2&r2=1.17.2.2.2.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/log.c.diff?cvsroot=cluster&only_with_tag=RHEL4U1&r1=1.11.2.3&r2=1.11.2.3.2.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&only_with_tag=RHEL4U1&r1=1.13.2.1&r2=1.13.2.1.2.1
next reply other threads:[~2005-04-28 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 22:14 bmarzins [this message]
2005-04-29 15:07 bmarzins
2005-04-29 15:42 bmarzins
2005-04-29 16:29 bmarzins
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=20050428221404.11238.qmail@sourceware.org \
--to=bmarzins@sourceware.org \
--cc=cluster-cvs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).