[lkml]   [2001]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: spin_lock_bh() usage check, please (was: [PATCH][RFC] Signal-per-fd for RT signals)
Dan Kegel wrote:

> so it crashes on a uniprocessor system when an interrupt that
> causes a sigio comes in while the process was busy expanding its
> file table, to wit:

I'm checking that. My variant of patch will be posted tomorrow, after I'll
finish testing it. It will be against 2.4.9 and addresses all crashes you've

> p.s. The bug was introduced by Luban's one-signal-per-fd patch; I ran into
> it while running my variant of his patch,
> My variant makes the following changes:
> * it fixes an oops related to 'task->files' being null during SIGINT
> * it fixes two oopses related to signal queue overflow
> * it keeps poll data, not pointers, in struct file. This saves space
> and makes the consequence of screwing up less severe.
> * it overloads an existing struct file field to avoid the space penalty;
> it doesn't bloat struct file.
> * it assumes that it's better to keep the kernel uncluttered, so it
> changes the meaning of siginfo.si_code rather than introduces new ioctl's.
> (I hear the Austin draft of the Posix single unix spec is deleting all mention
> of SIGIO, so it looks like we're free to 'improve' that interface freely
> once Austin becomes the law of the land :-)

I'm reluctant to make such changes, like f_error field overloading because
a) it may backbite in future if you'll use this mechanism for all I/O and not only
since you are interfering with it's legitimate usage, in short, it makes patch more
dependent of possible kernel code changes
b) I want the default kernel behavior to be exactly the same, as if without this
patch, thus additional fcntl to control this feature. If you do not activate it, you
don't get it,

Keeping pointer allows for additional sanity check to make sure I'm not screwed,
and cheap update events information in siginfo.
Keeping interests strips you of this ability. And also, you have to have additional
method of gettong events information in user space, because you are not updating
and cannot rely on it anymore. So, to utilize signal per fd feature you have to modify
event loop and not file descriptor setup, which I'd also try to avoid.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.041 / U:1.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site