zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: zsh-4.3.1[45] problem on FreeBSD
Date: Mon, 02 Jan 2012 11:07:04 -0800	[thread overview]
Message-ID: <120102110704.ZM10434@torch.brasslantern.com> (raw)
In-Reply-To: <120101120852.ZM12005@torch.brasslantern.com>

On Jan 1, 12:08pm, Bart Schaefer wrote:
}
} I wonder if we should just queue_signals()/unqueue_signals() around
} the entire body of zrefresh(), always?  Or is this the only place
} that's important?

As Herbert has now confirmed that the race can be resolved --

Although it probably wouldn't hurt anything to queue signals around
the bulk of zrefresh(), this part of zleread() is the only point at
which zleactive can be true before at least one call to zrefresh()
has completed; which, I think, means this is the only place where a
SIGWINCH could cause confusion.

I'd still like to know more about exactly what goes on under FreeBSD
in the case where it hangs, but I think the conservative approach is
to restrict the signal queuing to this one section.  I'll add a few
lines of comment and commit the patch.

Adding a further queue/unqueue inside zrefresh() later won't conflict,
should we find another such race condition.


      parent reply	other threads:[~2012-01-02 19:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26 20:01 Herbert J. Skuhra
2011-12-27  0:52 ` Herbert J. Skuhra
2011-12-27  2:31 ` Bart Schaefer
2011-12-27 20:38   ` Herbert J. Skuhra
2011-12-28  0:53     ` Bart Schaefer
2012-01-01 14:25       ` Herbert J. Skuhra
2012-01-01 20:08         ` Bart Schaefer
2012-01-02 11:38           ` Herbert J. Skuhra
2012-01-02 19:36             ` Bart Schaefer
2012-01-03 11:33               ` Herbert J. Skuhra
2012-01-11  9:20                 ` Baptiste Daroussin
2012-01-02 19:07           ` Bart Schaefer [this message]

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=120102110704.ZM10434@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).