Re: F_CTRLFD (was Re: Why side-effects on open(2) are evil.)

2001-05-20 Thread Alexander Viro
On Sun, 20 May 2001, Edgar Toernig wrote: > IMHO any similar powerful (and versatile) interface will see the same > problems. Enforcing a read/write like interface (and rejecting drivers > that pass ptrs through this interface) may give you some knowledge about > the kernel/userspace

Re: F_CTRLFD (was Re: Why side-effects on open(2) are evil.)

2001-05-20 Thread Edgar Toernig
Alexander Viro wrote: > > On Sun, 20 May 2001, Edgar Toernig wrote: > > > IMHO any scheme that requires a special name to perform ioctl like > > functions will not work. Often you don't known the name of the > > device you're talking to and then you're lost. > > ls -l /proc/self/fd/ Oh come

Re: F_CTRLFD (was Re: Why side-effects on open(2) are evil.)

2001-05-20 Thread Alexander Viro
On Sun, 20 May 2001, Edgar Toernig wrote: > IMHO any scheme that requires a special name to perform ioctl like > functions will not work. Often you don't known the name of the > device you're talking to and then you're lost. ls -l /proc/self/fd/ and think of the results. We can export that

Re: F_CTRLFD (was Re: Why side-effects on open(2) are evil.)

2001-05-20 Thread Edgar Toernig
Alexander Viro wrote: > > For the latter, though, > we need to write commands into files and here your miscdevices (or procfs > files, or /dev/foo/ctl - whatever) is needed. IMHO any scheme that requires a special name to perform ioctl like functions will not work. Often you don't known the

Re: F_CTRLFD (was Re: Why side-effects on open(2) are evil.)

2001-05-20 Thread Edgar Toernig
Alexander Viro wrote: For the latter, though, we need to write commands into files and here your miscdevices (or procfs files, or /dev/foo/ctl - whatever) is needed. IMHO any scheme that requires a special name to perform ioctl like functions will not work. Often you don't known the name

Re: F_CTRLFD (was Re: Why side-effects on open(2) are evil.)

2001-05-20 Thread Alexander Viro
On Sun, 20 May 2001, Edgar Toernig wrote: IMHO any similar powerful (and versatile) interface will see the same problems. Enforcing a read/write like interface (and rejecting drivers that pass ptrs through this interface) may give you some knowledge about the kernel/userspace

Re: F_CTRLFD (was Re: Why side-effects on open(2) are evil.)

2001-05-20 Thread Edgar Toernig
Alexander Viro wrote: On Sun, 20 May 2001, Edgar Toernig wrote: IMHO any scheme that requires a special name to perform ioctl like functions will not work. Often you don't known the name of the device you're talking to and then you're lost. ls -l /proc/self/fd/n Oh come on. You

Re: F_CTRLFD (was Re: Why side-effects on open(2) are evil.)

2001-05-20 Thread Alexander Viro
On Sun, 20 May 2001, Edgar Toernig wrote: IMHO any scheme that requires a special name to perform ioctl like functions will not work. Often you don't known the name of the device you're talking to and then you're lost. ls -l /proc/self/fd/n and think of the results. We can export that as