From: Bart Van Assche <bvanassche@acm.org>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Bart Van Assche <bvanassche@acm.org>,
Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: [PATCH v2] simplify multipath signal handlers
Date: Fri, 10 May 2013 20:23:38 +0200 [thread overview]
Message-ID: <518D3B2A.3040004@acm.org> (raw)
In-Reply-To: <20130508183604.GW6253@ether.msp.redhat.com>
On 05/08/13 20:36, Benjamin Marzinski wrote:
> This patch changes how multipath's signal handlers work. Instead of
> having sighup and sigusr1 acquire locks and call functions directly,
> they now both simply set atomic variables. These two signals are
> blocked in child(), and all other threads inherit this sigmask. The
> only place in all the multipath code that doesn't block these signals
> is now the ppoll() call by the uxlsnr thread. When it is interrupted
> by a signal, the uxlsnr thread does the actual processing work.
>
> Instead of sigend using mutex locks and condition variables to tell
> the child() function to exit, it now uses a signal_handler safe
> semaphore that child() waits on and exit_daemon() increments.
>
> This patch also switches all the sigprocmask() calls to
> pthread_sigmask()
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Thanks for addressing my comments.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2013-05-10 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 18:36 [PATCH v2] simplify multipath signal handlers Benjamin Marzinski
2013-05-10 18:23 ` Bart Van Assche [this message]
2013-05-13 18:02 ` Christophe Varoqui
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=518D3B2A.3040004@acm.org \
--to=bvanassche@acm.org \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@gmail.com \
--cc=dm-devel@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