On Mon, 2007-06-11 at 14:02 -0500, Serge E. Hallyn wrote:
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
Hi!
How will kernel work with very long paths? I'd suspect some problems,
if path is 1MB long and I attempt to print it in /proc
somewhere.
Pathnames are only used for informational purposes in the kernel, except
in AppArmor of course. /proc only uses pathnames in a few
Quoting Stephen Smalley ([EMAIL PROTECTED]):
On Mon, 2007-06-11 at 14:02 -0500, Serge E. Hallyn wrote:
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
On Tue, 2007-06-12 at 10:34 -0500, Serge E. Hallyn wrote:
Quoting Stephen Smalley ([EMAIL PROTECTED]):
[...]
If we added support for named type transitions to SELinux, as proposed
earlier by Kyle Moffett during this discussion, wouldn't that address
that issue without needing a
Quoting Karl MacMillan ([EMAIL PROTECTED]):
On Tue, 2007-06-12 at 10:34 -0500, Serge E. Hallyn wrote:
Quoting Stephen Smalley ([EMAIL PROTECTED]):
[...]
If we added support for named type transitions to SELinux, as proposed
earlier by Kyle Moffett during this discussion, wouldn't
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 suspect
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 wrote:
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 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 suspect some problems,
if path is 1MB long and I attempt to print it in
Hi!
How will kernel work with very long paths? I'd suspect some problems,
if path is 1MB long and I attempt to print it in /proc
somewhere.
Pathnames are only used for informational purposes in the kernel, except in
AppArmor of course. /proc only uses pathnames in a few places,
but
On Saturday 09 June 2007 14:58, Pavel Machek wrote:
How will kernel work with very long paths? I'd suspect some problems,
if path is 1MB long and I attempt to print it in /proc
somewhere.
Pathnames are only used for informational purposes in the kernel, except
in AppArmor of
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 suspect some problems,
if path is 1MB long and I attempt to print it in /proc
somewhere.
Pathnames are only used for
On Wed 2007-05-23 18:16:45, Andreas Gruenbacher wrote:
On Tuesday 15 May 2007 11:14, Pavel Machek wrote:
Why is this configurable?
The maximum length of a pathname is an arbitrary limit: we don't want to
allocate arbitrary amounts of of kernel memory for pathnames so we introduce
this
On Monday 04 June 2007 12:55, Pavel Machek wrote:
On Wed 2007-05-23 18:16:45, Andreas Gruenbacher wrote:
On Tuesday 15 May 2007 11:14, Pavel Machek wrote:
Why is this configurable?
The maximum length of a pathname is an arbitrary limit: we don't want to
allocate arbitrary amounts of of
On Mon 2007-06-04 13:25:30, Andreas Gruenbacher wrote:
On Monday 04 June 2007 12:55, Pavel Machek wrote:
On Wed 2007-05-23 18:16:45, Andreas Gruenbacher wrote:
On Tuesday 15 May 2007 11:14, Pavel Machek wrote:
Why is this configurable?
The maximum length of a pathname is an
On Monday 04 June 2007 13:35, Pavel Machek wrote:
On Mon 2007-06-04 13:25:30, Andreas Gruenbacher wrote:
On Monday 04 June 2007 12:55, Pavel Machek wrote:
On Wed 2007-05-23 18:16:45, Andreas Gruenbacher wrote:
On Tuesday 15 May 2007 11:14, Pavel Machek wrote:
Why is this
Hi!
You very well know that the vfs has a limit of PATH_MAX characters (4096)
for pathnames. This means that at most that many characters can be passed
at once.
What users can do is something like this:
chdir(some/long/path);
chdir(some/even/longer/path);
...
and the
On Monday 04 June 2007 15:12, Pavel Machek wrote:
How will kernel work with very long paths? I'd suspect some problems,
if path is 1MB long and I attempt to print it in /proc
somewhere.
Pathnames are only used for informational purposes in the kernel, except in
AppArmor of course. /proc only
Module parameters, LSM hooks, initialization and teardown.
Signed-off-by: John Johansen [EMAIL PROTECTED]
Signed-off-by: Andreas Gruenbacher [EMAIL PROTECTED]
Index: b/security/apparmor/lsm.c
===
--- /dev/null
+++
19 matches
Mail list logo
