Same problem here with same hardware and KDE. I opened a bug report here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1247806. Any news about it
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
Am 2014-01-07 15:30, schrieb Ramkumar Ramachandra:
Seth Forshee wrote:
3. So what is really wanted is to be able to mux just the DDC over to
the IGPU when the device is initialized to read the panel mode.
One
possible problem is that the hw might not support muxing the DDC
separ
Am Fr 08.06.2007 21:01 schrieb Andrew Morton
<[EMAIL PROTECTED]>:
> On Fri, 8 Jun 2007 11:21:57 -0700
> "Keshavamurthy, Anil S" <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Jun 07, 2007 at 04:27:26PM -0700, Andrew Morton wrote:
> > > On Wed, 06 Jun 2007 11:57:00 -0700
> > > [EMAIL PROTECTED] wrote:
>
On Wednesday 06 June 2007 15:26, Stephen Smalley wrote:
> On Mon, 2007-06-04 at 23:03 +0200, Andreas Gruenbacher wrote:
> > [...] SELinux turns pathnames into labels when it
> > initially labels all files (when a policy is rolled out), whereas
> > AppArmor computes the "
e upper bound, and the drawback that access to exceptionally long paths
(beyond the arbitrary limit) is denied. So in a sense, the limit in AppArmor
does what you are asking for: it modifies things so that the kernel does not
allow "such crazy paths". It does not introduce this as a vfs l
On Saturday 09 June 2007 02:17, Greg KH wrote:
> On Sat, Jun 09, 2007 at 12:03:57AM +0200, Andreas Gruenbacher wrote:
> > AppArmor is meant to be relatively easy to understand, manage, and
> > customize, and introducing a labels layer wouldn't help these goals.
>
>
s, and we considered a fair number of
alternatives.
Have you seen the ``AppArmor FAQ'' thread?
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/major
20us.
Very nice, thanks!
> + /* Get the next period (per cpu)*/
> ts->sched_timer.expires = tick_init_jiffy_update();
> + offset = ktime_to_ns(tick_period) >> 1;
> + do_div(offset, NR_CPUS);
> + offset *= smp_processor_id();
Andreas Mohr
-
To unsub
Hi,
On Sun, Jun 10, 2007 at 04:31:03PM +0200, Thomas Gleixner wrote:
> That's one time during setup, no hot path.
Urks, should have looked at actual file then instead of patch context only,
sorry!
Andreas Mohr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel
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
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
inotify call d_path() on each
> open and glob match the result against a list of audit or inotify watches?
I don't remember doing so.
Thanks,
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majo
not. In
some (primitive) implementations it might no longer be possible to
distinguish between unwritten extents and zero-filled blocks, though
at this point DEALLOC of zero-filled blocks might not be harmful either.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File S
On Jun 14, 2007 22:04 +1000, David Chinner wrote:
> On Thu, Jun 14, 2007 at 03:14:58AM -0600, Andreas Dilger wrote:
> > > B FA_DEALLOCATE
> > > removes the underlying disk space with the given range. The disk space
> > > shall be removed regardless of it'
2, Athlon.
Signed-off-by: Andreas Mohr <[EMAIL PROTECTED]>
--- linux-2.6.22-rc4-mm2.orig/include/asm-i386/mc146818rtc.h2007-06-10
22:00:53.0 +0200
+++ linux-2.6.22-rc4-mm2/include/asm-i386/mc146818rtc.h 2007-06-09
21:40:21.0 +0200
@@ -43,8 +43,10 @@
un
he filesystem and RAID layers
can move beyond "ignorance is bliss" when talking to each other would be
great. Not rebuilding empty parts of the fs, limit parity resync to parts
of the fs that were in the previous transaction, use fs-supplied checksums
to verify on-disk data is correct,
This is a series of minor fixes for problems observed while
doing some randconfig fun on x86_64.
Some problems might have been reported on LKML before. But AFAIK they
are not fixed in current git. Thus I report them again - including
possible fixes.
Regards,
Andreas
--
Operating | AMD Saxony
x27; used by config symbol
'MOUSE_ATARI' refers to undefined symbol 'ATARI_KBD_CORE'
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
arch/m68k/Kconfig |3 ---
drivers/input/keyboard/Kconfig |4
2 files changed, 4 insertions(+), 3 deletions(-)
Fix kernel build problem:
thinkpad_acpi.c:(.text+0x7486a): undefined reference to `ec_write'
(as THINKPAD_ACPI depends on ACPI_EC)
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/misc/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/d
Fix kernel build problem as MSI_LAPTOP depends on ACPI_EC.
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/misc/Kconfig |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 72774c9..0d6f369 100644
Fix compile error with ACPI && !ACPI_POWER as bus.c
depends on power.c
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/acpi/Kconfig |4
drivers/acpi/Makefile |2 +-
2 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/drivers/acpi/Kconfig
Avoid compile warning if !ACPI_BLACKLIST_YEAR
CC drivers/acpi/blacklist.o
drivers/acpi/blacklist.c:76:5: warning: "CONFIG_ACPI_BLACKLIST_YEAR" is not
defined
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/acpi/blacklist.c |2 +-
1 files changed, 1
Fix build error if ACPI && !ACPI_SYSTEM as
bus.c depended on event.c
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/acpi/bus.c |2 +-
drivers/acpi/event.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/acpi/bus.c b/driv
Fix compile error:
In file included from drivers/infiniband/core/addr.c:32:
include/linux/inetdevice.h:15: error: '__NET_IPV4_CONF_MAX' undeclared here
(not in a function)
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
include/linux/inetdevice.h |1 +
1 files chang
':
xirc2ps_cs.c:(.exit.text+0x1055): undefined reference to
`pcmcia_unregister_driver'
make: *** [.tmp_vmlinux1] Error 1
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/net/pcmcia/Kconfig | 12 ++--
1 files changed, 10 insertions(+), 2 deletions(-)
diff
Fix kernel build problem as SONY_LAPTOP depends on ACPI_EC.
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
drivers/misc/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 0d6f369..463fa41 100644
rning: implicit declaration of function
'acpi_power_transition'
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index b4a9ea5..e01dca1 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -43,6 +43,8 @@ ACPI_MODULE_NAME(
mm/built-in.o:: more undefined references to `kmalloc_node' follow
... hmm, SLOB currently does not provide kmalloc_node() and friends.
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
init/Kconfig |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/init/Kconfig
Fix compile error:
CC sound/pci/ice1712/prodigy192.o
sound/pci/ice1712/prodigy192.c:708: error: ak4114_controls causes a section
type conflict
... but __initdata cannot be "const".
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
---
sound/pci/ice1712/prodigy19
On Tue, Jun 19, 2007 at 11:38:02PM -0400, Len Brown wrote:
> On Tuesday 19 June 2007 18:50, Andreas Herrmann wrote:
> > Avoid compile warning if !ACPI_BLACKLIST_YEAR
> >
> > CC drivers/acpi/blacklist.o
> > drivers/acpi/blacklist.c:76:5: warning: "CONFIG_
On Tue, Jun 19, 2007 at 08:51:58PM -0700, Randy Dunlap wrote:
> On Tue, 19 Jun 2007 20:49:34 -0700 Randy Dunlap wrote:
>
> > On Tue, 19 Jun 2007 23:38:02 -0400 Len Brown wrote:
> >
> > > On Tuesday 19 June 2007 18:50, Andreas Herrmann wrote:
> > > > Avoid
order = simple_strtoul(options, NULL, 10);
This is probably a bad name for a mount option. What about "order=10"?
Otherwise you prevent any other option from being used in the future.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsub
would break.
There shouldn't be a problem with increasing EXT{2,3,4}_MAX_BLOCK_SIZE to
32kB (AFAIK), but I haven't looked into this in a while.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "uns
past 64kB blocksize in any case.
> > There shouldn't be a problem with increasing EXT{2,3,4}_MAX_BLOCK_SIZE to
> > 32kB (AFAIK), but I haven't looked into this in a while.
>
> I'd love to see such a patch. That is also useful for arches that have
> PAGE_SIZE &
me a very expensive operation in at
least some cases (which are more than theoretical) would hurt those
applications, and nothing much could be done about it.
Adding better new-file mechanisms to SELinux probably is a good idea, and it
would weaken the SELinux seurity model for all I can t
works.
How exactly are struct vfsmount and struct dentry not in-kernel structures?
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
On Wed, Jun 20, 2007 at 01:44:35PM -0700, Randy Dunlap wrote:
> On Wed, 20 Jun 2007 00:52:03 +0200 Andreas Herrmann wrote:
>
> > Fix several build errors with PCMCIA=m && NET_PCMCIA=y:
> >
> >LD .tmp_vmlinux1
> >drivers/built-in.o: In functio
On Wed, Jun 20, 2007 at 11:25:48AM -0700, Ravikiran G Thirumalai wrote:
> On Wed, Jun 20, 2007 at 09:36:30AM -0400, Len Brown wrote:
> > On Wednesday 20 June 2007 04:49, Andreas Herrmann wrote:
> > > On Tue, Jun 19, 2007 at 11:38:02PM -0400, Len Brown wrote:
> > > >
On Saturday 16 June 2007 02:20, Pavel Machek wrote:
> Ok, so mv gets slower for big trees... and open() gets faster for deep
> trees. Previously, open in current directory was one atomic read of
> directory entry, now it has to read directory, and its parent, and its
> parent parent, and its...
>
>
>
>
> endif # V4L_USB_DRIVERS
>
> --
> Cheers,
> Mauro
>
Hi,
I am not sure whether it is related or not
But if you select USB as module but build your v4l_usb driver
into the kernel you also get compile errors.
Attached is a patch which will prevent this by changing the me
_link':
: undefined reference to `mii_link_ok'
drivers/built-in.o: In function `usbnet_nway_reset':
: undefined reference to `mii_nway_restart'
This occurs when an USBNET device is built-in but MII is
selected as module.
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
On Thu, Jun 21, 2007 at 08:36:15PM +0200, Andreas Herrmann wrote:
> On Wed, Jun 20, 2007 at 11:25:48AM -0700, Ravikiran G Thirumalai wrote:
> > On Wed, Jun 20, 2007 at 09:36:30AM -0400, Len Brown wrote:
> > >
> > > The underlying problem is that Kconfig d
On Tue, Jun 19, 2007 at 09:57:44PM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 20 Jun 2007, Andreas Herrmann wrote:
> > Fix kernel build problem:
> >
> > thinkpad_acpi.c:(.text+0x7486a): undefined reference to `ec_write'
> >
> > (as THINKPAD_ACPI d
x27;
Signed-off-by: Andreas Herrmann <[EMAIL PROTECTED]>
diff --git a/fs/dlm/Kconfig b/fs/dlm/Kconfig
index 69a9469..c0e4c59 100644
--- a/fs/dlm/Kconfig
+++ b/fs/dlm/Kconfig
@@ -1,5 +1,5 @@
menu "Distributed Lock Manager"
- depends on EXPERIMENTAL && INET
+
On Fri, Jun 22, 2007 at 03:51:34PM +0200, Jan Engelhardt wrote:
>
> On Jun 22 2007 15:46, Andreas Herrmann wrote:
> >Hi,
> >
> >I am not sure whether it is related or not
> >But if you select USB as module but build your v4l_usb driver
> >into the kernel you
On Fri, Jun 22, 2007 at 12:03:19PM -0300, Mauro Carvalho Chehab wrote:
> Em Sex, 2007-06-22 às 15:51 +0200, Jan Engelhardt escreveu:
> > On Jun 22 2007 15:46, Andreas Herrmann wrote:
> > >Hi,
> > >
> > >I am not sure whether it is related or not
> > >B
Am Sat 23 Jun 2007 11:27:20 PM CEST schrieb Arjan van de Ven
<[EMAIL PROTECTED]>:
On Sat, 2007-06-23 at 13:32 +, Thomas Gleixner wrote:
plain text document attachment
(x86-64-clockevents-irq-balancing.patch)
From: Venki Pallipadi <[EMAIL PROTECTED]>
Disable irq balancing on IRQ0.
this
which are y/n options won't
have any security architecture issues with unloading at all. The mere fact
that SELinux cannot be built as a module is a rather weak argument for
disabling LSM modules as a whole, so please don't.
Thanks,
Andreas
-
To unsubscribe from this list: send the
On Jun 25, 2007 20:33 +0530, Amit K. Arora wrote:
> I have not implemented FA_FL_FREE_ENOSPC and FA_ZERO_SPACE flags yet, as
> *suggested* by Andreas in http://lkml.org/lkml/2007/6/14/323 post.
> If it is decided that these flags are also needed, I will update this
> patch. Than
* default is keep existing data */
so that it doesn't imply this is only for DEALLOC.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAI
anging ctime, if
that is required even though the file is not visibly changing. Maybe the
ctime update should be implicit if the size or mtime are changing?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "
SIZE. I'll let the rest of you duke it out as long as at least one
of them makes it into the kernel.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
to have the *same* fat
multi-line comment duplicated bazillion times.
Thanks a lot!
Andreas Mohr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
can easily be the case on some notebooks AFAIK,
and it was on mine: Inspiron 8000 - bought it as completely dead until I simply
fiddled with CPU socket...).
Andreas Mohr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTEC
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&#x
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
o DOS the kernel with AppArmor.
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
" use is fully independent
from ACPI support (which you disabled), but I think it is, so my reasoning
may be valid.
find /sys -name "*lapic*"
should reveal whether local APIC is currently active or not and thus
whether this might be responsible or not.
Andreas Mohr
-
To unsubscribe from
nk. ALSA stuff was... (c.f. above ;).
> ... No time for analyze other issues.
>
> Thanks for helping,
> I'll take a look to lapic.
Maybe try pci=routeirq or some other useful parameters from
Documentation/kernel-parameters.txt.
And believe me that I'll take a HARD look at lapic
having with
new files using something better than restorecond in the future, perhaps even
an in-kernel mechanism (although I somewhat doubt it). But then again, their
basic model makes sense even without any live file relabeling, and so that's
probably not very high up on the priority list
On Jun 04, 2007 19:03 -0700, Andrew Morton wrote:
> What caused those inodes to be bad, anyway? Memory allocation failures?
This can happen if e.g. NFS has a stale file handle - it will look up
the inode by inum, but ext3_read_inode() will create a bad inode due to
i_nlink = 0.
Cheers, Andr
range. It does not know anything about types.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different.&quo
t; 'nopadding' instead of 'packed', then there's no need to emit code to
> handle unaligned loads.
You can add aligned(N) to increase the alignment again.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg,
he network driver module needs?
Background:
I'm suspecting the cassini driver to be the problem (memory leak?),
because I didn't have this problem without the cassini driver while using
another nic and driver.
Kind regards,
Andreas Hartmann
-
To unsubscribe from this list: send the l
It isn't listed in the e2fsprogs repo.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://v
cation for whatever reason (interrupt, out of
space, etc) like a regular write(2) call. In this case the return type needs
to also be an loff_t to match @len.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "u
your kernel has CONFIG_LBD enabled.
The kernel doesn't check if the block layer can actually write to
a block device > 2TB.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kern
Sam Ravnborg <[EMAIL PROTECTED]> writes:
> + * The follwoing markers are used for the cases where the reference to
s/follwoing/following/
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint =
e NBSP. But __only__ in ISO-8859. It is an invalid
> UTF-8 sequence (which is why you may not even "see" the nbsp :-)
Actually, in a utf-8 environment you see it much better.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürn
Jan Engelhardt <[EMAIL PROTECTED]> writes:
> On May 20 2007 11:14, Andreas Schwab wrote:
>>Jan Engelhardt <[EMAIL PROTECTED]> writes:
>>> On May 19 2007 22:24, Willy Tarreau wrote:
>>>>On Sat, May 19, 2007 at 09:50:43PM +0200, oliver pinter wrote:
>>
t; loop* nodes in /lib/udev/devices/, which will be
>> copied to /dev/ early on every bootup.
>>
>
> Won't these be removed after "losetup -d"?
No, only when you unload the loop module (and then only those that were
ever used).
Andreas.
--
Andreas Schwab, SuSE Labs,
e people who replied and sent some suggestions!
Due to the "scathing" (well, thorough ;) code review I'll send a patch
with those cleanups against 2.6.21-mm1 very soon.
(I was actually a bit surprised to see akpm commit this thing after this
review mail, but it's ok since it l
ral repository for this configuration item? A hard-
> coded value of 256 somewhere inside the kernel smells like a bug.
There is PATH_MAX and there is NAME_MAX, and only the latter (which is
260 for vfat) matters here.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products Gm
crement found during probing)"?
(with an optional "please report" part)
Andreas Mohr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
the right solution is for this. If you know you will
be resizing the fs you could increase the initial journal size at mke2fs
time (-J size=16). Alternately, it is possible resize to an intermediate
size and then delete and recreate the journal via tune2fs (which would
be the larger size by defa
then truncate_mutex is not needed.
> > + ret = ext4_ext_get_blocks(handle, inode, block,
> > + max_blocks, &map_bh,
> > + EXT4_CREATE_UNINITIALIZED_EXT, 0);
> > + BUG_ON(!ret);
>
with the journal that is probably also a good
and easy place to start (e.g. may be as easy as just giving a goal
block of s_blocks_count / 2 to the journal create code).
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: sen
do manual zero-filling of the file in userspace.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On May 07, 2007 19:02 -0400, Jeff Garzik wrote:
> Andreas Dilger wrote:
> >Actually, this is a non-issue. The reason that it is handled for
> >extent-only is that this is the only way to allocate space in the
> >filesystem without doing the explicit zeroing.
>
> P
.g. indirect blocks).
One of the design goals for sys_fallocate() was to allow FA_DELALLOC
to deallocate unwritten extents in a safe manner.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line "unsubscribe linu
n old kernel
is relatively harmless if the old kernel doesn't know what they are.
It's like having a key to a door that you don't know where it is.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send th
l allocation/
>unallocation ?
I would say yes. If glibc does the fallback fallocate via write() the
mtime/ctime will be updated, so it makes sense to be consistent for
both methods. Also, it just makes sense from the "this file was modified"
point of view.
Cheers, Andreas
--
Andr
o add a #include or so? ;)
(worked for me when adding to include/linux/power_supply.h)
Ugh, such a pain following ever-outdated and always-broken -mm versions ;)
Andreas Mohr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message t
On Thu, May 10, 2007 at 01:27:42AM +0400, Anton Vorontsov wrote:
> On Wed, May 09, 2007 at 11:08:20PM +0200, Andreas Mohr wrote:
> > Care to add a #include or so? ;)
> > (worked for me when adding to include/linux/power_supply.h)
> >
> > Ugh, such a pain following ever
Hi,
On Sat, May 05, 2007 at 07:56:05PM +0200, Andreas Mohr wrote:
> Due to the "scathing" (well, thorough ;) code review I'll send a patch
> with those cleanups against 2.6.21-mm1 very soon.
working 3D/DRI intel-agp.ko resume for i815 chip cleanup patch:
- revert register
On May 08, 2007 16:49 -0500, Serge E. Hallyn wrote:
> Quoting Andreas Dilger ([EMAIL PROTECTED]):
> > One of the important use cases I can see today is the ability to
> > split the heavily-overloaded e.g. CAP_SYS_ADMIN into much more fine
> > grained attributes.
>
>
On Monday 16 April 2007 18:21, Christoph Hellwig wrote:
> On Mon, Apr 16, 2007 at 06:11:30PM +0200, Andreas Gruenbacher wrote:
> > On Thursday 12 April 2007 12:06, Christoph Hellwig wrote:
> > > Once again very strong NACK. Every conditional passing of vfsmounts get
> >
ely case that
someone uses insanely long pathnames, this limit can be increased.
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please rea
even if the same files are mounted at several locations, parent
directory permissions may allow accessing only some of those locations.
Thanks,
Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
007-04-30
> 10:48:14.0 +0100
> +++ linux-2.6.22-rc1-mm1/include/asm-arm/termbits.h 2007-05-23
> 20:23:25.0 +0100
> @@ -15,6 +15,17 @@
> cc_t c_cc[NCCS];/* control characters */
> };
>
> +struct termios_2 {
s/_//
Andreas.
--
A
On Thursday 24 May 2007 03:28, James Morris wrote:
> On Wed, 23 May 2007, Andreas Gruenbacher wrote:
> > This is backwards from what AppArmor does. The policy defines which paths
> > may be accessed; all paths not explicitly listed are denied. If files are
> > mounted at mul
On Thursday 24 May 2007 15:19, James Morris wrote:
> On Thu, 24 May 2007, Andreas Gruenbacher wrote:
> > > Would you mind providing some concrete examples of how such a model
> > > would be useful?
> >
> > The model is explained, with examples, in the te
what the mapping turns out to be - the goal is to place
inodes with a similar hash into nearby inodes, and this heuristic works
relatively well for that. Once the given leaf block's inode range is full
then new inodes can be allocated from a new window as it was done for the
newly-created d
On Thursday 24 May 2007 20:40, Al Viro wrote:
> On Thu, May 24, 2007 at 08:10:00PM +0200, Andreas Gruenbacher wrote:
>
> > Read it like this: we don't have a good idea how to support multiple
> > namespaces so far. Currently, we interpret all pathnames relative to the
>
there is one.
Different policy for different names of the same binary makes more obvious
sense with chroot environments. That's slightly different from having
different permissions for the same file within a single profile though.
Thanks,
Andreas
-
To unsubscribe from this list: send the lin
a strange idea. AppArmor cannot assume anything about argv[0],
and it would be a really bad idea to change the well-established semantics of
argv[0].
There is no actual need for looking at argv[0], though: AppArmor decides based
on the actual pathname of the executable...
Thanks,
Andreas
-
To unsubsc
mit block itself.
We've got a pretty-much complete version of the ext3 journal checksumming
patch that avoids the need to do the pre-commit barrier, since the checksum
can verify at recovery time whether all of the transaction's blocks made
it to disk or not (which is what the commit b
y could be as well be separate copies, and different policy can be defined
for each one of them. (This is ignoring the fact that for small utilities
like gzip, profile inheritance is usually more useful than defining separate
profiles.)
Thanks,
Andreas
-
To unsubscribe from this li
ng to do with it.
It would be nice if you could stop calling argv[0] checks ``name-based access
control'': from the point of view of the kernel no access control is
involved, and even application-level argv[0] based access control makes no
sense whatsoever.
Thanks,
Andreas
-
To unsubs
On Saturday 26 May 2007 14:09, Tetsuo Handa wrote:
> Hello.
>
> Andreas Gruenbacher wrote:
> > > exec { "/usr/bin/gunzip" } "gzip", "-9", "some/file/to.gz";
> >
> > The above Perl code executes /usr/bin/gunzip and sets argv[0]
1 - 100 of 3652 matches
Mail list logo
