From: Giana <Giana_gn@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: I have a problem with signal mask
Date: Wed, 3 Oct 2007 05:16:05 -0700 (PDT) [thread overview]
Message-ID: <13017702.post@talk.nabble.com> (raw)
Hello,
I have done Streams multiplexers in Linux kernel. Created two multiplexers
and I could open these 2, close the file descriptors of each and could
link/unlink one with another properly .
But after linking, if i close the descriptor of the linked one: my signals
are unblocked automatically....
Scenario:
1. Created 2 Multiplexers. Link B under A.
2. Now I set SIG_BLOCK to my current running process.
3. Close file descriptor of B
4. Now the signals are received by the process, It automatically goes for
UN_BLOCK
5. But I want the SIG_BLOCK state should be continued in this case....
Only in this scenario, it happens. All other scenarios like (Unlink without
close fd / close fd with out link) works fine....
Please give me some suggestion on this....
Thanks & Regards,
Giana
--
View this message in context: http://www.nabble.com/I-have-a-problem-with-signal-mask-tf4561448.html#a13017702
Sent from the linux-kernel mailing list archive at Nabble.com.
reply other threads:[~2007-10-03 12:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=13017702.post@talk.nabble.com \
--to=giana_gn@yahoo.com \
--cc=linux-kernel@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