[lkml]   [2006]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: How to lock current->signal->tty
> Ar Maw, 2006-08-08 am 08:10 -0700, ysgrifennodd Arjan van de Ven:
> > > Unfortunately:
> > > Dquot passes the tty to tty_write_message without locking
> > > arch/ia64/kernel/unanligned seems to write to it without locking
> >
> > these two have absolutely no business at all using anything tty.... they should
> > just use printk with KERN_EMERG or whatever
> Dquot does - it writes to the controlling tty of the process exceeding
> quota . That is standard Unix behaviour
Yes. On one hand I find this behaviour kind of inconsistent (Unix usually
just returns an error code and that's it) but on the other hand there is
no other good way of informing user about e.g. exceeded quota soft
So I'll just fix up the tty locking ;).


Jan Kara <>
SuSE CR Labs
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: 2006-08-09 00:07    [W:0.056 / U:1.360 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site