On Tue, Jun 12, 2007 at 09:07:36AM +1000, Nathan Scott wrote:
> On Mon, 2007-06-11 at 08:58 -0700, Chris Wedgwood wrote:
> > > In the way xfs_fsr operates now, in almost all user space, I don't
> > > see any good way to tell XFS where to place the extents, other than
> > > creating the temporary fi
On Tue, 12 June 2007 01:51:34 +0200, Arnd Bergmann wrote:
> On Tuesday 12 June 2007, Jörn Engel wrote:
> > The initial storm of review comments has calmed down. I get the
> > impression that people either lose interest or run out of simple things
> > to point out. Maybe I should wait a bit before
On Tuesday 12 June 2007, Jörn Engel wrote:
> The initial storm of review comments has calmed down. I get the
> impression that people either lose interest or run out of simple things
> to point out. Maybe I should wait a bit before resending?
Your last series had a todo list of 11 items, plus mo
On Sun, 10 June 2007 19:24:28 +0200, Arnd Bergmann wrote:
>
> I think this is missing code that sets the initial i_uid/i_gid,
> but there may be more missing. Changing the uid value works,
> but creating files as non-root user doesn't.
Fixed in patch 557, see
http://logfs.org/logfs/patches
The i
Quoting Andreas Gruenbacher ([EMAIL PROTECTED]):
> On Monday 11 June 2007 16:33, Stephen Smalley wrote:
> > On Mon, 2007-06-11 at 01:10 +0200, Andreas Gruenbacher wrote:
> > > On Wednesday 06 June 2007 15:09, Stephen Smalley wrote:
> > > > On Mon, 2007-06-04 at 16:30 +0200, Andreas Gruenbacher wrot
On Mon, Jun 11, 2007 at 10:38:18AM +0100, Steven Whitehouse wrote:
> Hi,
>
> On Sat, 2007-06-09 at 09:35 -0700, Marc Eshel wrote:
> > This is the return code that setlease() currently returns when the lease
> > can not be obtained. Although ENOTSUPP would be more accurately describing
> > the er
On Sat, Jun 09, 2007 at 09:56:29AM -0700, Marc Eshel wrote:
> We need to export vfs_lease so nfsd can call it.
Oops, thanks for finding that--done.--b.
--b.
diff --git a/fs/locks.c b/fs/locks.c
index 82ac90b..c2fd0a5 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1453,6 +1453,8 @@ int vfs_setlease
On Monday 11 June 2007 16:33, Stephen Smalley wrote:
> On Mon, 2007-06-11 at 01:10 +0200, Andreas Gruenbacher wrote:
> > On Wednesday 06 June 2007 15:09, Stephen Smalley wrote:
> > > On Mon, 2007-06-04 at 16:30 +0200, Andreas Gruenbacher wrote:
> > > > On Monday 04 June 2007 15:12, Pavel Machek wro
On Sat, 2007-06-09 at 00:03 +0200, Andreas Gruenbacher wrote:
> On Wednesday 06 June 2007 15:26, Stephen Smalley wrote:
> > - under AA, each file may have an arbitrary set of "labels" or
> > "policies" applied to it depending on what programs are accessing it and
> > what names are being used to re
On Mon, 2007-06-11 at 01:10 +0200, Andreas Gruenbacher wrote:
> On Wednesday 06 June 2007 15:09, Stephen Smalley wrote:
> > On Mon, 2007-06-04 at 16:30 +0200, Andreas Gruenbacher wrote:
> > > On Monday 04 June 2007 15:12, Pavel Machek wrote:
> > > > How will kernel work with very long paths? I'd su
On Mon, 11 Jun 2007 02:33:30 -0700 (PDT)
[EMAIL PROTECTED] wrote:
> Ok, you are proposing throwing out all the label handling that SELinux
> does, including any caching. forgive me if I agree with the SELinux people
> that this is a very bad idea.
Well presumably AA would be doing caching etc..
Hi!
> ACPI should have taught everyone that sometimes putting an interpreter in
> the kernel really is the best option. looking at the problems of bouncing
> back out to userspace for file creation and renames it looks like a regex
> in the kernel is a lot safer and more reliable.
What do ACPI
Hi,
On Sat, 2007-06-09 at 09:35 -0700, Marc Eshel wrote:
> This is the return code that setlease() currently returns when the lease
> can not be obtained. Although ENOTSUPP would be more accurately describing
> the error it will be a new return code from setlease() that is currently
> not expec
On Mon, 11 Jun 2007, Sean wrote:
[EMAIL PROTECTED] wrote:
say that we give each file a unique label, and for simplicity we set the
label == path (note that this raises the issue, what will SELinux do when
there are multiple paths to the same file)
So don't do that then.
now say that you wa
On Sun, 10 Jun 2007 23:45:16 -0700 (PDT)
[EMAIL PROTECTED] wrote:
> say that we give each file a unique label, and for simplicity we set the
> label == path (note that this raises the issue, what will SELinux do when
> there are multiple paths to the same file)
So don't do that then.
> now say
15 matches
Mail list logo
