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:	Mon, 7 Feb 2011 09:30:22 -0600
From:	Eric Van Hensbergen <ericvh@...il.com>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc:	v9fs-developer@...ts.sourceforge.net,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [V9fs-developer] [RFC PATCH -V2 06/17] fs/9p: Add fid to inode in
 cached mode

On Sat, Feb 5, 2011 at 11:46 AM, Aneesh Kumar K.V
<aneesh.kumar@...ux.vnet.ibm.com> wrote:
> The fid attached to inode will be opened O_RDWR mode and is used
> for dirty page writeback only.
>
> FIXME!!: Should we make the fid owned by uid = 0
>

Good question, the idea was for the kernel to own the fid while the
cache needed it.  Although
its unlikely to ever be matched to anything else since its an "open"
fid (so it won't be a candidate
for a walk).  It might be more secure to have it owned by some special
constant (a NOUID which could be ~0)
and marks the fid as being owned by the client and no one else without
any sort of implication of authority/ownership.
We could then put a special check in the find fid code to ignore any
fids with NOUID.

      -eric
--
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/

Powered by blists - more mailing lists