lkml.org 
[lkml]   [2006]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    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
    limit.
    So I'll just fix up the tty locking ;).

    Honza

    --
    Jan Kara <jack@suse.cz>
    SuSE CR Labs
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-08-09 00:07    [W:0.028 / U:30.460 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site