From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: Csaba Kos <csaba.kos@gmail.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH] deadlock in script
Date: Mon, 2 Jun 2014 11:37:59 +0200 [thread overview]
Message-ID: <201406021138.00417.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20140602090840.GL9000@x2.net.home>
On Monday 02 June 2014, Karel Zak wrote:
> On Fri, May 30, 2014 at 06:52:20PM +0900, Csaba Kos wrote:
> > On Fri, May 30, 2014 at 6:15 PM, Karel Zak <kzak@redhat.com> wrote:
> > > On Fri, May 30, 2014 at 03:30:45PM +0900, Csaba Kos wrote:
> > >> diff --git a/term-utils/script.c b/term-utils/script.c
> > >> index e5d239c..32906d0 100644
> > >> --- a/term-utils/script.c
> > >> +++ b/term-utils/script.c
> > >> @@ -36,6 +36,9 @@
> > >> * - added Native Language Support
> > >> *
> > >> * 2000-07-30 Per Andreas Buer <per@linpro.no> - added
> > >> "q"-option + *
> > >> + * 2014-05-30 Csaba Kos <csaba.kos@gmail.com>
> > >> + * - fixed a rare deadlock after child termination
> > >> */
> > >>
> > >> /*
> > >> @@ -114,6 +117,8 @@ int tflg = 0;
> > >> int forceflg = 0;
> > >> int isterm;
> > >>
> > >> +sigset_t block_mask, unblock_mask;
> > >
> > > This declaration shadows declaration in main() where is also
> > > block_mask and unblock_mask -- I guess it's not expected.
> >
> > Sorry, I goofed when updating my patch to the current master.
> > Thanks for the careful review! Updated patch attached.
>
> All applied, thanks!
>
> Karel
Could this already fix the TODO in
tests/ts/script/race (6cae66ea)?:
# TODO see comments about script design
# https://github.com/karelzak/util-linux/pull/62
TS_KNOWN_FAIL="yes"
cu,
Rudi
next prev parent reply other threads:[~2014-06-02 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 6:30 [PATCH] deadlock in script Csaba Kos
2014-05-30 9:15 ` Karel Zak
2014-05-30 9:52 ` Csaba Kos
2014-06-02 9:08 ` Karel Zak
2014-06-02 9:37 ` Ruediger Meier [this message]
2014-06-02 9:57 ` Karel Zak
2014-06-02 10:03 ` Ruediger Meier
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=201406021138.00417.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=csaba.kos@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox