From: Philippe Troin <phil@fifi.org>
To: Jason Gunthorpe <jgg@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lost O_NONBLOCK (Bug?)
Date: 19 Apr 2001 10:47:32 -0700 [thread overview]
Message-ID: <87n19czsqz.fsf@tantale.fifi.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1010413141220.7113E-100000@wakko.deltatee.com>
In-Reply-To: <Pine.LNX.3.96.1010413141220.7113E-100000@wakko.deltatee.com>
Jason Gunthorpe <jgg@debian.org> writes:
> On 12 Apr 2001, Philippe Troin wrote:
>
> > Apt I guess ? It has a very strange behavior when backgrounded...
>
> Not really, just want it tries to run dpkg it hangs.
>
> > > The last read was after the process was forgrounded. The read waits
> > > forever, the non-block flag seems to have gone missing. It is also a
> > > little odd I think that it repeated to get SIGTTIN which was never
> > > actually delivered to the program.. Shouldn't SIGTTIN suspend the process?
>
> > Strace can perturbate signal delivery, especially for terminal-related
> > signals, I wouldn't trust it...
>
> I know, the problem still happens without strace.
Do you have a snippet that can reproduce the problem ? Does this
happens only with 2.4, or both 2.2 and 2.4 have the problem ?
> > O_NONBLOCK is not lost... Attempting to read from the controlling tty
> > even from a O_NONBLOCK descriptor will trigger SIGTTIN.
>
> I don't really care about the SIGTTIN, what bugs me is that the read that
> happens after the process has been foregrounded blocks - and that should
> not be.
True.
8< snip >8
Phil.
prev parent reply other threads:[~2001-04-19 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 4:44 Jason Gunthorpe
2001-04-13 6:45 ` Philippe Troin
2001-04-13 20:16 ` Jason Gunthorpe
2001-04-19 17:47 ` Philippe Troin [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=87n19czsqz.fsf@tantale.fifi.org \
--to=phil@fifi.org \
--cc=jgg@debian.org \
--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
all inboxes | Powered by JetHome®