All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abramo Bagnara <abramo.bagnara@libero.it>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Davide Libenzi <davidel@xmailserver.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Synchronous signal delivery..
Date: Fri, 14 Feb 2003 09:55:24 +0100	[thread overview]
Message-ID: <3E4CAEFC.92914AB3@libero.it> (raw)
In-Reply-To: Pine.LNX.4.44.0302131452450.4232-100000@penguin.transmeta.com

Linus Torvalds wrote:
> 
> On Thu, 13 Feb 2003, Davide Libenzi wrote:
> >
> > It does not have necessarily to be just another ioctl/fcntl, it can be a
> > write. About security, chages might be allowed only to the task that
> > created the fd, if you're concerned. It's not that someone will starve
> > w/out such functionality though.
> 
> I'd actually like to reserve writes to _sending_ signals. Especially if
> you have another process that listens in on the signals you get, it might
> want to also force the signals through.

This reminds me the unfortunate (and much needed) lack of an unified way
to send/receive out-of-band data to/from a regular fd.

Something like:
	oob = fd_open(fd, channel, flags);
	write(oob, ...)
	read(oob, ....)
	close(oob);

Don't you think it's time to introduce it and to start to avoid the
proliferation of different tricky ways to do the same things?

-- 
Abramo Bagnara                       mailto:abramo.bagnara@libero.it

Opera Unica                          Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy

  reply	other threads:[~2003-02-14  8:45 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 19:46 Synchronous signal delivery Linus Torvalds
2003-02-13 20:22 ` Davide Libenzi
2003-02-13 20:25   ` Linus Torvalds
2003-02-13 22:26     ` Davide Libenzi
2003-02-13 22:54       ` Linus Torvalds
2003-02-14  8:55         ` Abramo Bagnara [this message]
2003-02-14 14:24           ` Alan Cox
2003-02-14 13:57             ` Abramo Bagnara
2003-02-15 12:36               ` Ingo Oeser
2003-02-15 17:59                 ` Abramo Bagnara
2003-02-16 14:52                   ` Ingo Oeser
2003-02-15  0:00         ` Davide Libenzi
2003-02-15  0:06           ` Matti Aarnio
2003-02-15  1:08             ` Linus Torvalds
2003-02-15  1:30               ` Jeff Garzik
2003-02-15  1:23             ` Davide Libenzi
2003-02-15  1:03           ` Linus Torvalds
2003-02-15  2:09             ` Davide Libenzi
2003-02-15 20:08               ` Linus Torvalds
2003-02-15 23:39                 ` Davide Libenzi
2003-02-17  2:28                 ` Jan Harkes
2003-02-15  5:04             ` Keith Adamson
2003-02-15 19:19           ` James Antill
2003-02-15 22:31             ` Davide Libenzi
2003-02-17 23:34               ` James Antill
2003-02-17 15:26           ` Daniel Heater
2003-02-15  4:08   ` Werner Almesberger
2003-02-15 22:00     ` Davide Libenzi
2003-02-16  0:18       ` Werner Almesberger
2003-02-17  4:46     ` Jamie Lokier
2003-02-13 20:45 ` Paul P Komkoff Jr
2003-02-13 21:25   ` Richard B. Johnson
2003-03-27 21:40   ` watching for file creation completion [was Re: Synchronous signal delivery..] Alexander Kellett
2003-02-14  2:40 ` Synchronous signal delivery Jamie Lokier
2003-02-14  3:11   ` Keith Adamson
2003-02-14  3:54     ` Keith Adamson
2003-02-15  0:04   ` Davide Libenzi
2003-02-15  1:01     ` Jamie Lokier
2003-02-15  1:12       ` Randy.Dunlap
2003-02-15  1:50       ` Davide Libenzi
2003-02-15  2:08         ` Jamie Lokier
2003-02-15  4:09           ` Davide Libenzi
2003-02-15  4:34             ` Jamie Lokier
2003-02-14 10:55 ` Giuliano Pochini
2003-02-14 13:04   ` Keith Adamson
2003-02-15  4:25   ` Werner Almesberger
2003-02-15  5:14     ` Werner Almesberger
  -- strict thread matches above, loose matches on Subject: below --
2003-02-14  7:09 Dan Kegel

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=3E4CAEFC.92914AB3@libero.it \
    --to=abramo.bagnara@libero.it \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.