[PATCH 09/16] Unionfs: don't create whiteouts on rightmost branch

If we are unlinking/rmdir'ing an object on the rightmost branch, there's no need to create a whiteout there: this saves on storage space and inodes. Also, in the (degenerate) case of having only one branch, this really saves on whiteouts. CC: Hugh Dickins <[EMAIL PROTECTED]> Signed-off-by:

Re: [2.6 patch] remove CONFIG_EXPERIMENTAL

On Sun 2007-11-25 17:16:31, Adrian Bunk wrote: > This patch removes the EXPERIMENTAL option and all dependencies on > EXPERIMENTAL because they are pointless. > > Complete rationale: > - Many people and all distributions are currently forced to enable > CONFIG_EXPERIMENTAL since the options

[PATCH 04/16] Unionfs: minor cleanup in the debugging infrastructure

Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/debug.c | 64 --- 1 files changed, 30 insertions(+), 34 deletions(-) diff --git a/fs/unionfs/debug.c b/fs/unionfs/debug.c index bc221d6..c2b8b58 100644 --- a/fs/unionfs/debug.c +++

[PATCH 03/16] Unionfs: minor coding standards applied

Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/copyup.c |4 ++-- fs/unionfs/dirfops.c |5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/fs/unionfs/copyup.c b/fs/unionfs/copyup.c index 98bed0b..3fe4865 100644 --- a/fs/unionfs/copyup.c +++

[PATCH 06/16] Unionfs: handle whiteouts more efficiently in filldir

If we cache a dirent for file "foo", and then it gets deleted, then we look for a ".wh.foo" whiteout entry in the same dirent cache. But our dirent cache strips the ".wh." prefix, thus looking for an entry named "foo" whose filldir_node->whiteout should be 1 instead of 0. In that case, don't

[PATCH 02/16] Unionfs: minor cleanup in writepage

From: Hugh Dickins <[EMAIL PROTECTED]> Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/mmap.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/unionfs/mmap.c b/fs/unionfs/mmap.c index 4918f77..1e10280 100644 --- a/fs/unionfs/mmap.c +++

[PATCH 01/16] Unionfs: use f_path instead of f_dentry/mnt

Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/debug.c |2 +- fs/unionfs/fanout.h |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/unionfs/debug.c b/fs/unionfs/debug.c index 8464fbb..bc221d6 100644 --- a/fs/unionfs/debug.c +++ b/fs/unionfs/debug.c @@

[PATCH 05/16] Unionfs: set lower mnt after mkdir which resulted in copyup

Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/inode.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/fs/unionfs/inode.c b/fs/unionfs/inode.c index 1708f40..9c144be 100644 --- a/fs/unionfs/inode.c +++ b/fs/unionfs/inode.c @@ -674,8 +674,10 @@ out:

[PATCH 16/16] Unionfs: use generic_file_aio_read/write

There's no apparent need to define our own aio_read/write methods. Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/file.c | 27 ++- 1 files changed, 2 insertions(+), 25 deletions(-) diff --git a/fs/unionfs/file.c b/fs/unionfs/file.c index b7d0d55..c922173

[PATCH 12/16] Unionfs: reintroduce a bmap method

This is needed for swapon(2) files in the union. Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/mmap.c | 23 +++ 1 files changed, 23 insertions(+), 0 deletions(-) diff --git a/fs/unionfs/mmap.c b/fs/unionfs/mmap.c index 3f65e52..fa358ef 100644 ---

[PATCH 08/16] Unionfs: release lower resources on successful rmdir

This patch prevents those resources from lingering around until memory pressure would have forced them out. The patch also properly handles directories that have been rmdir'ed which are still some process's cwd. CC: Hugh Dickins <[EMAIL PROTECTED]> Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>

[PATCH 07/16] Unionfs: remove useless debugging messages

These are considered normal behaviour, they don't really reveal any insight to the person debugging the code, and they tend to clutter console messages. Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/commonfops.c |5 - fs/unionfs/dentry.c | 15 +++ 2 files

[PATCH 11/16] Unionfs: update times in setattr

Needed to maintain Unix semantics via utimes(2). Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/inode.c | 12 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/fs/unionfs/inode.c b/fs/unionfs/inode.c index ef61d9c..63ff3d3 100644 ---

[PATCH 13/16] Unionfs: support splice(2)

Also remove redundant variable from unionfs_readpage (saves a bit on stack space). Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/file.c |1 + fs/unionfs/mmap.c | 10 -- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/fs/unionfs/file.c

[PATCH 15/16] Unionfs: update our inode size correctly upon partial write

Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/mmap.c |9 ++--- 1 files changed, 2 insertions(+), 7 deletions(-) diff --git a/fs/unionfs/mmap.c b/fs/unionfs/mmap.c index ea5ef3d..8c07eed 100644 --- a/fs/unionfs/mmap.c +++ b/fs/unionfs/mmap.c @@ -250,7 +250,6 @@ static int

[PATCH 10/16] Unionfs: create opaque directories' whiteouts unconditionally

Needed to maintain Unix semantics (LTP testing). Signed-off-by: Erez Zadok <[EMAIL PROTECTED]> --- fs/unionfs/subr.c | 14 ++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git a/fs/unionfs/subr.c b/fs/unionfs/subr.c index 968ee8c..1a26c57 100644 --- a/fs/unionfs/subr.c

[GIT PULL -mm] 00/16 Unionfs updates/fixes/cleanups

The following is a series of patches related to Unionfs. The main changes here are bug fixes (mostly discovered using ltp-full-20071031), as well as full support for splice(2) and swapon(2). These patches were tested (where appropriate) on Linus's 2.6.24 latest code (as of

[PATCH] Send IN_ATTRIB events when link count changes

Hi Andrew, would you pick up this patch for testing in -mm? Thanks. Honza -- Jan Kara <[EMAIL PROTECTED]> SUSE Labs, CR --- Send inotify events to the inode itself when its link count has changed. Signed-off-by: Jan Kara

Re: [PATCH] -mm (2.6.24-rc3-mm1) Smack using capabilities 32 and 33

Quoting Casey Schaufler ([EMAIL PROTECTED]): > From: Casey Schaufler <[EMAIL PROTECTED]> > > This patch takes advantage of the increase in capability bits > to allocate capabilities for Mandatory Access Control. Whereas > Smack was overloading a previously allocated capability it is > now using a

Re: PCMCIA serial_cs driver binding problems.

On Nov 23, 9:40am, "Kay Sievers" wrote: } Subject: Re: PCMCIA serial_cs driver binding problems. Hi Kay, thanks for the note. > > I've tried to manually echo the device number (0.0 or 1.0) into the > > /sys/bus/pcmcia/drivers/serial_cs/bind pseudo-file but nothing > > happens. The device

Re: time accounting problem (powerpc only?)

Contrary to what I claimed later in the thread, my 64-bit powerpc box (quad-core G5) doesn't suffer from this problem. Does anybody have any idea? I don't even know how to debug it further. johannes signature.asc Description: This is a digitally signed message part

Re: [UPDATED PATCH] IP22ZILOG: fix lockup and sysrq

On Mon, Nov 26, 2007 at 04:58:03PM +0100, Thomas Bogendoerfer wrote: > - fix lockup when switching from early console to real console > - make sysrq reliable > - fix panic, if sysrq is issued before console is opened > > Signed-off-by: Thomas Bogendoerfer <[EMAIL PROTECTED]> Acked-by: Ralf

Re: [RFC PATCH] Add CONFIG_BITS to remove the test in arch/x86/Makefile

On Mon, 26 Nov 2007 14:36:07 +0100 Loic Grenie <[EMAIL PROTECTED]> wrote: > > I propose the following patch to arch/x86/Makefile and Kconfig. > > Actions: > > - Add a BITS variable to Kconfig which takes value 32 or 64 according >to 64BIT. Linus' suggestion was WORD_SIZE and

Re: [PATCH 2/2] iwlwifi: add power management support -v2

On Saturday 17 November 2007 07:15:05 Tomas Winkler wrote: > Why power management shouldn't be enabled while in AC? The semantic of this > ioctls is quite unclear. IWL_POWER_AC and IWL_POWER_BATTERY are just two power modes. IWL_POWER_AC would be the default power mode when we're in AC (no power

[git patches] libata fixes

NOTE: This includes 100% of the fixes collected during the week I was on vacation, by Tejun... rebased. So all the commit ids are different from his push. If you have not pulled from Tejun, then pull this. If you have pulled from Tejun, then do not pull this (I will rebase once Tejun's pull

Re: can support for "rpm"-based package building just be dropped?

On Nov 26 2007 11:13, Robert P. J. Day wrote: >> >>>Only on current machines. You'd break building kernel RPMs on older >> >>>systems that don't have rpmbuild installed. >> >> >> >> Those old machines probably do not even run a distro-fabricated >> >> gcc that would compile a git head kernel. >>

Re: can support for "rpm"-based package building just be dropped?

On Mon, 26 Nov 2007, Jan Engelhardt wrote: > > On Nov 26 2007 10:53, Robert P. J. Day wrote: > > > >>>Only on current machines. You'd break building kernel RPMs on older > >>>systems that don't have rpmbuild installed. > >> > >> Those old machines probably do not even run a distro-fabricated > >>

[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: drivers/net/Kconfig|2 +- drivers/net/amd8111e.c |6 ++ drivers/net/bfin_mac.c |2 +-

[UPDATED PATCH] IP22ZILOG: fix lockup and sysrq

- fix lockup when switching from early console to real console - make sysrq reliable - fix panic, if sysrq is issued before console is opened Signed-off-by: Thomas Bogendoerfer <[EMAIL PROTECTED]> --- arch/mips/sgi-ip22/ip22-setup.c | 19 --- drivers/serial/ip22zilog.c | 247

Re: can support for "rpm"-based package building just be dropped?

On Nov 26 2007 10:53, Robert P. J. Day wrote: > >>>Only on current machines. You'd break building kernel RPMs on older >>>systems that don't have rpmbuild installed. >> >> Those old machines probably do not even run a distro-fabricated gcc that >> would compile a git head kernel. > >well, in a

Re: [PATCH] [libata] Return proper ATA INT status in pata_bf54x driver.

sonic zhang wrote: INT status can be OR. Signed-off-by: Sonic Zhang <[EMAIL PROTECTED]> --- drivers/ata/pata_bf54x.c |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) applied - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message

Logwatch errors not very clear

Greetings; Running kernel 2.6.24-rc3 on an athlon xp-2800, 333 fsb. >From logwatch: WARNING: Kernel Errors Present [536447.736378] end_request: I/O error, dev hdc, sector ...: 1 Time(s) [536447.736383] Buffer I/O error on device hdc, l ...: 1 Time(s) [536447.736387] Buffer I/O

Re: Inotify fails to send IN_ATTRIB events

> This looks bad, though: > > include/linux/fsnotify.h:121: warning: passing argument 2 of > 'audit_inode_child' from incompatible pointer type > > Missing "->d_inode"? That's the difference between 2.6.22 and 2.6.24-git against which I wrote the patch :).

Re: can support for "rpm"-based package building just be dropped?

On Mon, 26 Nov 2007, Jan Engelhardt wrote: > > On Nov 26 2007 06:58, Ray Lee wrote: > >On Nov 26, 2007 12:54 AM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > >> on current systems, "rpm" no longer has build capability and will > >> fail thusly: > >> > >> rpm --target i386 -ta

Re: [RFC] Documentation about unaligned memory access

> Going back to an earlier example: > void myfunc(u8 *data, u32 value) > { > [...] > *((u16 *) data) = cpu_to_le32(value); > [...] typo? should it be a u32 cast? > To avoid the unaligned memory access, you could rewrite it as follows: > >

Re: [RFC] Documentation about unaligned memory access

> Sidenote: in the above example, you may wish to reorder the fields in the > above structure so that the overall structure uses less memory. For example, > moving field3 to sit inbetween field1 and field2 (where the padding is > inserted) would shrink the overall structure by 1 byte: > >

Re: kernel BUG at fs/inode.c

On Thu 22-11-07 18:20:15, [EMAIL PROTECTED] wrote: > Hi, > > > Thanks for report. It looks like a problem in UDF. Actually I think > > I've already seen a similar report. Are there any IO errors in the logs > > or anything else suspitious? > > > At the risk of reporting further bugs :-)

Re: [PATCH] ehea: Add kdump support

On Mon, 2007-11-26 at 19:16 +1100, Michael Ellerman wrote: > > Hi Thomas, > > I'm sorry, but this patch is all wrong IMHO. > > For kdump we have to assume that the kernel is fundamentally broken, > we've panicked, so something bad has happened - every line of kernel > code that is run

Re: [PATCH 3/4] fib_hash: kmalloc + memset conversion to kzalloc

On Mon, Nov 26, 2007 at 10:24:03AM +, Joonwoo Park wrote: > fib_hash: kmalloc + memset conversion to kzalloc > fix to avoid memset entirely. Patch applied. -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page:

Re: [PATCH 2/4] fib_semantics: kmalloc + memset conversion to kzalloc

On Mon, Nov 26, 2007 at 10:24:03AM +, Joonwoo Park wrote: > fib_semantics: kmalloc + memset conversion to kzalloc > fix to avoid memset entirely. Also applied. -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page:

Re: [PATCH 1/4] xfrm_hash: kmalloc + memset conversion to kzalloc

On Mon, Nov 26, 2007 at 10:23:51AM +, Joonwoo Park wrote: > 2007/11/26, Patrick McHardy <[EMAIL PROTECTED]>: > > How about also switching vmalloc/get_free_pages to GFP_ZERO > > and getting rid of the memset entirely while you're at it? > > > > xfrm_hash: kmalloc + memset conversion to

Re: can support for "rpm"-based package building just be dropped?

On Nov 26 2007 06:58, Ray Lee wrote: >On Nov 26, 2007 12:54 AM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: >> on current systems, "rpm" no longer has build capability and will >> fail thusly: >> >> rpm --target i386 -ta ../kernel-2.6.24rc3g2ffbb837dirty.tar.gz >> --target: unknown option >> >>

[PATCH v2] Add the word 'Warning' in check_nmi_watchdog() output

Our automated test suite looks for keywords like error, fail, warning in the boot log. In the case when the nmi watchdog is determined to be stuck in check_nmi_watchdog(), none of those keywords are displayed. This patch adds a keyword, 'Warning, so it makes it easier to notice when the nmi

Re: can support for "rpm"-based package building just be dropped?

On Nov 26, 2007 7:12 AM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > On Mon, 26 Nov 2007, Robert P. J. Day wrote: > > > On Mon, 26 Nov 2007, Ray Lee wrote: > > > > > On Nov 26, 2007 12:54 AM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > > > on current systems, "rpm" no longer has build

Re: [2.6 patch] ipv4/arp.c:arp_process(): remove bogus #ifdef mess

On Sun, Nov 25, 2007 at 04:30:03PM +, Adrian Bunk wrote: > > > > > > Please look at net/ipv4/arp.c:arp_process() > > > > > > Am I right that CONFIG_NET_ETHERNET=n and CONFIG_NETDEV_1000=y or > > > CONFIG_NETDEV_1=y will not be handled correctly there? > > > > > > And the best solution

Re: [PATCH] utsns: Restore proper namespace handling.

Quoting Eric W. Biederman ([EMAIL PROTECTED]): > > When CONFIG_UTS_NS was removed it seems that we also deleted > the code for handling sysctls in the other then the initial > uts namespace. This patch restores that code. > > Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]> Thanks, Eric.

Re: [linux-usb-devel] [BUG] USB_PERSIST

On Sun, 25 Nov 2007, Raymano Garibaldi wrote: > The device which has the root fs is a READ-ONLY device. There is no > way for it to change between getting detached and reattached to the > computer which is suspended. You might think so at first. But suppose another device of the same type got

Re: can support for "rpm"-based package building just be dropped?

On Mon, 26 Nov 2007, Robert P. J. Day wrote: > On Mon, 26 Nov 2007, Ray Lee wrote: > > > On Nov 26, 2007 12:54 AM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > > on current systems, "rpm" no longer has build capability and will > > > fail thusly: > > > > > > rpm --target i386 -ta

Re: can support for "rpm"-based package building just be dropped?

On Mon, 26 Nov 2007, Ray Lee wrote: > On Nov 26, 2007 12:54 AM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > > on current systems, "rpm" no longer has build capability and will > > fail thusly: > > > > rpm --target i386 -ta ../kernel-2.6.24rc3g2ffbb837dirty.tar.gz > > --target: unknown option

Re: [PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar forfixed-link property

On Mon, 2007-11-26 at 17:29 +0300, Vitaly Bordug wrote: > fixed-link says: register new "Fixed/emulated PHY", i.e. PHY that > not connected to the real MDIO bus. > > Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]> > Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]> > > --- > >

Re: [PATCH 2/3] teach set_special_pids() to use struct pid

Oleg Nesterov wrote: > Change set_special_pids() to work with struct pid, not pid_t from global name > space. This again speedups and imho cleanups the code. > > Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]> Acked-by: Pavel Emelyanov <[EMAIL PROTECTED]> > ---

Re: [PATCH 1/3] fix setsid() for sub-namespace /sbin/init

Oleg Nesterov wrote: > sys_setsid() still deals with pid_t's from the global namespace. This means > that the "session > 1" check can't help for sub-namespace init, setsid() can't > succeed because copy_process(CLONE_NEWPID) populates PIDTYPE_PGID/SID links. > > Remove the usage of

Re: can support for "rpm"-based package building just be dropped?

On Nov 26, 2007 12:54 AM, Robert P. J. Day <[EMAIL PROTECTED]> wrote: > on current systems, "rpm" no longer has build capability and will > fail thusly: > > rpm --target i386 -ta ../kernel-2.6.24rc3g2ffbb837dirty.tar.gz > --target: unknown option > > so it would make more sense to just require

Re: [RFC] Documentation about unaligned memory access

On Fri, 23 Nov 2007, Arne Georg Gleditsch wrote: > dean gaudet <[EMAIL PROTECTED]> writes: > > on AMD x86 pre-family 10h the boundary is 8 bytes, and on fam 10h it's 16 > > bytes. the penalty is a mere 3 cycles if an access crosses the specified > > boundary. > > Worth noting though, is that

Re: [PATCH] scatterlist: add more safeguards

On Mon, Nov 26 2007, Tejun Heo wrote: > Add more safeguards to protect against misinterpreting a chain entry > as a normal scatterlist and vice-versa. > > * Make sure the entry isn't a chain when assigning and reading a > normal sg. > > * Clear offset and length when chaining. > >

Re: [PATCH 1/3] fix setsid() for sub-namespace /sbin/init

On 11/26, Oleg Nesterov wrote: > > sys_setsid() still deals with pid_t's from the global namespace. This means > that the "session > 1" check can't help for sub-namespace init, setsid() can't > succeed because copy_process(CLONE_NEWPID) populates PIDTYPE_PGID/SID links. > > Remove the usage of

Re: Question regarding naming scheme (HP Jornada 6XX/7XX)

On Nov 25, 2007 11:30 PM, Paul Mundt <[EMAIL PROTECTED]> wrote: > On Mon, Nov 26, 2007 at 12:03:29AM +0100, Kristoffer Ericson wrote: > > > Why I want to use 600-series/700-series instead of 6XX/7XX is simply > > because 600-series/700-series leaves no doubt. > > > Apparently your end users are

Re: [PATCH 1/2] crypto test: use print_hex_dump from

On Mon, Nov 26, 2007 at 03:13:02PM +0800, Denis Cheng wrote: > these utilities implemented in lib/hexdump.c are more handy, please use this. > > Cc: Randy Dunlap <[EMAIL PROTECTED]> > Signed-off-by: Denis Cheng <[EMAIL PROTECTED]> OK this is pretty nice. But you just missed out because the GCM

Re: [PATCH 05/27] rename open_namei() to open_pathname()

On Thu, Nov 01, 2007 at 04:08:32PM -0700, Dave Hansen wrote: > > open_namei() no longer touches namei's. rename it > to something more appropriate: open_pathname(). The name is quite non-descriptive. What about just leaving it as filp_open and merging this into the previous patches to avoid

[PATCH 2/3] [POWERPC] fsl_soc: add support for gianfar for fixed-link property

fixed-link says: register new "Fixed/emulated PHY", i.e. PHY that not connected to the real MDIO bus. Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]> Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]> --- Documentation/powerpc/booting-without-of.txt |3 + arch/powerpc/sysdev/fsl_soc.c

[PATCH 3/3] [POWERPC] MPC8349E-mITX: Vitesse 7385 PHY is not connected to the MDIO bus

...thus use fixed-link to register proper "Fixed PHY" Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]> Signed-off-by: Vitaly Bordug <[EMAIL PROTECTED]> --- arch/powerpc/boot/dts/mpc8349emitx.dts | 11 ++- 1 files changed, 2 insertions(+), 9 deletions(-) diff --git

[PATCH 1/3] [NET] phy/fixed.c: rework to not duplicate PHY layer functionality

With that patch fixed.c now fully emulates MDIO bus, thus no need to duplicate PHY layer functionality. That, in turn, drastically simplifies the code, and drops down line count. As an additional bonus, now there is no need to register MDIO bus for each PHY, all emulated PHYs placed on the

[PATCH 1/3] fix setsid() for sub-namespace /sbin/init

sys_setsid() still deals with pid_t's from the global namespace. This means that the "session > 1" check can't help for sub-namespace init, setsid() can't succeed because copy_process(CLONE_NEWPID) populates PIDTYPE_PGID/SID links. Remove the usage of task_struct->pid and convert the code to use

[PATCH 2/3] teach set_special_pids() to use struct pid

Change set_special_pids() to work with struct pid, not pid_t from global name space. This again speedups and imho cleanups the code. Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]> --- PT/include/linux/sched.h~2_set_special_pids 2007-11-26 15:52:15.0 +0300 +++ PT/include/linux/sched.h

[PATCH? 3/3] move daemonized kernel threads into the swapper's session

Any reason why daemonized kthread still uses 1,1 special pids? This patch sets 0,0 pids, this matches kthread_create'ed threads. Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]> --- PT/kernel/exit.c~3_daemonize_swapper2007-11-26 16:47:35.0 +0300 +++ PT/kernel/exit.c

[RFC PATCH] Make arch/x86/Makefile_{32,64} more similar

This is a patch to improve the similarity between arch/x86/Makefile_32 and arch/x86/Makefile_64. The remaining differences between both makefiles are nearly trivial and it is probably possible to collapse most of them in arch/x86/Makefile, leaving only a few assignements in

Re: [BUG] 2.6.23-rc3 can't see sd partitions on Alpha

Andrew Morton wrote: > Could be something change in sysfs. Please double-check the config > options, make sure that something important didn't get disabled. > > Failing that, it would be great if you could bisect this down to the > offending commit.

Re: [PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever

Attached the same patch, but it also cleans the manage.c code a bit, because the IRQ types 'simple IRQ', 'level-IRQ' and 'FastEOI' were handled differently while they should be handled the same. Kind Regards, Remy 2007/11/26, Remy Bohmer <[EMAIL PROTECTED]>: > Hello, > > I use 2.6.23.1-rt5 on

Re: XFS related Oops

On Wed, Nov 14, 2007 at 10:04:45 +1100, David Chinner wrote: > On Tue, Nov 13, 2007 at 11:51:19AM +0100, Tino Keitel wrote: > > On Tue, Nov 13, 2007 at 09:27:20 +1100, David Chinner wrote: > > > > [...] > > > > > No. I'd say something got screwed up during suspend/resume. Is it > > >

[RFC PATCH] Add CONFIG_BITS to remove the test in arch/x86/Makefile

I propose the following patch to arch/x86/Makefile and Kconfig. Actions: - Add a BITS variable to Kconfig which takes value 32 or 64 according to 64BIT. - Modify arch/x86/Makefile to use CONFIG_BITS instead of testing ARCH. How this could be expanded: - Either

[PATCH PREEMPT_RT]: On AT91 ARM: GPIO Interrupt handling can/will stall forever

Hello, I use 2.6.23.1-rt5 on the Atmel AT91 series. Interrupt threading on Preempt-RT and ARM works fine, except for (edge-triggered) GPIO interrupts. There is a problem when a new interrupt arives while the interrupt thread is handling the previous interrupt. If this occurs the interrupt

[PATCH] Fix for sched-cfs sysctl.

This trivial patch fixes a compilation error that occurs when CONFIG_FAIR_GROUP_SCHED and !CONFIG_SMP. diff --git a/kernel/sysctl.c b/kernel/sysctl.c index 678223a..8bebf25 100644 --- a/kernel/sysctl.c +++ b/kernel/sysctl.c @@ -330,7 +330,7 @@ static struct ctl_table kern_table[] = {

Re: XFS related Oops

On Wed, Nov 14, 2007 at 10:04:45 +1100, David Chinner wrote: > On Tue, Nov 13, 2007 at 11:51:19AM +0100, Tino Keitel wrote: > > On Tue, Nov 13, 2007 at 09:27:20 +1100, David Chinner wrote: > > > > [...] > > > > > No. I'd say something got screwed up during suspend/resume. Is it > > >

Re: [PATCH 2/2] ide-scsi: use print_hex_dump from

On Mon, Nov 26, 2007 at 04:37:50PM +0800, rae l wrote: > I know this is different from the original hexdump in ide-scsi.c, I > just want to tell someone that there's a good implementation of > hexdump in kernel.h, and I think the default KERN_DEBUG and > print_hex_dump is more informative and has

Re: [UPDATED PATCH] Support for Toshiba TMIO multifunction devices

On Thu, Nov 22, 2007 at 10:52:46AM +, ian wrote: > On Thu, 2007-11-22 at 00:52 +, Russell King - ARM Linux wrote: > > On Thu, Nov 22, 2007 at 12:34:09AM +, ian wrote: > > > Unfortunately, this is broken as designed (in fact this whole file is.) > > Fix attached below. Thanks. > +

Re: [REQUEST] Option for skipping unreadable blocks on Video DVD

Hi! > > I think that if they are using the normal block layer accesses on the > > DVD device, there may be some retries that occur which are likely > > undesirable in this case since they will just stall playback. If they > > are using SG_IO to feed raw requests into the drive (which I imagine >

Re: Possibly SATA related freeze killed networking and RAID

Hi! > > kernel: [734344.717844] irq 21: nobody cared (try booting with the > > "irqpoll" option) > > kernel: [734344.717866] > > Your machine decided to emit interrupt 21 without an apparent reason. > Whatever caused that made the kernel shut down IRQ 21 at which point the > disk drives on

Re: nohz and strange sleep latencies

Hi! > > > but perhaps somehow we miss this fact and fail to turn off the lapic > > > clockevents drivers? > > > > Ok, I guess I'm lost. If I offline second CPU, I immediately get > > 1000Hz timer tick... is that expected? > > Hmm. No. I have no idea why this is happening. > > 34196 total

Re: Small System Paging Problem - OOM-killer goes nuts

Josh Goldsmith wrote: The problem comes when I try to untar a large file (in this case linux-2.6.23.tar.bz2). Regardless if I kill off every other process, eventually the oom-killer will appear and kill either the tar or the shell. What's the actual command you are executing? - To

[PATCH] scatterlist: add more safeguards

Add more safeguards to protect against misinterpreting a chain entry as a normal scatterlist and vice-versa. * Make sure the entry isn't a chain when assigning and reading a normal sg. * Clear offset and length when chaining. Signed-off-by: Tejun Heo <[EMAIL PROTECTED]> --- While converting

Re: [PATCH] [NET]: Fix TX bug VLAN in VLAN

On Fri, Nov 23, 2007 at 12:12:52PM +, Joonwoo Park wrote: > This patch fixes http://bugzilla.kernel.org/show_bug.cgi?id=8766 > > Is it possible? > BUG((veth->h_vlan_proto != htons(ETH_P_8021Q)) && !(VLAN_DEV_INFO(dev)->flags > & VLAN_FLAG_REORDER_HDR)) > I'm afraid, queued packet before

Re: [PATCH 4/4] atm/ambassador: kmalloc + memset conversion to kzalloc

On Mon, 26 Nov 2007, Joonwoo Park wrote: > 2007/11/26, Robert P. J. Day <[EMAIL PROTECTED]>: > > i realized that. but all you can say is that only amb_init() calls > > setup_dev() *currently*. when you're not looking, someone else might > > (for whatever reason) call setup_dev() from elsewhere,

[PATCH] Extended interrupt LVT support for AMD Barcelona

This patch adds extended interrupt support for AMD Barcelona CPUs. The patch provides functions to setup MCE and IBS interrupt vectors. Compared to the previous K8 implementation the vector offsets are centrally handled now in apic_64.c. Thus, the APIC setup code is responsible for vector

Re: [RFC] Re: nozomi version 2.1d for review

On Montag 26 November 2007 02:28:36, you (Michael Lothian) wrote: > Hi Frank > > I was wondering if you had a git tree somewhere I could pull. Hello Mike, no, unfortunately currently not. From time to time (when i feel enough worthwhile changes came together) i send a new version to Greg who

Re: [PATCH] Keep UML Kconfig in sync with x86

On Mon, Nov 19, 2007 at 02:02:24PM -0500, Jeff Dike wrote: > Fix a 2.6.24-rc3 UML build breakage introduced by commit > 1032c0ba9da5c5b53173ad2dcf8b2a2da78f8b17 - it introduces X86_32, with > many things which UML needs depending on it. > > This patch adds definitions of X86_32 and

Re: [PATCH 4/4] atm/ambassador: kmalloc + memset conversion to kzalloc

2007/11/26, Robert P. J. Day <[EMAIL PROTECTED]>: > i realized that. but all you can say is that only amb_init() calls > setup_dev() *currently*. when you're not looking, someone else might > (for whatever reason) call setup_dev() from elsewhere, and *that* call > might not zero that memory

Re: [PATCH] ehea: Add kdump support

Michael Ellerman wrote on 26.11.2007 09:16:28: > Solutions that might be better: > > a) if there are a finite number of handles and we can predict their > values, just delete them all in the kdump kernel before the driver > loads. Guessing the values does not work, because of the handle

Re: [PATCH 4/4] atm/ambassador: kmalloc + memset conversion to kzalloc

On Mon, 26 Nov 2007, Joonwoo Park wrote: > 2007/11/26, Robert P. J. Day <[EMAIL PROTECTED]>: > > i'm not sure the above is a safe thing to do, as you're zeroing that > > area, then making a function call and assuming, upon entry to the > > function call, that the caller has done the right thing.

Re: [PATCH] [2.6.24-rc3-mm1] loop cleanup in fs/namespace.c - repost

On Wed, Nov 21, 2007 at 03:24:33PM -0800, Andrew Morton wrote: > -repeat: > - if (atomic_dec_and_lock(>mnt_count, _lock)) { > + while (atomic_dec_and_lock(>mnt_count, _lock)) { > if (likely(!mnt->mnt_pinned)) { > spin_unlock(_lock); >

Re: [Patch] mm/sparse.c: Improve the error handling for sparse_add_one_section()

Hi, Cong-san. > ms->section_mem_map |= SECTION_MARKED_PRESENT; > > ret = sparse_init_one_section(ms, section_nr, memmap, usemap); > > out: > pgdat_resize_unlock(pgdat, ); > - if (ret <= 0) > - __kfree_section_memmap(memmap, nr_pages); > + > return ret;

Re: [PATCH 1/4] xfrm_hash: kmalloc + memset conversion to kzalloc

> > i believe the more common standard for the above is: > > else if (hashdist) { > > to reduce the level of overall indentation, no? > No, it was. Because there was a memset in that indentation, but I made it by removing memset. Thanks. Joonwoo - To unsubscribe from this list: send the line

Re: [PATCH 2/4] fib_semantics: kmalloc + memset conversion to kzalloc

fib_semantics: kmalloc + memset conversion to kzalloc fix to avoid memset entirely. Thanks. Joonwoo Signed-off-by: Joonwoo Park <[EMAIL PROTECTED]> --- diff --git a/net/ipv4/fib_semantics.c b/net/ipv4/fib_semantics.c index 1351a26..352f8c4 100644 --- a/net/ipv4/fib_semantics.c +++

RE: [PATCH 1/4] xfrm_hash: kmalloc + memset conversion to kzalloc

2007/11/26, Patrick McHardy <[EMAIL PROTECTED]>: > How about also switching vmalloc/get_free_pages to GFP_ZERO > and getting rid of the memset entirely while you're at it? > xfrm_hash: kmalloc + memset conversion to kzalloc fix to avoid memset entirely. Thanks Patrick. Thanks. Joonwoo

Re: [PATCH 3/4] fib_hash: kmalloc + memset conversion to kzalloc

fib_hash: kmalloc + memset conversion to kzalloc fix to avoid memset entirely. Thanks. Joonwoo Signed-off-by: Joonwoo Park <[EMAIL PROTECTED]> --- diff --git a/net/ipv4/fib_hash.c b/net/ipv4/fib_hash.c index 527a6e0..9d0cee2 100644 --- a/net/ipv4/fib_hash.c +++ b/net/ipv4/fib_hash.c @@ -102,10

Re: [PATCH 4/4] atm/ambassador: kmalloc + memset conversion to kzalloc

2007/11/26, Robert P. J. Day <[EMAIL PROTECTED]>: > i'm not sure the above is a safe thing to do, as you're zeroing that > area, then making a function call and assuming, upon entry to the > function call, that the caller has done the right thing. i don't see > how you can count on that,

Re: [PATCH] zfcp: add some internal zfcp adapter statistics

On Sunday 25 November 2007 12:16, James Bottomley wrote: > > On Wed, 2007-10-31 at 11:33 +0100, Swen Schillig wrote: > > From: Swen Schillig <[EMAIL PROTECTED]> > > > > add some statistics provided by the zFCP adapter to the sysfs > > > > The new zFCP adapter statistics provide a variety of

Re: Possibility to adjust the only-root-can-bind-to-port-under-1024 limit

Radoslaw Szkodzinski (AstralStorm) skrev: In Linux you have to be root in order to listen to TCP or UDP ports below 1024 (the well-known ports). As far as I know, this limit is hardcoded in the kernel. The proper way to enable port <= 1024 binding support is adding CAP_NET_BIND_SERVICE to >

[PATCH] [libata] Return proper ATA INT status in pata_bf54x driver.

INT status can be OR. Signed-off-by: Sonic Zhang <[EMAIL PROTECTED]> --- drivers/ata/pata_bf54x.c |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/ata/pata_bf54x.c b/drivers/ata/pata_bf54x.c index b5e3842..81db405 100644 --- a/drivers/ata/pata_bf54x.c +++

Re: [PATCH 1/2] msi: set 'En' bit of MSI Mapping Capability on HT platform

On Sun, 25 Nov 2007 11:21:48 +0800 "peerchen" <[EMAIL PROTECTED]> wrote: > According to the HyperTransport spec, 'En' indicate if the MSI Mapping is > active. So it should be set when enable the MSI. > Cool, I had a patch that added a quirk to enable MSI Mapping on Broadcom's HT1000 so that

Re: [RFC] Documentation about unaligned memory access

On Nov 23, 2007 1:15 AM, Daniel Drake <[EMAIL PROTECTED]> wrote: [...] > > Before I do so, any comments on the following? > [...] > void myfunc(u8 *data, u32 value) > { > [...] > value = cpu_to_le32(value); > memcpy(data, value,

<    1   2   3   4   5   6   7   8   9   >