public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
* cluster/gfs-kernel/src/gfs incore.h log.h ops_ ...
@ 2005-03-03 16:35 bmarzins
0 siblings, 0 replies; 2+ messages in thread
From: bmarzins @ 2005-03-03 16:35 UTC (permalink / raw)
To: cluster-cvs
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: bmarzins@sourceware.org 2005-03-03 16:35:20
Modified files:
gfs-kernel/src/gfs: incore.h log.h ops_fstype.c
Log message:
Fixed 146672. While it is still possible to see this bug, the problem that I
saw every time it happened to me was that the process in gfs_log_dump() got
starved waiting for the sd_log_lock semaphore. This fix changes sd_log_lock into
a rw_semaphore, and uses down_write and up_write instead of down and up.
read write semaphores are totally fair, so gfs_log_dump() can't get starved
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/incore.h.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.17&r2=1.17.2.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/log.h.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.2&r2=1.2.2.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.13&r2=1.13.2.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* cluster/gfs-kernel/src/gfs incore.h log.h ops_ ...
@ 2005-03-03 16:38 bmarzins
0 siblings, 0 replies; 2+ messages in thread
From: bmarzins @ 2005-03-03 16:38 UTC (permalink / raw)
To: cluster-cvs
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: bmarzins@sourceware.org 2005-03-03 16:38:50
Modified files:
gfs-kernel/src/gfs: incore.h log.h ops_fstype.c
Log message:
Fixed 146672. While it is still possible to see this bug, the problem that I
saw every time it happened to me was that the process in gfs_log_dump() got
starved waiting for the sd_log_lock semaphore. This fix changes sd_log_lock into
a rw_semaphore, and uses down_write and up_write instead of down and up.
read write semaphores are totally fair, so gfs_log_dump() can't get starved
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/incore.h.diff?cvsroot=cluster&r1=1.17&r2=1.18
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/log.h.diff?cvsroot=cluster&r1=1.2&r2=1.3
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&r1=1.14&r2=1.15
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-03 16:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-03-03 16:35 cluster/gfs-kernel/src/gfs incore.h log.h ops_ bmarzins
2005-03-03 16:38 bmarzins
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).