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/recovery.c gnbd-ker ...
Date: Fri, 10 Nov 2006 22:16:00 -0000	[thread overview]
Message-ID: <20061110221647.24248.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL5
Changes by:	bmarzins@sourceware.org	2006-11-10 22:16:47

Modified files:
	gfs-kernel/src/gfs: recovery.c 
	gnbd-kernel/src: gnbd.c 

Log message:
	fix for bz215095 & 215099.
	
	for 215099, gnbd now only handles signals in sock_xmit() when it is called by
	the gnbd_recvd process. Otherwise, it simply blocks the signals until it
	completes the IO. This keeps gnbd from sending partial requests to the
	server, which can lead to data corruption.
	
	for 215095, the gfs function clean_journal() now uses the noinline attriubute,
	gfs_find_jhead() only uses on struct gfs_log_header, and gfs_recover_journal()
	dynamically allocates its struct gfs_log_header, all to conserve stack space.
	
	In the gnbd function sock_xmit(), you no longer get the signal info, so
	gnbd_recvd cannot print which signal it received, but it saves over 120 bytes
	of stack space.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/recovery.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.9&r2=1.9.2.1
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gnbd-kernel/src/gnbd.c.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.15&r2=1.15.2.1


             reply	other threads:[~2006-11-10 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 22:16 bmarzins [this message]
2006-11-10 22:17 bmarzins
2006-11-21 22:01 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=20061110221647.24248.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).