lkml.org 
[lkml]   [1999]   [Dec]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Can't hardlink in different dirs. (BUG#826)


On Sun, 5 Dec 1999, Alan Curry wrote:

> Alexander Viro writes the following:
> >
> >On Fri, 3 Dec 1999, Pavel Machek wrote:
> >
> >> Is not this bug of fuser? I mean, if someone has file opened, should
> >> not it be visible by fuser?
> >
> >The whole point being that _nobody_ has it opened. It was attached to a
>
> Still, it's a bug if this information is not exported to userspace *somehow*,
> by /proc/inflight or something.

Just _what_ information do you want to get from there? That some packet
has a reference to file? Great. Gonna love this DoS - you'll have to lock
the whole thing to do that and it will not be a fast operation. OK, you
did it. So? Yes, we know that somebody holds such a reference. Fine. Who?
The destination may change. Easily. Moreover, if several processes hold
have the receiveing socket opened _any_ of them may get the packet. Better
yet, there may be no one having such a thing - socket itself may be passed
the same way. Want to trace _all_ pathes? 'cause many pointers can be
passed that way... You are not even promised that there will be no loops.
Good luck dealing with that.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

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