Re: Temporary lockup on loopback block device

> > > Arguably we just have the wrong backing-device here, and what we should do > > > is to propagate the real backing device's pointer through up into the > > > filesystem. There's machinery for this which things like DM stacks use. > > > > > > I wonder if the post-2.6.23 changes happened to

Re: [RFC: 2.6 patch] add -fno-tree-scev-cprop to KBUILD_CFLAGS

On Sun, Nov 11, 2007 at 07:48:29AM +0100, Adrian Bunk wrote: > But the kernel does (at least on some architectures) not link with > libgcc or ship other code providing the required libgcc functions. > > Richard Guenther suggested in gcc bug #32044 to use -fno-tree-scev-cprop > (new option in

Re: AppArmor Security Goal

Dr. David Alan Gilbert wrote: > > > Allowing a user to tweak (under constraints) their settings might allow > them to do something like create two mozilla profiles which are isolated > from each other, so that the profile they use for general web surfing > is isolated from the one they use for

[2.6 patch] net/ipv4/ipvs/: remove unused exports

This patch removes the following unused EXPORT_SYMBOL's: - ip_vs_try_bind_dest - ip_vs_find_dest Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- net/ipv4/ipvs/ip_vs_conn.c |1 - net/ipv4/ipvs/ip_vs_ctl.c |1 - 2 files changed, 2 deletions(-)

[RFC: 2.6 patch] add -fno-tree-scev-cprop to KBUILD_CFLAGS

The gcc from svn that will become gcc 4.3 generates libgcc calls in cases like the following (on 32bit architectures): <-- snip --> static inline void timespec_add_ns(struct timespec *a, u64 ns) { ... while(ns >= NSEC_PER_SEC) { ns -= NSEC_PER_SEC;

[2.6 patch] sched_fair.c: make sched_nr_latency static

sched_nr_latency can now become static. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- fc6c112552b2eb423a29c2b0d100e97db3a47c45 diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c index d3c0307..ee00da2 100644 --- a/kernel/sched_fair.c +++ b/kernel/sched_fair.c @@ -43,7 +43,7 @@ unsigned

[2.6 patch] remove references to "make dep"

"make dep" is no longer required in kernel 2.6, but was still mentioned in some places. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- arch/arm/mach-imx/Makefile |3 --- arch/arm/mach-netx/Makefile|3 --- arch/frv/kernel/gdb-stub.c |

[RFC: 2.6 patch] MAINTAINERS: remove the MTRR entry

I haven't seen Richard doing MTRR related work for quite some time, and the "X86 ARCHITECTURE" entry in MAINTAINERS already covers the people currently responsible for this code. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- abbbf23fd306fc62d3b13c8e199142b3409d5ebd diff --git

[2.6 patch] include/linux/sysctl.h: remove empty #else

This patch removes an empty #else. Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- 8e3fb6d59ceb3fbb853c0d74f1aa0a73de90af97 diff --git a/include/linux/sysctl.h b/include/linux/sysctl.h index e99171f..4c1694d 100644 --- a/include/linux/sysctl.h +++ b/include/linux/sysctl.h @@ -1070,8 +1070,6

Re: [PATCH 2/2] Version 11 (2.6.24-rc2) Smack: Simplified Mandatory Access Control Kernel

--- Eric Paris <[EMAIL PROTECTED]> wrote: > [snip from fs/super.c:vfs_kern_mount() just for reference] > if (data) { > secdata = alloc_secdata(); > if (!secdata) > goto out_mnt; > > error =

Re: Temporary lockup on loopback block device

> > > Arguably we just have the wrong backing-device here, and what we > > > should do is to propagate the real backing device's pointer through > > > up into the filesystem. There's machinery for this which things > > > like DM stacks use. Just thinking about the new implementation --- you

Re:

From: Eric Dumazet <[EMAIL PROTECTED]> Date: Sat, 10 Nov 2007 02:42:42 +0100 > [NET] adds a missing include > > Signed-off-by: Eric Dumazet <[EMAIL PROTECTED]> Applied, thanks Eric. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL

Re: [PATCH] kconfig: use $K64BIT to set 64BIT with all*config targets

On Sat, Nov 10, 2007 at 09:55:06PM +0100, Guillaume Chazarain wrote: > Hi, > > On 11/10/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: > > The variable K64BIT can now be used to select the > > value of CONFIG_64BIT. > > Why not calling the environment variable CONFIG_64BIT, > in preparation of the

Re: [PATCH 0/5] introduce K64BIT=y and backward compatibility ARCH={i386,x86_64} for x86

On Sat, Nov 10, 2007 at 09:40:38PM +0100, Sam Ravnborg wrote: > As discussed in another thread the right thing is to add a generic solution > to select between 32 and 64 bit - useable for powerpc, s390, ppc et al. >... I seriously question this would be "the right thing". 32/64bit isn't that

Re: cd/dvd inaccessible in 2.6.24-rc2

Hello Jeff, Yes it is. I'll keep testing with previous kernels. Dmesg does look different with 2.6.23 vs 2.6.24-rc2 This is 2.6.23 : scsi8 : pata_jmicron scsi9 : pata_jmicron ata9: PATA max UDMA/100 cmd 0x0001c000 ctl 0x0001c102 bmdma 0x0001c400 irq 17 ata10: PATA max

Re: AppArmor Security Goal

On Sat, 10 Nov 2007, John Johansen wrote: On Sat, Nov 10, 2007 at 03:52:31PM -0800, [EMAIL PROTECTED] wrote: On Sat, 10 Nov 2007, Dr. David Alan Gilbert wrote: Allowing a user to tweak (under constraints) their settings might allow them to do something like create two mozilla profiles which

Re: [PATCH] [POWERPC] Fix CONFIG_SMP=n build error on ppc64

On Sat, Nov 10, 2007 at 02:59:29PM -0600, Olof Johansson wrote: > [POWERPC] Fix CONFIG_SMP=n build error > > The patch "KVM: fix !SMP build error" change the way smp_call_function() > actually uses the passed in function names on non-SMP builds. So > previously it was never caught that the

Re: AppArmor Security Goal

On Sat, Nov 10, 2007 at 03:52:31PM -0800, [EMAIL PROTECTED] wrote: > On Sat, 10 Nov 2007, Dr. David Alan Gilbert wrote: > > > a question for Crispin, > is there a wildcard replacement for username? so that you could grant > permission to /home/$user/.mozilla.. and grant each user access

Re: [PATCH] time: fix sysfs_show_{available,current}_clocksources() buffer overflow problem

On Sun, Nov 11, 2007 at 11:29:59AM +0800, Miao Xie wrote: >on 2007-11-8 20:11 WANG Cong wrote: >>On Thu, Nov 08, 2007 at 07:47:41PM +0800, WANG Cong wrote: >>>Yes, snprintf is safer than sprintf. But here, the 'count' will be >>>mis-pointed when snprintf returns no less than PAGE_SIZE (what you

Re: [PATCH, RFC] improved hacks to allow -rt to run kernbench on POWER

> Removed this as well, also seemed to work. Please note, however, that > this is just running kernbench. But this did seem to get rid of some > of the warnings as well. ;-) Now only have the xics_startup() warning. > > > Overall, looks fine ! > > I bet that there are more gotchas lurking

Re: AppArmor Security Goal

On Sat, Nov 10, 2007 at 05:27:51PM -0800, [EMAIL PROTECTED] wrote: > On Sat, 10 Nov 2007, Alan Cox wrote: > >>> but how can the system know if the directory the user wants to add is >>> reasonable or not? what if the user says they want to store their >>> documents in /etc? >> >> A more clear

[PATCH] log2.h: Define order_base_2() macro for convenience.

Given a number of places in the tree that need to calculate this value explicitly, might as well just create a macro for it. Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]> --- run-time tested for the first several values. note that this macro is defined strictly in terms of rounding

Re: Temporary lockup on loopback block device

On Sun, 11 Nov 2007, Mikulas Patocka wrote: > On Sat, 10 Nov 2007, Andrew Morton wrote: > > > On Sat, 10 Nov 2007 20:51:31 +0100 (CET) Mikulas Patocka <[EMAIL > > PROTECTED]> wrote: > > > > > Hi > > > > > > I am experiencing a transient lockup in 'D' state with loopback device. > > > It > >

Re: AppArmor Security Goal

On Sat, Nov 10, 2007 at 06:17:30PM -0800, Casey Schaufler wrote: > > --- Crispin Cowan <[EMAIL PROTECTED]> wrote: > > > Dr. David Alan Gilbert wrote: > > ... > > > > Can you explain why you want a non-privileged user to be able to edit > > policy? I would like to better understand the problem

Re: AppArmor Security Goal

On Sat, Nov 10, 2007 at 01:28:25PM -0800, [EMAIL PROTECTED] wrote: > On Sat, 10 Nov 2007, Andi Kleen wrote: > >> Crispin Cowan <[EMAIL PROTECTED]> writes: >> >> The document should be a good base for a merge. >> >>> * A confined process can operate on a file descriptor passed to it >>>

NFSv4 broken in -mm (MMOM "10-Nov-2007 22:46")

I'm using http://userweb.kernel.org/~akpm/mmotm/ timestamped "10-Nov-2007 22:46". Creating dummy f/s and exporting it to localhost, mounting it as nfsv4, then # touch foo touch: setting times of `foo': No such file or directory # echo > bar bar: Invalid argument Erez. - To unsubscribe from

Re: [PATCH] time: fix sysfs_show_{available,current}_clocksources() buffer overflow problem

on 2007-11-8 20:11 WANG Cong wrote: On Thu, Nov 08, 2007 at 07:47:41PM +0800, WANG Cong wrote: Yes, snprintf is safer than sprintf. But here, the 'count' will be mis-pointed when snprintf returns no less than PAGE_SIZE (what you called overflow). So you may also need: if

Re: AppArmor Security Goal

On Sat, Nov 10, 2007 at 01:24:46PM -0800, Crispin Cowan wrote: > Andi Kleen wrote: > > Crispin Cowan <[EMAIL PROTECTED]> writes: > > > > The document should be a good base for a merge. > > > > > >> * A confined process can operate on a file descriptor passed to it > >> by an

Re: [RFC 13/13] Char: nozomi, cleanup read and write

On Samstag 10 November 2007 23:04:41, you (Jiri Slaby) wrote: > On 11/10/2007 05:15 PM, Adrian Bunk wrote: > > On Fri, Nov 09, 2007 at 06:51:35PM -0500, Jiri Slaby wrote: > >> ... > >> - if (size_bytes - i == 2) { > >> + if (unlikely(size_bytes - i == 2)) { > >> ... > > > >

Re: patch conflicts (MMOTM "10-Nov-2007 22:46")

On Sat, 10 Nov 2007 20:04:35 -0500 Erez Zadok <[EMAIL PROTECTED]> wrote: > Andrew, > > I'm using http://userweb.kernel.org/~akpm/mmotm/ timestamped "10-Nov-2007 > 22:46". > > 1. I was getting a bunch of patch conflicts, until I realized that this >latest set of patches was to be applied

Re: [PATCH] make ds1wm driver to check ds1wm_platform_data pointer against NULL

On Nov 11, 2007 1:08 AM, Evgeniy Polyakov <[EMAIL PROTECTED]> wrote: > On Fri, Nov 09, 2007 at 05:02:38PM -0800, Andrew Morton ([EMAIL PROTECTED]) > wrote: > > > @@ -351,6 +351,10 @@ static int ds1wm_probe(struct platform_device *pdev) > > > goto err0; > > > } > > > plat =

Re: AppArmor Security Goal

--- Crispin Cowan <[EMAIL PROTECTED]> wrote: > Dr. David Alan Gilbert wrote: > ... > > Can you explain why you want a non-privileged user to be able to edit > policy? I would like to better understand the problem here. > > Note that John Johansen is also interested in allowing non-privileged >

Re: [PATCH 1/6] Suppress A.OUT library support if !CONFIG_BINFMT_AOUT [try #5]

On Fri, 09 Nov 2007 15:34:37 + David Howells <[EMAIL PROTECTED]> wrote: > --- a/include/linux/Kbuild > +++ b/include/linux/Kbuild > @@ -1,3 +1,4 @@ > +# -*- makefile -*- what's that? > header-y += byteorder/ > header-y += dvb/ > header-y += hdlc/ > @@ -17,7 +18,9 @@ header-y += usb/ >

Re: AppArmor Security Goal

On Sat, 10 Nov 2007, Alan Cox wrote: but how can the system know if the directory the user wants to add is reasonable or not? what if the user says they want to store their documents in /etc? A more clear example is wanting to wrap a specific tool with temporary rules. Those rules would

patch conflicts (MMOTM "10-Nov-2007 22:46")

Andrew, I'm using http://userweb.kernel.org/~akpm/mmotm/ timestamped "10-Nov-2007 22:46". 1. I was getting a bunch of patch conflicts, until I realized that this latest set of patches was to be applied against 2.6.24-rc2 (your mm.patch gave it away :-) The last snapshot was against

[PATCH] kernel/capability.c get_task_comm compile error (MMOTM)

Using http://userweb.kernel.org/~akpm/mmotm/ timestamped "10-Nov-2007 22:46". $ make CC kernel/capability.o kernel/capability.c: In function 'sys_capset': kernel/capability.c:231: warning: passing argument 1 of 'get_task_comm' from incompatible pointer type kernel/capability.c:231:

[PATCH] mm/memory.c follow_hugetlb_page compiler error (MMOTM)

Using http://userweb.kernel.org/~akpm/mmotm/ timestamped "10-Nov-2007 22:46". CONFIG_HUGETLB_PAGE not set. $ make CC mm/memory.o mm/memory.c:1040:29: error: macro "follow_hugetlb_page" passed 8 arguments, but takes just 7 mm/memory.c: In function 'get_user_pages': mm/memory.c:1039:

Re: [PATCH] Include header required for INT_MAX

On Samstag, 10. November 2007, Christoph Hellwig wrote: > On Sat, Nov 10, 2007 at 03:55:15PM +0100, Thomas Koeller wrote: > > cdrom.h uses INT_MAX, so it must include kernel.h or > > limits.h (userspace) for a definition. > > Nack, we shoiuld never include userspace headers in kernel headers, > an

[PATCH 2/2] [e1000 VLAN] Disable vlan hw accel when promiscuous mode

IMHO even though netdevice is in the promiscuous mode, we should receive all of ingress packets. This disable the vlan filtering feature when a vlan hw accel configured e1000 device goes into promiscuous mode. This make packets visible to sniffers though it's not vlan id of itself. Any check,

[PATCH 1/2] [VLAN] Don't drop an unclassfied vlan packet as PACKET_OTHERHOST

IMHO linux should not drop unclassified vlan packets to pass these to sniffers. isn't it? But, since the __vlan_hwaccel_rx drops unclassified vlan packets, sniffers cannot see them. This make the __vlan_hwaccel_rx receive and process an unclassified vlan packet as a PACKET_OTHERHOST. Any check,

Re: Temporary lockup on loopback block device

> > Arguably we just have the wrong backing-device here, and what we should do > > is to propagate the real backing device's pointer through up into the > > filesystem. There's machinery for this which things like DM stacks use. > > > > I wonder if the post-2.6.23 changes happened to make this

Re: Temporary lockup on loopback block device

On Sat, 10 Nov 2007, Andrew Morton wrote: > On Sat, 10 Nov 2007 20:51:31 +0100 (CET) Mikulas Patocka <[EMAIL PROTECTED]> > wrote: > > > Hi > > > > I am experiencing a transient lockup in 'D' state with loopback device. It > > happens when process writes to a filesystem in loopback with

Warning: commit message does not conform to UTF-8. (mmotm "10-Nov-2007 22:46")

Andrew, I'm getting minor warnings when applying two patches from It's probably not serious but I wonder if checkpatch catches this. Applying patch..git-net.patch Warning: commit message does not conform to UTF-8. You may want to amend it after fixing

Re: WARNING: at lib/kref.c:33 kref_get() (-mm 2007-11-06-02-32++)

In message <[EMAIL PROTECTED]>, Andrew Morton writes: > On Fri, 9 Nov 2007 21:12:47 -0500 Erez Zadok <[EMAIL PROTECTED]> wrote: > > > Setup: FC6 system with MM snapshot broken-out-2007-11-06-02-32 > > That's a bit old. > > > and these two > > patches added: > > > >

Re: Fw: Buffer overflow in CIFS VFS.

Steve French wrote: > On Nov 10, 2007 7:03 AM, Przemyslaw Wegrzyn <[EMAIL PROTECTED]> wrote: > >> Steve French wrote: >> >>> That might be better, although without memory pools, this would perform >>> much worse >>> >>> >> Why ? I don't get your point here. >> > What I meant is

Re: cd/dvd inaccessible in 2.6.24-rc2

On Sat, 10 Nov 2007 23:05:53 + Alan Cox <[EMAIL PROTECTED]> wrote: > > > ata9.00: qc timeout (cmd 0xa0) > > > ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen > > > ata9.00: cmd a0/00:00:00:02:00/00:00:00:00:00/a0 tag 0 cdb 0x5a data 2 > > > in > > > res

Re: USB storage: corrupted data transfers

Mark Lord wrote: Mark Lord wrote: Something may be broken in USB / usb-storage land. I've got a 2GB USB stick here. I want to copy it to an image file on my hard drive: cat /dev/sdb > usbkey.image1 Make a second copy, with or without unplugging/replugging the stick: cat /dev/sdb >

problems with spi interface & ads 784X under 2.6.23

on kernel 2.6.23 , with an Arm AT91rm9200 sometimes when i "pen-down" on the touch screen,I'm seeing ads7846 spi0.0: touchscreen, irq 75 input: ADS784x Touchscreen as /devices/platform/atmel_spi.0/spi0.0/input/input0 at91_rtc at91_rtc: rtc core: registered at91_rtc as rtc0 atmel_spi

Re: AppArmor Security Goal

> but how can the system know if the directory the user wants to add is > reasonable or not? what if the user says they want to store their > documents in /etc? A more clear example is wanting to wrap a specific tool with temporary rules. Those rules would depend on the exact file being edited

Re: AppArmor Security Goal

> I submit that the AppArmor model is valid, even if it totally failed all > of David Gilbert's questions (I think AppArmor can actually provide > about half of what he asked for). The model looks valid. I have difficulty constructing many scenarios where its useful but it appears valid providing

Re: AppArmor Security Goal

* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: That I wrote: > >If the adminisrator set something up with (2) as the starting point it > >would seem reasonable for the user to be able to add the ability to edit > >documents in extra directories for their style of organising documents > >they work

Re: AppArmor Security Goal

On Sat, 10 Nov 2007, Dr. David Alan Gilbert wrote: Can you explain why you want a non-privileged user to be able to edit policy? I would like to better understand the problem here. I think it might depend on how strict the users starting point is; you could say: 1 This document editor can

Re: cd/dvd inaccessible in 2.6.24-rc2

Will Trives wrote: Hello, Motherboard: Gigabyte GA-P35-DS4 (rev. 1.1) Chipset: Intel P35 + ICH9R PATA port runs off JMicron controller CD/DVD Device: BENQ DW1640 16X I cannot access my dvd burner under 2.6.24-rc2, I have no problems under 2.6.23. Basically the drive is detected OK,

Re: [PATCH] drivers/video/s1d13xxxfb.c as module with dbg

On 11/10/07, Stanislav Brabec <[EMAIL PROTECTED]> wrote: > Attached patch fixes two compilation problems of s1d13xxxfb.c: > - Fixes outdated dbg() message to fix compilation error with debugging > enabled. > - Do not read kernel command line options when compiled as module. > > Signed-off-by:

Re: cd/dvd inaccessible in 2.6.24-rc2

Alan Cox wrote: ata9.00: qc timeout (cmd 0xa0) ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata9.00: cmd a0/00:00:00:02:00/00:00:00:00:00/a0 tag 0 cdb 0x5a data 2 in res 51/54:03:00:02:00/00:00:00:00:00/a0 Emask 0x5 (timeout) ata9.00: status: { DRDY ERR } Could be

Re: AppArmor Security Goal

* Crispin Cowan ([EMAIL PROTECTED]) wrote: > Dr. David Alan Gilbert wrote: > > * Crispin Cowan ([EMAIL PROTECTED]) wrote: > > > >> I don't get the problem: if you want your web browser to be able to > >> access where you commonly store your documents, then give it that > >> permission. The

Re: [BUG]: Crash with CONFIG_FAIR_CGROUP_SCHED=y

Serge E. Hallyn [EMAIL PROTECTED] wrote: | Quoting Srivatsa Vaddagiri ([EMAIL PROTECTED]): | > On Fri, Nov 09, 2007 at 09:45:21AM +0100, Dmitry Adamushko wrote: | > > Humm... the 'current' is not kept within the tree but | > > current->se.on_rq is supposed to be '1' , | > > so the old code looks

Re: AppArmor Security Goal

Alan Cox wrote: >> Can you explain why you want a non-privileged user to be able to edit >> policy? I would like to better understand the problem here. >> > Because root doesn't trust users who in turn may not trust apps they run > or wish to control things. I don't see a problem with that

Re: cd/dvd inaccessible in 2.6.24-rc2

On Sat, 10 Nov 2007 14:49:23 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote: > On Sat, 10 Nov 2007 15:27:11 +1100 Will Trives <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > > Motherboard: Gigabyte GA-P35-DS4 (rev. 1.1) > > Chipset: Intel P35 + ICH9R > > PATA port runs off JMicron controller

[PATCH] NFS: Fix the ustat() regression

From: Trond Myklebust <[EMAIL PROTECTED]> Since 2.6.18, the superblock sb->s_root has been a dummy dentry with a dummy inode. This breaks ustat(), which actually uses sb->s_root in a vfstat() call. Fix this by making the s_root a dummy alias to the directory inode that was used when creating the

Re: Temporary lockup on loopback block device

On Sat, 2007-11-10 at 14:54 -0800, Andrew Morton wrote: > On Sat, 10 Nov 2007 20:51:31 +0100 (CET) Mikulas Patocka <[EMAIL PROTECTED]> > wrote: > > > Hi > > > > I am experiencing a transient lockup in 'D' state with loopback device. It > > happens when process writes to a filesystem in

Re: AppArmor Security Goal

> Can you explain why you want a non-privileged user to be able to edit > policy? I would like to better understand the problem here. Because root doesn't trust users who in turn may not trust apps they run or wish to control things. I don't see a problem with that viewpoint in terms of

Re: Temporary lockup on loopback block device

On Sat, 10 Nov 2007 20:51:31 +0100 (CET) Mikulas Patocka <[EMAIL PROTECTED]> wrote: > Hi > > I am experiencing a transient lockup in 'D' state with loopback device. It > happens when process writes to a filesystem in loopback with command like > dd if=/dev/zero of=/s/fill bs=4k > > CPU is

Re: WARNING: at lib/kref.c:33 kref_get() (-mm 2007-11-06-02-32++)

On Fri, 9 Nov 2007 21:12:47 -0500 Erez Zadok <[EMAIL PROTECTED]> wrote: > Setup: FC6 system with MM snapshot broken-out-2007-11-06-02-32 That's a bit old. > and these two > patches added: > > r-o-bind-mounts-track-number-of-mount-writer-fix-buggy-loop.patch >

Re: cd/dvd inaccessible in 2.6.24-rc2

On Sat, 10 Nov 2007 15:27:11 +1100 Will Trives <[EMAIL PROTECTED]> wrote: > > Hello, > > Motherboard: Gigabyte GA-P35-DS4 (rev. 1.1) > Chipset: Intel P35 + ICH9R > PATA port runs off JMicron controller > CD/DVD Device: BENQ DW1640 16X > > I cannot access my dvd burner under 2.6.24-rc2, I have

Re: [PATCH 0/5] introduce K64BIT=y and backward compatibility ARCH={i386,x86_64} for x86

On Sat, Nov 10, 2007 at 02:33:02PM -0800, Randy Dunlap wrote: > On Sat, 10 Nov 2007 21:40:38 +0100 Sam Ravnborg wrote: > > > As discussed in another thread the right thing is to add a generic solution > > to select between 32 and 64 bit - useable for powerpc, s390, ppc et al. > > > > First step

Re: AppArmor Security Goal

Dr. David Alan Gilbert wrote: > * Crispin Cowan ([EMAIL PROTECTED]) wrote: > >> I don't get the problem: if you want your web browser to be able to >> access where you commonly store your documents, then give it that >> permission. The above rule says that your web browser doesn't get to go >>

Re: AppArmor Security Goal

* Crispin Cowan ([EMAIL PROTECTED]) wrote: > * Manipulating AppArmor policy requires being both root privileged > and not being confined by AppArmor, thus there is explicitly no > capability for non-privileged users to change AppArmor policy. It's a pity that there is no way to

Re: [PATCH 0/5] introduce K64BIT=y and backward compatibility ARCH={i386,x86_64} for x86

On Sat, 10 Nov 2007 21:40:38 +0100 Sam Ravnborg wrote: > As discussed in another thread the right thing is to add a generic solution > to select between 32 and 64 bit - useable for powerpc, s390, ppc et al. > > First step was to teach kconfig how to force 64BIT to a specific value. > The x86

Re: [PATCH] kconfig: use $K64BIT to set 64BIT with all*config targets

On Sat, Nov 10, 2007 at 02:16:19PM -0800, Randy Dunlap wrote: > On Sat, 10 Nov 2007 21:43:26 +0100 Sam Ravnborg wrote: > > > The variable K64BIT can now be used to select the > > value of CONFIG_64BIT. > > > > This is for example useful for powerpc to generate > > allmodconfig for both bit sizes

Re: dib7000m_i2c_enumeration() is unused

Hi all, This is another story of "the chip-vendor provides driver support and is waiting for device to hit the market". DiBcom knows that there are devices out there that are using the dib7000m in way that they need the dib7000m_i2c_enumeration to work properly. But it is impossible to know

Re: AppArmor Security Goal

* Crispin Cowan ([EMAIL PROTECTED]) wrote: > Dr. David Alan Gilbert wrote: > > * Crispin Cowan ([EMAIL PROTECTED]) wrote: > > >> * Manipulating AppArmor policy requires being both root privileged > >> and not being confined by AppArmor, thus there is explicitly no > >> capability

Re: [PATCH] kconfig: document make K64BIT=y in README

On Sat, 10 Nov 2007 21:43:28 +0100 Sam Ravnborg wrote: > Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> > --- > README |2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/README b/README > index 159912c..6622ba1 100644 > --- a/README > +++ b/README > @@ -194,6 +194,8

Re: [PATCH] x86: Use CONFIG_64BIT to select between 32 and 64 bit in Kconfig

On Sat, 10 Nov 2007 21:43:27 +0100 Sam Ravnborg wrote: > This change allow us to use the new syntax: > make K64BIT={n,y} to select between 32 and 64 bit. > > Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> > --- > arch/x86/Kconfig | 26 -- > 1 files changed, 8

Re: [PATCH] kconfig: use $K64BIT to set 64BIT with all*config targets

On Sat, 10 Nov 2007 21:43:26 +0100 Sam Ravnborg wrote: > The variable K64BIT can now be used to select the > value of CONFIG_64BIT. > > This is for example useful for powerpc to generate > allmodconfig for both bit sizes - like this: > make ARCH=powerpc K64BIT=y > make ARCH=powerpc K64BIT=n > >

Re: AppArmor Security Goal

Dr. David Alan Gilbert wrote: > * Crispin Cowan ([EMAIL PROTECTED]) wrote: > > * Manipulating AppArmor policy requires being both root privileged >> and not being confined by AppArmor, thus there is explicitly no >> capability for non-privileged users to change AppArmor policy. >>

Re: [PATCH] virtio config_ops refactoring

Rusty Russell wrote: On Saturday 10 November 2007 10:45:38 Anthony Liguori wrote: The problem is the ABI. We can either require that PCI configuration values are accessed with natural instructions, or it makes very little sense to use the PCI configuration space for virtio configuration

Re: [RFC 13/13] Char: nozomi, cleanup read and write

On 11/10/2007 05:15 PM, Adrian Bunk wrote: > On Fri, Nov 09, 2007 at 06:51:35PM -0500, Jiri Slaby wrote: >> ... >> --- a/drivers/char/nozomi.c >> +++ b/drivers/char/nozomi.c >> ... >> -if (size_bytes - i == 2) { >> +if (unlikely(size_bytes - i == 2)) { >> ... > > Please

[git patches] net driver fixes

Please pull from 'upstream-linus' branch of master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git upstream-linus to receive the following updates: MAINTAINERS | 10 ++- drivers/net/Kconfig |2 +-

Re: USB storage: corrupted data transfers

Mark Lord wrote: Something may be broken in USB / usb-storage land. I've got a 2GB USB stick here. I want to copy it to an image file on my hard drive: cat /dev/sdb > usbkey.image1 Make a second copy, with or without unplugging/replugging the stick: cat /dev/sdb > usbkey.image2 After

Re: [PATCH 0/11 v3] enable "make ARCH=x86"

On Sat, Nov 10, 2007 at 12:35:01PM -0800, H. Peter Anvin wrote: > In fact, we should be able to get rid of ARCH entirely; CONFIG_ options > have the huge advantage that they're saved in a file, and you don't have to > type them on every make run. The only option that I can't see us getting >

Re: AppArmor Security Goal

Andi Kleen wrote: > Crispin Cowan <[EMAIL PROTECTED]> writes: > > The document should be a good base for a merge. > > >> * A confined process can operate on a file descriptor passed to it >> by an unconfined process, even if it manipulates a file not in the >> confined process's

Re: [Linux-usb-users] USB storage: corrupted data transfers

On Sat, 10 Nov 2007, Mark Lord wrote: > Something may be broken in USB / usb-storage land. > > I've got a 2GB USB stick here. > I want to copy it to an image file on my hard drive: > > cat /dev/sdb > usbkey.image1 > > Make a second copy, with or without unplugging/replugging the stick: >

Re: AppArmor Security Goal

On Sat, 10 Nov 2007, Andi Kleen wrote: Crispin Cowan <[EMAIL PROTECTED]> writes: The document should be a good base for a merge. * A confined process can operate on a file descriptor passed to it by an unconfined process, even if it manipulates a file not in the confined

2.6.24-rc2 STD with s2disk fails to activate suspended system after loading

please cc me, I'm not not subscribed to LKML Hello, with kernel 2.6.24-rc2 STD with s2disk suspends the system to disk, but when I start the system and the suspended systemimage is loaded, it fails to "activate" this suspended systemimage and continues after some time with following the normal

USB storage: corrupted data transfers

Something may be broken in USB / usb-storage land. I've got a 2GB USB stick here. I want to copy it to an image file on my hard drive: cat /dev/sdb > usbkey.image1 Make a second copy, with or without unplugging/replugging the stick: cat /dev/sdb > usbkey.image2 After doing this, the

Re: AppArmor Security Goal

Crispin Cowan <[EMAIL PROTECTED]> writes: The document should be a good base for a merge. > * A confined process can operate on a file descriptor passed to it > by an unconfined process, even if it manipulates a file not in the > confined process's profile. To block this attack,

[PATCH] [POWERPC] Fix CONFIG_SMP=n build error on ppc64

[POWERPC] Fix CONFIG_SMP=n build error The patch "KVM: fix !SMP build error" change the way smp_call_function() actually uses the passed in function names on non-SMP builds. So previously it was never caught that the function passed in was never actually defined. This causes a build error on

Re: [PATCH] kconfig: use $K64BIT to set 64BIT with all*config targets

Hi, On 11/10/07, Sam Ravnborg <[EMAIL PROTECTED]> wrote: > The variable K64BIT can now be used to select the > value of CONFIG_64BIT. Why not calling the environment variable CONFIG_64BIT, in preparation of the day when all CONFIG_ variables can be passed by environment variables? -- Guillaume

Re: [PATCH 0/11 v3] enable "make ARCH=x86"

On Sat, Nov 10, 2007 at 12:35:01PM -0800, H. Peter Anvin wrote: > > HOWEVER, I think the right thing for allyesconfig, allmodconfig, > randconfig, etc. is to be able to override specific variables. Right > now, one has to use indirection via a file, which is a bit clumsy; it > would be better

[PATCH] kconfig: document make K64BIT=y in README

Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> --- README |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/README b/README index 159912c..6622ba1 100644 --- a/README +++ b/README @@ -194,6 +194,8 @@ CONFIGURING the kernel: "make *config" checks for a file named

[PATCH] kconfig: use $K64BIT to set 64BIT with all*config targets

The variable K64BIT can now be used to select the value of CONFIG_64BIT. This is for example useful for powerpc to generate allmodconfig for both bit sizes - like this: make ARCH=powerpc K64BIT=y make ARCH=powerpc K64BIT=n To use this the Kconfig file must use "64BIT" as the config value to

[PATCH] x86: introduce ARCH=i386,ARCH=x86_64 to select 32/64 bit

Using the newly added infrastructure is is now simple to add addition ARCH= symbols to select between 32 and 64 bit. Do this for x86. Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> --- Makefile | 16 +--- arch/x86/Makefile| 10 +++---

[PATCH] x86: Use CONFIG_64BIT to select between 32 and 64 bit in Kconfig

This change allow us to use the new syntax: make K64BIT={n,y} to select between 32 and 64 bit. Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> --- arch/x86/Kconfig | 26 -- 1 files changed, 8 insertions(+), 18 deletions(-) diff --git a/arch/x86/Kconfig

[PATCH] kconfig: factor out code in confdata.c

This patch introduce no functional changes. Signed-off-by: Sam Ravnborg <[EMAIL PROTECTED]> Cc: Roman Zippel <[EMAIL PROTECTED]> --- scripts/kconfig/confdata.c | 119 +++ 1 files changed, 64 insertions(+), 55 deletions(-) diff --git

[PATCH 0/5] introduce K64BIT=y and backward compatibility ARCH={i386,x86_64} for x86

As discussed in another thread the right thing is to add a generic solution to select between 32 and 64 bit - useable for powerpc, s390, ppc et al. First step was to teach kconfig how to force 64BIT to a specific value. The x86 Kconfig file needed a small twist to use 64BIT as the symbol to

Re: [PATCH 0/11 v3] enable "make ARCH=x86"

Paul Mundt wrote: Indeed, that's what I was intending on keeping around as a convention, and simply overloading SRCARCH for the sh64 case. i386/x86_64 potentially has the same issue though, and if the intent is to have a single ARCH for both of them, I don't see how that would possibly work

Re: [PATCH] fix up perfmon to build on -mm

Greg KH <[EMAIL PROTECTED]> writes: [dropped perfmon list because gmane messed it up and it's apparently closed anyways] > Is there any way to just provide a basic framework that everyone can > agree on and then add on more stuff as time goes on? Do we have to have > every different

Re: Laptop's HDD

Maciej W. Rozycki wrote: On Sun, 4 Nov 2007, Alberto Gonzalez wrote: The problem comes from a very high rate of load/unload cycles of the heads that reaches the 300.000-600.000 limit in 2-3 years (with smartmontools it can checked it with "smartctl -A /dev/sda") . There are reports of

Re: Module init call vs symbols exporting race?

Jan Glauber <[EMAIL PROTECTED]> writes: > I've seen a symbol-resolving race on s390. The qeth module uses symbols > from qdio and although the loading order seems correct and the qdio > symbols should be available the following error appears: FWIW i see such messages all the time with usb serial

  1   2   3   4   >