Hello,
Bartlomiej Zolnierkiewicz wrote:
* (partially) fix DMA in RAID mode
Code intended to check DMA status was checking DMA command register.
Moreover firmware seems to forget to set DMA capable bit for the
slave device (at least in RAID mode but without ITE RAID volumes) so
Tejun Heo wrote:
Tejun Heo wrote:
Greg KH wrote:
On Mon, May 21, 2007 at 10:31:01AM +0530, Maneesh Soni wrote:
On Thu, May 17, 2007 at 08:16:10PM +0200, Tejun Heo wrote:
Allowing attribute and symlink dentries to be reclaimed means
sd-s_dentry can change dynamically. However, updates to the
On Fri, 2007-06-08 at 23:18 +0100, Jack Stone wrote:
This patch series replaces DPRINTK with pr_debug in alternative.c,
autofs, autofs4
and ncpfs. A new function called pr_err is also added to keep
functionality in
ncpfs. The last 2 patches add support for pr_debug_pid and apply it to
On Fri, Jun 08, 2007 at 03:46:30PM -0700, Auke Kok wrote:
Currently there are 97 occurrences where drivers need the pci
revision ID. We can do this once for all devices. Even the pci
subsystem needs the revision several times for quirks. The extra
u8 member pads out nicely in the pci_dev
But; if the Linux kernel should Dual-Licensed (GPL V2 and GPL V3), it
will allow us the both worlds' fruits like code exchanging from other
Open Source Projects (OpenSolaris etc.) that is compatible with GPL V3
and not with GPL V2 and of course the opposite is applicable,too.
That is a
On Sat, 9 Jun 2007, Sean wrote:
so are you suggesting that SELinux would call out to userspace for every
file open to get the label for that file?
No, i'm not. You must already have a kernel function in the current
implementation of AA that decides the proper policy for each path. Why
not
On 6/8/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Fri, 08 Jun 2007 23:43:46 +0530
Balbir Singh [EMAIL PROTECTED] wrote:
This patch implements per container statistics infrastructure and re-uses
code from the taskstats interface.
boggle.
Symbol: CONTAINERS [=y]
Selected by:
On Sat, 2007-06-09 15:57:55 +1000, Neil Brown [EMAIL PROTECTED] wrote:
On Saturday June 9, [EMAIL PROTECTED] wrote:
As we know the forthcoming GPL V3 will be not compatible with the GPL V2
and Linux Kernel is GPL V2 only.
So, another point is, which is previously mentioned by Linus and
On Sat, 9 Jun 2007, Sean wrote:
On Fri, 8 Jun 2007 22:18:40 -0700 (PDT)
[EMAIL PROTECTED] wrote:
the way I would describe the difference betwen AA and SELinux is:
SELinux is like a default allow IPS system, you have to describe
EVERYTHING to the system so that it knows what to allow and what
On Sat, 9 Jun 2007 00:04:15 -0700 (PDT)
[EMAIL PROTECTED] wrote:
if it was this easy just have SELinux set the label == path
you first need to figure out what the path is. right now this can't be
done, the AA paches provide this capability.
The question is: why not just extend SELinux to
On Jun 8 2007 17:42, Benjamin Gilbert wrote:
@@ -0,0 +1,299 @@
+/*
+ * x86-optimized SHA1 hash algorithm (i486 and above)
+ *
+ * Originally from Nettle
+ * Ported from M4 to cpp by Benjamin Gilbert [EMAIL PROTECTED]
+ *
+ * Copyright (C) 2004, Niels M?ller
+ * Copyright (C) 2006-2007 Carnegie
On Sat, 9 Jun 2007 00:13:22 -0700 (PDT)
[EMAIL PROTECTED] wrote:
did you read my explination of the analogy?
It was a rather poor analogy i'm afraid. But the point i make still stands.
So far you've failed to show any reason SELinux can't be reasonably extended
to handle all the features you
On Jun 8 2007 13:36, Greg KH wrote:
Any comments or critique of this is greatly appreciated.
Rules to access device-information in the Linux kernel sysfs
The kernel exported sysfs exports internal kernel implementation-details
and depends on internal
On Jun 9 2007 00:10, Sam Ravnborg wrote:
Hi Matthieu.
Can you please try to tell what your patch actually does.
As for the part added in the MAkefile you pass -lintl for Cygwin -
but I fail to see _why_ -lintl is needed.
It is because I think .DLLs do not have something like ELF's DT_NEEDED,
On Jun 8 2007 22:19, Sam Ravnborg wrote:
On Fri, Jun 08, 2007 at 09:08:36AM -0400, Rich Chase wrote:
An Apparent bug:
version 2.6.21.3
missing the file ./scripts/mod/elfconfig.h
To build an external module you need to point to a directory
where a fully build kernel is placed.
You could do a
Jörn Engel wrote:
Whenever writes/erases to the device happen, the device driver would
need to call a function like
/**
* unmap_page_range - remove all mapping to the given range of an address space
* @mapping - the address space in question
* @start_index - index of the first page in the
On Jun 8 2007 08:40, Robert P. J. Day wrote:
If you disable CONFIG_DEBUG_KERNEL, things should go back to normal
sizes for you.
grow so much compared to *which other modules*? the ones that came
with your distro? if that's the case, try installing your new modules
with
# make
Ian Kent wrote:
On Fri, 2007-06-08 at 23:18 +0100, Jack Stone wrote:
This patch series replaces DPRINTK with pr_debug in alternative.c,
autofs, autofs4
and ncpfs. A new function called pr_err is also added to keep
functionality in
ncpfs. The last 2 patches add support for pr_debug_pid and
On Sat, 9 Jun 2007, Jan Engelhardt wrote:
On Jun 8 2007 22:19, Sam Ravnborg wrote:
On Fri, Jun 08, 2007 at 09:08:36AM -0400, Rich Chase wrote:
An Apparent bug:
version 2.6.21.3
missing the file ./scripts/mod/elfconfig.h
To build an external module you need to point to a directory
On Sat, 9 Jun 2007, Jan Engelhardt wrote:
On Jun 8 2007 22:19, Sam Ravnborg wrote:
On Fri, Jun 08, 2007 at 09:08:36AM -0400, Rich Chase wrote:
An Apparent bug:
version 2.6.21.3
missing the file ./scripts/mod/elfconfig.h
To build an external module you need to point to a directory
Jack Stone wrote:
This patch series replaces DPRINTK with pr_debug in alternative.c,
autofs, autofs4
and ncpfs. A new function called pr_err is also added to keep
functionality in
ncpfs. The last 2 patches add support for pr_debug_pid and apply it to
autofs4 to
keep the output the same as
On Sat, 9 Jun 2007 00:09:55 -0700 Paul Menage [EMAIL PROTECTED] wrote:
On 6/8/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Fri, 08 Jun 2007 23:43:46 +0530
Balbir Singh [EMAIL PROTECTED] wrote:
This patch implements per container statistics infrastructure and re-uses
code from the
From: Grant Grundler [EMAIL PROTECTED]
Date: Sat, 9 Jun 2007 00:59:53 -0600
On Fri, Jun 08, 2007 at 03:46:30PM -0700, Auke Kok wrote:
Currently there are 97 occurrences where drivers need the pci
revision ID. We can do this once for all devices. Even the pci
subsystem needs the revision
Badari Pulavarty [EMAIL PROTECTED] writes:
No. You still need my patch to fix the current breakage.
Agreed.
This patch makes hugetlbfs also use same naming convention as regular shmem
for
its
name. This is not absolutely needed, its a nice to have. Currently, user space
tools
can't
On Sat, 9 Jun 2007, Sean wrote:
On Sat, 9 Jun 2007 00:04:15 -0700 (PDT)
[EMAIL PROTECTED] wrote:
if it was this easy just have SELinux set the label == path
you first need to figure out what the path is. right now this can't be
done, the AA paches provide this capability.
The question is:
This patch adds a new macro to print to KERN_ERR initially for ncp but
others may want to use it
Signed-off-by: Jack Stone [EMAIL PROTECTED]
---
Index: linux/include/linux/kernel.h
===
--- linux.orig/include/linux/kernel.h
+++
On Sat, 9 Jun 2007, Sean wrote:
remember that the security hooks in the kernel are not SELinux API's, they
are the Loadable Security Model API. What the AA people are asking for is
for the LSM API to be modified enough to let their code run (after that
(and working in parallel) they will work on
On 6/9/07, Andrew Morton [EMAIL PROTECTED] wrote:
- CONTAINER_DEBUG should depend on CONTAINERS
CONTAINER_DEBUG is actually a container subsystem whose sole purpose
is to provide debugging information about any hierarchy that it's
mounted as a part of. So in some senses it's in the same boat
This patch converts all DPRINTKs in alternative.c to pr_debug
Signed-off-by: Jack Stone [EMAIL PROTECTED]
---
--- linux/arch/i386/kernel/alternative.c2007-06-07 17:25:46.0
+0100
+++ linux/arch/i386/kernel/alternative.c2007-06-07 20:45:52.0
+0100
@@ -1,3 +1,4 @@
Justin Treon wrote:
--- Carsten Otte [EMAIL PROTECTED] wrote:
The nice thing about this approach is: we use page-count and rmap,
both already exist and are perfectly suited for our purpose.
The downside: We need mem_map[] struct page entries behind all memory
segments. Nowerdays we can easily
This patch replaces DPRINTKs in autofs
Signed-off-by: Jack Stone [EMAIL PROTECTED]
---
Index: linux/fs/autofs/autofs_i.h
===
--- linux.orig/fs/autofs/autofs_i.h
+++ linux/fs/autofs/autofs_i.h
@@ -31,12 +31,6 @@
#include
On Sat, 9 Jun 2007 01:06:09 -0700 (PDT)
[EMAIL PROTECTED] wrote:
but the SELinux API's are not the core security API's in Linux, the LSM
API's are. and AA is useing the LSM API's (extending them where they and
SELinux don't do what's needed)
Calling LSM core and pretending that SELinux
This patch updates the DPRINTK macro in autofs4 to use pr_debug as the
macro uses a special print format.
Signed-off-by Jack Stone [EMAIL PROTECTED]
---
Index: linux/fs/autofs4/autofs_i.h
===
--- linux.orig/fs/autofs4/autofs_i.h
+++
This patch replaces DPRINTKs in ncpfs with a combination of pr_debug and
pr_err as appropriate.
Signed-off-by: Jack Stone [EMAIL PROTECTED]
---
Index: linux/fs/ncpfs/dir.c
===
--- linux.orig/fs/ncpfs/dir.c
+++ linux/fs/ncpfs/dir.c
@@
On Sat, 9 Jun 2007 01:07:53 -0700 Paul Menage [EMAIL PROTECTED] wrote:
On 6/9/07, Andrew Morton [EMAIL PROTECTED] wrote:
- CONTAINER_DEBUG should depend on CONTAINERS
CONTAINER_DEBUG is actually a container subsystem whose sole purpose
is to provide debugging information about any
This patch adds a new function to kernel.h. This function prints out the
pid of the current process and the name of the function where it was
called from followed by the debug message and a newline.
This function mimics the output of autofs4.
Signed-off-by: Jack Stone [EMAIL PROTECTED]
---
On 6/9/07, Andrew Morton [EMAIL PROTECTED] wrote:
Would it not be simplest to have CONTAINERS as the top-level
user-configurable item and to then have everything else depend on it?
Yes, OK - it can go that way around too. I guess my thought was that
people would be more interested in
This patch uses the new pr_debug_pid function to replace DPRINKs in
autofs4 without breaking the functionality.
Signed-off-by: Jack Stone [EMAIL PROTECTED]
---
Index: linux/fs/autofs4/autofs_i.h
===
---
Hi,
I'm having some trouble with the 2.6.21 -rt series on my single
processor machine:
APIC error on CPU0: 01(01)
[a010ce5b] smp_error_interrupt+0x5b/0x70
[a01034f8] error_interrupt+0x28/0x30
[a024ca38] iowrite16+0x28/0x30
[a02c7ecf] rhine_interrupt+0x6f/0xb20
[a039d553]
Bartlomiej Zolnierkiewicz wrote:
Hi,
On Friday 08 June 2007, Jeff Garzik wrote:
On Fri, Jun 08, 2007 at 02:18:55PM +0200, Bartlomiej Zolnierkiewicz wrote:
On Monday 04 June 2007, Jiri Slaby wrote:
ide-generic, add another device exception
ide-generic is a generic ISA IDE driver, this one is
Hi all,
please take care about following bug commited at bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=8603
Thanks a lot!
Michal
-
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 Sat, 9 Jun 2007 01:03:15 -0700 (PDT)
[EMAIL PROTECTED] wrote:
becouse the SELinux people don't want to have this in their code for one
thing.
Tuff nuggies to the SELinux people.. Show them code good enough they'd be
embarrassed to reject.
you seem to be ignoring the SELinux people who
On Sat, Jun 09, 2007 at 09:53:22AM +0200, Jan Engelhardt wrote:
On Jun 8 2007 22:19, Sam Ravnborg wrote:
On Fri, Jun 08, 2007 at 09:08:36AM -0400, Rich Chase wrote:
An Apparent bug:
version 2.6.21.3
missing the file ./scripts/mod/elfconfig.h
To build an external module you need to
On Sat, Jun 09, 2007 at 03:57:30AM -0400, Robert P. J. Day wrote:
On Sat, 9 Jun 2007, Jan Engelhardt wrote:
On Jun 8 2007 22:19, Sam Ravnborg wrote:
On Fri, Jun 08, 2007 at 09:08:36AM -0400, Rich Chase wrote:
An Apparent bug:
version 2.6.21.3
missing the file
EVIOCGRAB is nice and very useful, however over time I've gotten
multiple requests to make it possible for applications to get events
straight from the event device while xf86-input-evdev is getting events
from the same device.
Here is the least invasive patch I could think of, it changes the
CIJOML napsal(a):
Hi all,
please take care about following bug commited at bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=8603
Thanks a lot!
Does this happen without atheros drivers? Do you use hal or openhal?
thanks,
--
http://www.fi.muni.cz/~xslaby/Jiri Slaby
Jiri Slaby napsal(a):
CIJOML napsal(a):
Hi all,
please take care about following bug commited at bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=8603
Thanks a lot!
Does this happen without atheros drivers? Do you use hal or openhal?
HAL, ok, try to reproduce with untainted kernel.
On Fri, 2007-06-08 at 16:46 -0700, Greg KH wrote:
On Sat, Jun 09, 2007 at 12:02:28AM +0100, Richard Purdie wrote:
On Fri, 2007-06-08 at 11:57 -0700, Greg KH wrote:
On Fri, Jun 01, 2007 at 05:23:24PM +0100, Richard Purdie wrote:
Why not just do a simple:
led01
led02
led03
from kernel/module.c:
...
ks = lookup_symbol(name, __start___ksymtab_gpl_future,
__stop___ksymtab_gpl_future);
if (ks) {
if (!gplok) {
printk(KERN_WARNING Symbol %s is being used
Celso wrote:
Hello, I'm using -ck since... along time ago (I start using it with the
kernel 2.6.16) . I started using it with Ubuntu and the response of the
system was better. Since that I always compile my kernels with -ck.
Actually I use 2.6.20-ck1 and I have no problems, even with things
Good day!
Sorry for intruding, but I'm seeing the same problem on my U10 with
2.6.22-rc3 and Xorg-7.1+gentoo patches.
On Wed, Jun 06, 2007 at 04:22:10PM -0700, David Miller wrote:
From: David Miller [EMAIL PROTECTED]
Date: Wed, 30 May 2007 13:01:40 -0700 (PDT)
From: Mikael Pettersson
Now there is a anon dirty limit since a few releases, but I'm not
fully convinced it solves the problem completely.
A gut feeling or is there more?
Lots of other subsystem can allocate a lot of memory
and they usually don't cooperate and have similar dirty limit concepts.
So you could run
Bartlomiej Zolnierkiewicz wrote:
Sergei, do we need to disallow UDMA6 completely on HPT734 or
is it only an issue with some problematic devices (= blacklist)?
Note that I didn't change what the old code was doing in this regard --
although the HPT374 spec does *not* say that UDMA6 is
On Fri, 8 Jun 2007 16:48:45 +0200 (CEST), Geert Uytterhoeven wrote:
On Fri, 8 Jun 2007, Jean Delvare wrote:
OK. Geert, care to submit a new patch removing struct i2c_device_id
altogether?
Sorry, probably not...
I just thought I found a grave bug while looking into adding zorro
support
On Sat, 09 Jun 2007 11:30:04 +1000
Herbert Xu [EMAIL PROTECTED] wrote:
Please cc networking patches to [EMAIL PROTECTED]
Jeff Layton [EMAIL PROTECTED] wrote:
The following patch is a first stab at removing this need. It makes it
so that in tcp_recvmsg() we also check
Hi,
After switching an older machine over from the PDC20265 PATA driver to the
libata driver pata_pdc202xx_old my HDDs are now limited to UDMA/33. With the
old driver they were happily running with UDMA/100.
I'm including the relevant kernel output for both cases below.
Cheers,
- Udo
Sean wrote:
All of a sudden you've implemented the main features of AA with very
few changes to the kernel. It should be more maintainable, and much
easier to get accepted into the kernel.
Do you agree with passing struct vfsmount to VFS helper functions and LSM
hooks
and introducing
Getting the following error :
drivers/char/mwave/3780i.c: In function 'dsp3780I_EnableDSP':
drivers/char/mwave/3780i.c:323: error: cannot take address of
bit-field 'LoadValue'
drivers/char/mwave/3780i.c:323: error: cannot take address of
bit-field 'LoadValue'
drivers/char/mwave/3780i.c:323:
On Sat, 9 Jun 2007 20:26:57 +0900
Tetsuo Handa [EMAIL PROTECTED] wrote:
Sean wrote:
All of a sudden you've implemented the main features of AA with very
few changes to the kernel. It should be more maintainable, and much
easier to get accepted into the kernel.
Do you agree with passing
Linus,
Please pull from:
ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git
master
For the following:
- Fixes the V4L ABI breakage as reported on http://lkml.org/lkml/2007/5/14/42
(required several changes on ivtv code);
- A building fix for
Hi Michal,
Subject: V4L ABI breakage
References : http://lkml.org/lkml/2007/5/14/42
Submitter : Robert Fitzsimons [EMAIL PROTECTED]
Caused-By : Hans Verkuil [EMAIL PROTECTED]
Mauro Carvalho Chehab [EMAIL PROTECTED]
commit
Remove an unnecessary C style preprocessor directive from ARM SHA-1
assember implementation. It confuses sloccount.
Signed-off-by: Heikki Orsila [EMAIL PROTECTED]
diff --git a/arch/arm/lib/sha1.S b/arch/arm/lib/sha1.S
index ff6ece4..67c2bf4 100644
--- a/arch/arm/lib/sha1.S
+++
On Sat, 2007-06-09 at 09:55 +0200, Jan Engelhardt wrote:
On Jun 8 2007 08:40, Robert P. J. Day wrote:
If you disable CONFIG_DEBUG_KERNEL, things should go back to normal
sizes for you.
grow so much compared to *which other modules*? the ones that came
with your distro? if that's the
Greg KH wrote:
- Do not use libsysfs
It makes assumptions about sysfs which are not true. Its API does not
offer any abstraction, it exposes all the kernel driver-core
implementation details in its own API. Therefore it is not better than
reading directories and opening the files
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
Starting beeper as soon as ACPI sleep returns is very useful in
debugging apparently dead machines. If it beeps at all, it makes
sense to start playing with CMOS tracer.
Signed-off-by: Pavel Machek [EMAIL PROTECTED]
diff --git a/arch/i386/kernel/acpi/wakeup.S b/arch/i386/kernel/acpi/wakeup.S
On Sat, 2007-06-09 15:08:17 +0200, Pavel Machek [EMAIL PROTECTED] wrote:
Starting beeper as soon as ACPI sleep returns is very useful in
debugging apparently dead machines. If it beeps at all, it makes
sense to start playing with CMOS tracer.
I'd even go so far and implement it
Hi,
As I understand it, an IDE hard drive can be reset in three ways. A
power-on reset, a hard reset caused by pin 1 (RESET-) on the IDE
connector, and a soft reset (bit SRST in the device control register).
RESET- is held low on a power on, but can also be used later to do a
hard reset.
I can
On Sat, 9 June 2007 09:55:15 +0200, Carsten Otte wrote:
Jörn Engel wrote:
Either that or using standard mtd-read() and mtd-write() calls. I see
some advantages to mtd-write() in particular, as the device driver
needs some notification to trigger unmap_page_range() before the actual
write
[Jan Kara - Thu, Jun 07, 2007 at 04:41:21PM +0200]
| On Thu 07-06-07 17:54:58, Cyrill Gorcunov wrote:
| [Jan Kara - Thu, Jun 07, 2007 at 11:36:07AM +0200]
| | Hi Cyrill!
| |
| | On Wed 06-06-07 21:53:51, Cyrill Gorcunov wrote:
| | This patch prevents from deadlock on inode being dropped.
On Saturday 09 June 2007 15:10:31 Ralph Corderoy wrote:
Hi,
As I understand it, an IDE hard drive can be reset in three ways. A
power-on reset, a hard reset caused by pin 1 (RESET-) on the IDE
connector, and a soft reset (bit SRST in the device control register).
RESET- is held low on a
On Sat, 9 Jun 2007, Sean wrote:
On Sat, 9 Jun 2007 20:26:57 +0900
Tetsuo Handa [EMAIL PROTECTED] wrote:
Sean wrote:
All of a sudden you've implemented the main features of AA with very
few changes to the kernel. It should be more maintainable, and much
easier to get accepted into the
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 Jun 9 2007 08:08, Jon Masters wrote:
So I missed half of this conversation - you're saying that on a
CONFIG_DEBUG_KERNEL, you have such large .ko module files that depmod
segfaults? Can I get a core dump or any further information? :-)
Just make sure your /lib/modules/kernel is like 300
Joel Schopp wrote:
Dan Williams wrote:
checkpatch currently complains about macros like the following:
#define for_each_dma_cap_mask(cap, mask) \
for ((cap) = first_dma_cap(mask); \
(cap) DMA_TX_TYPE_END;\
(cap) = next_dma_cap((cap), (mask)))
On Jun 09, 2007, at 01:41:42, Paul Mackerras wrote:
Davide Libenzi writes:
The only reason we use a floating base, is because Uli preferred
to have non-exactly predictable fd allocations. There no reason of
re-doing the same POSIX mistake all over again:
Why must everything that makes
Hi!
Some may infer otherwise from your document.
Not only that, the implication that secrecy is only useful to
intelligence agencies is pretty funny.
That was not the claim. Rather, that intelligence agencies have a very
strong need for privacy, and will go to greater lengths to
On Fri, 08 Jun 2007 10:14:03 +0200, Gerard H. Pille wrote:
[1.] One line summary of the problem:
Since I switched from 2.6.20 to 2.6.21 on my Athlon AMD64 laptop, the system
time is slow - about 1' on 15'.
According to your system description it seems that you have a
Targa Visionary laptop
hi all
i am bit confused with the function defination of inet_listen.
How a listen socket can listen and return to application at a time.
since a server stops at accpet not at listen then how listening port start.
I was thinking that the listen call thread out at the tcp_v4_hash
function time
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.
Woah, that describes the userspace
On Fri, 2007-06-08 at 19:06 -0700, David Miller wrote:
From: Trond Myklebust [EMAIL PROTECTED]
Date: Fri, 08 Jun 2007 17:43:27 -0400
It is not dhcp. I'm seeing the same bug with bog-standard ifup with a
static address on an FC-6 machine.
It appears to be something in the latest dump
On Fri, Jun 08, 2007 at 07:10:03PM -0700, Ulrich Drepper wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Al Viro wrote:
Any real-world examples of exploitable holes based on that?
Return to libc exploit, calling dup2, where some privileged data is
redirected from the normal file
On Saturday 09 June 2007 10:10, Sean wrote:
Clinging to the current AA implementation instead of honestly considering
reasonable alternatives does not inspire confidence or teamwork.
What you imply is pretty insulting. I can assure you we looked into many
possible implementation choices, and
[EMAIL PROTECTED] wrote:
On Sat, 9 Jun 2007, Sean wrote:
snip
what SELinux cannot do is figure out what label to assign a new file.
Nit: SELinux figures out what to label new files fine, just not based on
the name. This works in most cases, eg., when user_t creates a file in
/tmp it
Hi, Stefan,
I have worked out a new patch with single-threaded unit supported in
multithreaded device probing. A new flag as follow is added to struct
device,
unsigned singlethreaded_probe:1;
Which indicate that the device node and all its children node must be
probed single-threaded. During
device_bind_driver() error code returning has been fixed.
release() function has been written, so that to free resources
in correct way; the release path is now clean.
Before the rework, it used to cause
Device '[EMAIL PROTECTED]:1' does not have a release() function, it is broken
and must be
On Sat, 2007-06-09 at 15:59 +0200, Jan Engelhardt wrote:
On Jun 9 2007 08:08, Jon Masters wrote:
So I missed half of this conversation - you're saying that on a
CONFIG_DEBUG_KERNEL, you have such large .ko module files that depmod
segfaults? Can I get a core dump or any further information?
On Jun 09, 2007, at 01:18:40, [EMAIL PROTECTED] wrote:
SELinux is like a default allow IPS system, you have to describe
EVERYTHING to the system so that it knows what to allow and what to
stop.
WRONG. You clearly don't understand SELinux at all. Try booting in
enforcing mode with an
Hi Andrew:
I am maintaining a git tree for the hwmon subsystem now. You may pull from
it here:
git://lm-sensors.org/kernel/mhoffman/hwmon-2.6.git testing
The current contents include the remainder of Jean Delvare's quilt patch
series, plus a single patch to MAINTAINERS. Once you start
device_bind_driver() error code returning has been fixed.
release() function has been written, so that to free resources
in correct way; the release path is now clean.
Before the rework, it used to cause
Device '[EMAIL PROTECTED]:1' does not have a release() function, it is broken
and must be
On Sat, Jun 09, 2007 at 05:25:08AM -0400, Robert P. J. Day wrote:
from kernel/module.c:
...
ks = lookup_symbol(name, __start___ksymtab_gpl_future,
__stop___ksymtab_gpl_future);
if (ks) {
if (!gplok) {
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Al Viro wrote:
So which code is supposed to do that open/write in your example? Library?
Unmodified application? Application specifically modified to make *that*
open() randomized?
Why should that matter? All of the above. Any piece of code
Huang, Ying wrote:
Can this mechanism solve the demand of IEEE1394 subsystem effectively?
Probably. I don't know when I will have time to try it.
(BTW, we should actually be able to probe subunits in parallel, however
I suspect that some firmwares will not tolerate this.)
...
+/**
+ *
On Sat, 9 Jun 2007 17:17:57 +0200
Andreas Gruenbacher [EMAIL PROTECTED] wrote:
On Saturday 09 June 2007 10:10, Sean wrote:
Clinging to the current AA implementation instead of honestly considering
reasonable alternatives does not inspire confidence or teamwork.
What you imply is pretty
On Sat, 9 Jun 2007 12:00:31 -0400 Mark M. Hoffman [EMAIL PROTECTED] wrote:
Hi Andrew:
I am maintaining a git tree for the hwmon subsystem now. You may pull from
it here:
git://lm-sensors.org/kernel/mhoffman/hwmon-2.6.git testing
The current contents include the remainder of Jean
On Sat, 9 Jun 2007, Kyle Moffett wrote:
On Jun 09, 2007, at 01:18:40, [EMAIL PROTECTED] wrote:
SELinux is like a default allow IPS system, you have to describe EVERYTHING
to the system so that it knows what to allow and what to stop.
WRONG. You clearly don't understand SELinux at all. Try
On 6/9/07, Mikael Pettersson [EMAIL PROTECTED] wrote:
According to your system description it seems that you have a
Targa Visionary laptop with a VIA chipset and a Mobile Athlon64.
If so, then you probably have the same problem I reported some time
ago: see
On Sat, Jun 09, 2007 at 09:26:34AM -0700, Ulrich Drepper wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Al Viro wrote:
So which code is supposed to do that open/write in your example? Library?
Unmodified application? Application specifically modified to make *that*
open()
On Sat, 9 Jun 2007, Paul Mackerras wrote:
Davide Libenzi writes:
The only reason we use a floating base, is because Uli preferred to have
non-exactly predictable fd allocations. There no reason of re-doing the
same POSIX mistake all over again:
Why must everything that makes things
On Sat, 9 Jun 2007, Al Viro wrote:
That's simply not true. On the current kernel nothing stops you from e.g.
picking a random number and using F_DUPFD. Voila - there's your randomized
descriptor. Portable to earlier kernels.
Moreover, nonsense^H^H^Hq_fd() can be implemented in userland
1 - 100 of 430 matches
Mail list logo
