public inbox for cluster-cvs@sourceware.org
help / color / mirror / Atom feed
From: bmarzins@sourceware.org
To: cluster-cvs@sources.redhat.com
Subject: cluster/gnbd-kernel/src gnbd.c
Date: Thu, 09 Nov 2006 21:22:00 -0000	[thread overview]
Message-ID: <20061109212240.7053.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Branch: 	RHEL4
Changes by:	bmarzins@sourceware.org	2006-11-09 21:22:40

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

Log message:
	It was previously possible to confuse gnbd by sending a process a signal while
	gnbd was writing to the socket (bz 210453). This usually hangs the socket, but
	can possibly cause data corruption. To fix this gnbd now only handles signals
	for gnbd_recvd.  GNBD blocks all signals for all other processes while it
	is going socket IO, so that a partial IO will never be send to the server,
	except when the connection is lost.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gnbd-kernel/src/gnbd.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.6.2.2&r2=1.6.2.3


             reply	other threads:[~2006-11-09 21:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 21:22 bmarzins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-28  6:13 fabbione
2007-06-19 22:34 bmarzins
2007-06-19 22:31 bmarzins
2007-01-05 23:01 bmarzins
2006-12-18 18:18 bmarzins
2006-12-18 18:17 bmarzins
2006-12-18 18:15 bmarzins
2006-08-08 21:04 bmarzins
2006-07-12 17:34 bmarzins
2006-06-02 19:58 bmarzins
2006-06-02 19:53 bmarzins
2006-03-17  0:43 bmarzins
2006-02-13 20:34 bmarzins
2006-02-13 20:21 cfeist
2006-02-13 20:20 cfeist
2005-06-21 15:39 bmarzins
2005-06-21 10:49 teigland
2005-05-09 23:05 jbrassow
2005-04-29 14:54 bmarzins
2005-04-20 18:23 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=20061109212240.7053.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).