linux-kernel - Re: How to tell whether a struct file is held by a process?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 May 2009 15:12:35 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Pantelis Koukousoulas <pktoss@...il.com>
Cc:	Kernel development list <linux-kernel@...r.kernel.org>,
	Kay Sievers <kay.sievers@...y.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: How to tell whether a struct file is held by a process?

> Who is "me" in this case? Assuming that those writing the userspace programs
> are cooperative though, I agree. We can declare that whatever program does not

The software authors.

> play by the (userspace locking) rules is crap and either fix it (if open source)
> or refuse to install it / complain (if closed source).

Which for the general case I think is reasonable. If the bad program is
determined to be bad then it can equally just ptrace the process with the
file open and drive it that way.

> >
> >> So, if there is a clean / acceptable way to handle the reset issue in userspace
> >
> > Firstly can you explain *why* you think there is a problem ?
> >
> 
> I admit this could be a bias from the way I imagined the whole thing
> to work before
> this discussion. I think I can see how a userspace locking scheme based on port
> numbers could avoid also the reset problem

That was a serious request to understand what you think the problem is
and what problem is worrying you. I'm deeply sceptical of the need for
any kernel locking on this one but I'd like to understand better why you
think there are some cases it would be needed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/