lkml.org 
[lkml]   [2004]   [Nov]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Problem with ioctl command TCGETS
    Hi!

    > > > The set-get is supposed to be used for queries, too? The size of value is
    > > > only used for the get case to describe the buffer length in that case?
    > > > because otherwise the set-get case may require a short value in and a large
    > > > answer structure out.
    > >
    > > You misunderstand the motivation. This is to get/set small compact
    > > parameters, not huge structures or big data. Think get/setsockopt().
    >
    > Think read(2)/write(2). We already have several barfbags too many,
    > and that includes both ioctl() and setsockopt(). We are stuck with
    > them for compatibility reasons, but why the hell would we need yet
    > another one?

    Passing structure using read/write is evil, because there's nowhere to hook
    32/64 bit translation.
    --
    64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms

    -
    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: 2005-03-22 14:08    [W:7.128 / U:0.076 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site