Unfortunately when the SD card disappears so do the typical shell commands (as that's the device I'm booting off). I was left having to Ah I see - the stuff in there is correct. Does that mean that brn should Sigh. I think I've seen those posts ( http://thread.gmane.org/gmane.linux.acpi.devel/32779/focus=33442 ? ) and hadn't fully comprehended what you were fighting against. Doesn't this I wish I could say - for some reason every option to download the source code in the dropdown ...

The existing NFSv4 xattr handlers do not accept xattr calls to the security namespace. This patch extends these handlers to accept xattrs from the security namespace in addition to the default NFSv4 ACL namespace. Signed-off-by: Matthew N. Dodd <Matthew.Dodd@sparta.com> Signed-off-by: David P. Quigley <dpquigl@tycho.nsa.gov> --- fs/nfs/nfs4proc.c | 52 ++++++++++++++++++++++++++++++++++++++++---------- security/security.c | 1 + 2 files changed, 42 insertions(+), 11 ...

This patch adds the ability to encode and decode file labels on the server for the purpose of sending them to the client and also to process label change requests from the client. Signed-off-by: Matthew N. Dodd <Matthew.Dodd@sparta.com> Signed-off-by: David P. Quigley <dpquigl@tycho.nsa.gov> --- fs/nfsd/export.c | 3 + fs/nfsd/nfs4proc.c | 25 +++++++++++- fs/nfsd/nfs4xdr.c | 101 ++++++++++++++++++++++++++++++++++++++++++--- fs/nfsd/vfs.c | 22 ...

This patch adds a new recommended attribute named label into the NFSv4 file attribute structure. It also adds several new flags to allow the NFS client and server to determine if this attribute is supported and if it is being sent over the wire. Signed-off-by: Matthew N. Dodd <Matthew.Dodd@sparta.com> Signed-off-by: David P. Quigley <dpquigl@tycho.nsa.gov> --- include/linux/nfs4.h | 2 ++ include/linux/nfs_fs_sb.h | 2 +- include/linux/nfs_xdr.h | 4 ++++ ...

It has been six months since the last time we submitted a patch set to the mailing list for review. In this time we have fixed almost all of the issues that people have had with the last patch set and have added a new feature to allow for process labels to be transported with the RPC request. Below I review each of the issues raised with the last patch set and what was done to fix them. I also list the features present in this patch set and known issues. When reviewing the code please be ...

There currently doesn't exist a labeling type that is adequate for use with labeled NFS. Since NFS doesn't really support xattrs we can't use the use xattr labeling behavior. For this we developed a new labeling type. The native labeling type is used solely by NFS to ensure NFS inodes are labeled at runtime by the NFS code instead of relying on the SELinux security server on the client end. Signed-off-by: Matthew N. Dodd <Matthew.Dodd@sparta.com> Signed-off-by: David P. Quigley ...

Two fields have been added to the nfs_fattr structure to carry the security label and its length. This has raised the need to provide lifecycle management for these values. This patch introduces two macros nfs_fattr_alloc and nfs_fattr_fini which are used to allocate and destroy these fields inside the nfs_fattr structure. These macros do not modify any other components of the structure so nfs_fattr_init still has to be used on these structures. In the event that CONFIG_SECURITY is not set these ...

This patch adds two new text options to to the NFS mount options to specify security labeling. It also sends certain LSM related mount options into the module for handling. Signed-off-by: Matthew N. Dodd <Matthew.Dodd@sparta.com> Signed-off-by: David P. Quigley <dpquigl@tycho.nsa.gov> --- fs/nfs/super.c | 9 +++++++++ include/linux/nfs4_mount.h | 6 +++++- security/selinux/hooks.c | 2 +- 3 files changed, 15 insertions(+), 2 deletions(-) diff --git a/fs/nfs/super.c ...

This patch implements the client transport and handling support for labeled NFS. The patch adds two functions to encode and decode the security label recommended attribute which makes use of the LSM hooks added earlier. It also adds code to grab the label from the file attribute structures and encode the label to be sent back to the server. Signed-off-by: Matthew N. Dodd <Matthew.Dodd@sparta.com> Signed-off-by: David P. Quigley <dpquigl@tycho.nsa.gov> --- fs/nfs/inode.c | 45 ...

Thanks, didn't know it was, from what Michael had told me it was *very rare* that's why I asked Luis --

Hi, the platform I am working on right now (ARM) has a so called 'TCM' (tightly coupled memory) that is some 8 to 32kB of SRAM in the chip, no waitstates, very high bandwidth, and it is possible to access it *while* accessing main memory. It may be a very good thing (for example) to implement a software FIFO to be used in ISRs or such. Do you know of any implementation of such software FIFO or any other kernel driver for TCMs? bye Alessio --

Under what conditions will the clause "(unsigned long)pr->id < 0)" be true, and when will it be false? What will any sane optimizing compiler do? And *sometimes*, the *real* bug is that pr->id should be a signed quantity, not an unsigned one, and the cast is just papering over the issue. In other words, the original line is almost certainly buggy. However, this isn't the right fix. Somebody who actually understands the code will have to decide what *should* be happening here (that's ...

Fix declaration of cgroup_mm_owner_callbacks() The choice of real/dummy declaration for cgroup_mm_owner_callbacks() shouldn't be based on CONFIG_MM_OWNER, but on CONFIG_CGROUPS. Otherwise kernel/exit.c fails to compile when something other than a cgroups controller selects CONFIG_MM_OWNER Signed-off-by: Paul Menage <menage@google.com> --- This is a retry with a mailer that hopefully didn't break the whitespace formatting include/linux/cgroup.h | 15 ++++++--------- 1 file changed, ...

Fix declaration of cgroup_mm_owner_callbacks() The choice of real/dummy declaration for cgroup_mm_owner_callbacks() shouldn't be based on CONFIG_MM_OWNER, but on CONFIG_CGROUPS. Otherwise kernel/exit.c fails to compile when something other than a cgroups controller selects CONFIG_MM_OWNER Signed-off-by: Paul Menage <menage@google.com> --- include/linux/cgroup.h | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) Index: ...

David pointed out that the default sched_clock() fallback is broken in that it wraps too soon. Fix this by using the 64 bit jiffie value so that we're large enough to overflow properly. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> CC: David Howells <dhowells@redhat.com> --- arch/x86/kernel/tsc.c | 6 ++---- kernel/sched_clock.c | 2 +- 2 files changed, 3 insertions(+), 5 deletions(-) Index: ...

Struct members may be marked as private by using /* private: */ before them, as noted in Documentation/kernel-doc-nano-HOWTO.txt: <quote> Inside a struct description, you can use the "private:" and "public:" comment tags. Structure fields that are inside a "private:" area are not listed in the generated output documentation. Example: /** * struct my_struct - short description * @a: first member * @b: second member * * Longer description */ struct my_struct { int a; ...

From: Randy Dunlap <randy.dunlap@oracle.com> Fix kernel-doc to handle structs whose members are all private; otherwise invalid XML is generated: xmlto: input does not validate (status 3) linux-2.6.27-rc6-git4/Documentation/DocBook/debugobjects.xml:146: element variablelist: validity error : Element variablelist content does not follow the DTD, expecting ((title , titleabbrev?)? , varlistentry+), got () Document linux-2.6.27-rc6-git4/Documentation/DocBook/debugobjects.xml does not ...

Trying to build rc6-mmotm0913 dies: CC security/selinux/hooks.o security/selinux/hooks.c: In function =E2=80=98selinux_bprm_committing_cr= eds=E2=80=99: security/selinux/hooks.c:2325: error: =E2=80=98struct task_struct=E2=80= =99 has no member named =E2=80=98it_prof_expires=E2=80=99 make=5B2=5D: *** =5Bsecurity/selinux/hooks.o=5D Error 1 make=5B1=5D: *** =5Bsecurity/selinux=5D Error 2 make: *** =5Bsecurity=5D Error 2 I suspect that itimers-fix-itimer-many-thread-hang.patch has a ...

Trying to build 2.6.27-rc6-mmotm0913 dies a horrid death: CC fs/sysfs/dir.o fs/sysfs/dir.c: In function =E2=80=98sysfs_mv_dir=E2=80=99: fs/sysfs/dir.c:993: error: implicit declaration of function =E2=80=98__sy= sfs_get_dentry=E2=80=99 fs/sysfs/dir.c:993: warning: assignment makes pointer from integer withou= t a cast make=5B2=5D: *** =5Bfs/sysfs/dir.o=5D Error 1 make=5B1=5D: *** =5Bfs/sysfs=5D Error 2 make: *** =5Bfs=5D Error 2 Diagnosis: Andrew added ...

This drives size of tags file from 68.9 MB down to 67.7 MB. Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com> --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/Makefile +++ b/Makefile @@ -1450,7 +1450,7 @@ define find-sources -name $1 -print; \ find $(__srctree) $(RCS_FIND_IGNORE) \ \( -name include -o -name arch -o -name '.tmp_*' \) -prune -o \ - -name $1 -print; \ + -name $1 -print | sed -e 's#^./##'; \ ) ...

I would conclude that the application is severely broken, not the server itself. The scheduler is trying to be fair. Unless you're assigning priorities, it has no way of knowing that those 1000 CPU hog processes are less important than your netcat process. Once those processes have shown to be much longer-running than netcat, the kernel realizes that giving netcat priority is the the best approximation to ideal shortest-time-to-completion-first scheduling, so netcat gets to run ...

[Yinghai Lu - Mon, Sep 15, 2008 at 09:25:14AM -0700] | On Mon, Sep 15, 2008 at 9:22 AM, Cyrill Gorcunov <gorcunov@gmail.com> wrote: | > [Yinghai Lu - Mon, Sep 15, 2008 at 09:12:37AM -0700] | > | On Mon, Sep 15, 2008 at 8:05 AM, Cyrill Gorcunov <gorcunov@gmail.com> wrote: | > | > We should check first if there is ESR register before read/write it. | > | > | > | > Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> | > | > --- | > | > | > | > Please review and test if possible. Thanks. | > | ...

We should check first if there is ESR register before read/write it. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> --- Please review and test if possible. Thanks. Index: linux-2.6.git/arch/x86/kernel/smpboot.c =================================================================== --- linux-2.6.git.orig/arch/x86/kernel/smpboot.c 2008-09-14 21:49:36.000000000 +0400 +++ linux-2.6.git/arch/x86/kernel/smpboot.c 2008-09-15 18:30:37.000000000 +0400 @@ -893,8 +893,10 @@ do_rest: /* * ...

Well, since you ask :-P. Here's an equivalent incantation. I hope it's not too brittle. Don't forget to unmount the SD card first. cd /sys/module/ehci_hcd/drivers/pci:ehci_hcd echo -n 0000:00:1d.7 | sudo tee unbind; echo -n 0000:00:1d.7 | sudo tee bind The magic number is the PCI ID for the USB Host Controller, taken from your error message. If the manual "bind" works you should then see a symlink, "0000:00:1d.7" It might have bitrotted on stock kernels? The newer interface is under ...

Hi, I've found my sound defunct in mmotm 2008-09-13-03-09 (opposing to 2008-09-10-19-39). My debug shows: HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 HDA Intel 0000:00:1b.0: setting latency timer to 64 azx_codec_create (1232): t=0, max=4, def=3, mask=4, probe_mask=ffffffff snd_hda_codec_new A: ffff88007b6988f8 patch_stac927x A: 0 stac92xx_parse_auto_config A stac92xx_parse_auto_config B stac92xx_parse_auto_config E stac92xx_parse_auto_config ...

Hi, After doing # echo 1 > /sys/class/graphics/fb0/blank I got the following in my kernel log: ============================================= [ INFO: possible recursive locking detected ] 2.6.27-rc6-00086-gda63874-dirty #97 --------------------------------------------- echo/1564 is trying to acquire lock: ((fb_notifier_list).rwsem){..--}, at: [<c005a384>] __blocking_notifier_call_chain+0x38/0x6c but task is already holding lock: ((fb_notifier_list).rwsem){..--}, at: [<c005a384>] ...

From: Marco Stornelli <marco.stornelli@gmail.com> Added support for the mem kernel command line option Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com> --- --- setup.c.orig 2008-09-15 11:30:00.000000000 +0200 +++ setup.c 2008-09-15 11:30:17.000000000 +0200 @@ -283,6 +283,25 @@ static int __init early_parse_fbmem(char } early_param("fbmem", early_parse_fbmem); +/* + * Pick out the memory size. We look for mem=size@start, + * where start and size are "size[KkMm]" + ...

From: Marco Stornelli <marco.stornelli@gmail.com> Fixed the type of size and start, now they are resource_size_t. Fixed the double pointer parameter, now it's only a single pointer. Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com> --- --- linux-2.6.26.5/arch/avr32/kernel/setup.c.orig 2008-09-15 11:30:00.000000000 +0200 +++ linux-2.6.26.5/arch/avr32/kernel/setup.c 2008-09-15 11:30:17.000000000 +0200 @@ -283,6 +283,25 @@ static int __init ...

Lots of whitespace damage here. Your first patch looked OK --- ~Randy Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA http://linuxplumbersconf.org/ --

OK, I can see your point here. However, this is a completely different change to my original patch. Would it not make more sense to queue my original patch and then for me to write some patches to move all the Again, this is a good idea but a different change to the patch I wrote originally. So, what I propose is this. Could you please queue my bug fix (I can send the two patches again) and then I will begin working on the generic patches to fix the issues that you've raised in this ...

The previous mail is mangled. So resending the patch. This patch fixes the topology problem in the 2.6.25 kernel. The cores and the packages in the system are not deteced correctly in the kernel due to the problem in the logical cpu to apic id mapping. The problem is solved by assigning the APIC ids from the BIOS APIC table to the cpus. Topology before applying the patch CPU0 attaching sched-domain: domain 0: span 00000003 groups: 00000001 00000002 domain 1: span 000000ff ...

Ok. So the platform driver settings do match those in the BIOS. My guess would be the platform driver is fine and the BIOS screws up. The "HC died" message is interesting. Sounds like the controller for these two USB devices stops working. Maybe try unloading and reloading the ehci module? I don't think I can help any more though. - I CC: the maintainer, maybe Corentin has other reports or ideas - Are any BIOS upgrades available? None of them mention this problem, but the ...

I guess russell crow doesnt have a problem with me(Gladiator), but as soon as jodie foster is the main character(Panic Room); I receieve this: [14417.951134] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK [14417.951150] sr 0:0:0:0: [sr0] Sense Key : Hardware Error [current] [14417.951160] Info fld=0xc1a00 [14417.951163] sr 0:0:0:0: [sr0] Add. Sense: Track following error [14417.951172] end_request: I/O error, dev sr0, sector 3172264 [14417.951181] Buffer I/O ...

Hi all... Since some days ago I have notcied my 64bit cooker box was too slow, for example, to perform an urpmi update. Looking at dmesg/syslog, I have seen an strange message: ata4: EH pending after 5 tries, giving up ata4: EH complete ata3: EH pending after 5 tries, giving up ata3: EH complete ata2: EH complete ata4: EH pending after 5 tries, giving up ata4: EH complete ata3: EH pending after 5 tries, giving up ata3: EH complete It repeats continuously. But there is nothing attached ...

some guys complained that it is even too verbose with KERN_DEBUG YH --

ised; " --- ~Randy Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA http://linuxplumbersconf.org/ --

could be enabled via "boot=verbose" to get more debug info will use it to convert some printk(KERN_DEBUG ...) Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> --- include/linux/kernel.h | 19 +++++++++++++++++++ kernel/printk.c | 21 +++++++++++++++++++++ 2 files changed, 40 insertions(+) Index: linux-2.6/include/linux/kernel.h =================================================================== --- linux-2.6.orig/include/linux/kernel.h +++ ...

I can understand the desire to enable filtering on a subsystem-by-subsystem basis, but I think rather than doing a subsystem-specific hack we should do something that any subsystem can use. Perhaps we could extend the current <level> hack to include a subsystem, something like: <7><x86>Your blort driver seems to be befudged, trying blarfing. ... and something like "loglevel=x86:7,acpi:3,..." -hpa --

WARNING: HACK - HACK - HACK Under the RT kernel (with hardirq preemption) the eHEA driver hangs right after booting. Fiddling with the hardirqs and softirqs priorities allows to run a bit longer but as soon as the network gets under load, the hang returns. After investigating, it appears that the driver is loosing interrupts. To make a long story short, looking at the code, it appears that the XICS maps all its interrupts to level sensitive interrupts (I don't know if it's the reality ...

Hi Thomas, Jan-Bernd, Christoph, Heck, I sure do not want this to be applied mainstream nor into any tree. The sole purpose of this patch was to trigger some reaction from the people who Agreed, but the fact that it fails with hardirq preemption leads me to believe (without any more knowledge about the harware) that there might be something amiss with this driver (or the code concerning the XICS) Nope, this is just a quick hack that allows me to have a functional eHEA under the ...

Hi Linus, Please pull the latest SLAB git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/penberg/slab-2.6.git for-linus The tree contains a small fix for SLUB /proc/slabinfo emulation from Salman Qazi. Pekka Salman Qazi (1): slub: fixed uninitialized counter in struct kmem_cache_node mm/slub.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/mm/slub.c b/mm/slub.c index fb486d5..0c83e6a 100644 --- a/mm/slub.c +++ ...

Hi Andrew, I love CONFIG_DEBUG_MUTEXES. Could you please pick up following patch? ===================================== From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Patch against: mmotm 09/13 Patch name: fix-a-race-condtion-of-oops_in_progress-fix2.patch Applied after: fix-a-race-condtion-of-oops_in_progress-fix.patch if CONFIG_DEBUG_MUTEXES=y, mutex.c makes following build error. because oops_in_progress was changed from int to ...

Thanks. -SK --

Hi, Lots of arch-specific include/ directories were moved to arch/$ARCH/. E.g., arch/arm/include/asm/ contains lots of files and a few sub-directories. --- ~Randy Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA http://linuxplumbersconf.org/ --

From: Chris Snook <csnook@redhat.com> Driver for Atheros L2 10/100 network device. Includes necessary changes for Kconfig, Makefile, and pci_ids.h. Sighed-off-by: Chris Snook <csnook@redhat.com> Signed-off-by: Jay Cliburn <jacliburn@bellsouth.net> --- If this file is too large for vger, the full patch may be obtained from ftp://ftp.hogchain.net/pub/linux/attansic/atlx/0001-atl2-add-atl2-driver.patch drivers/net/Kconfig | 11 + drivers/net/Makefile | 1 + ...

Doesn't make sense to do an FTRACE startup test when FTRACE isn't even being compiled in. Signed-off-by: Steven Noonan <steven@uplinklabs.net> --- kernel/trace/Kconfig | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index 16e5bb5..1ee0400 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig @@ -152,6 +152,7 @@ config FTRACE_SELFTEST config FTRACE_STARTUP_TEST bool "Perform a startup test on ftrace" depends ...

From: "Bosko Radivojevic" <bosko.radivojevic@gmail.com> Date: Mon, 15 Sep 2008 00:49:15 +0200 netdev@vger.kernel.org is where networking developers are, added to the CC: Also, most of us are at the kernel summit and the plumbers conference over the next few days, so don't expect any response of substance for at least a week. Likely it will take longer, --

Hmm, undelete done right. Just one question... how slow/fast is it compared to conventional filesystems (ext3?)? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html --

Hi! After my first submission, Szabolcs Szakacsits showed benchmark results using compilebench. On Thu, 21 Aug 2008 00:25:55 +0300 (MET DST) Accordint to his measurement, NILFS2 showed a very low performance on the first measument, and it recovered after a while. I still don't know the reason why NILFS2 shows such behaviour, and I'm thinking to follow the benchmark. A little while ago, I tried another benchmark on the kernel 2.6.27-rc6. The iozone benchmark. The result was as ...

The fix is in: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=62a877... if you still see problems please give me the exact mount / remount commands that cause you problems. --

Yes, with 2.6.26 it mounts fine. According to that earlier message on the list, this is a regression introduced in either 2.6.27-rc2 or 2.6.27-rc3. -- Frederik Himpe --

[Ingo Molnar - Mon, Sep 15, 2008 at 09:56:55AM +0200] | | * Cyrill Gorcunov <gorcunov@gmail.com> wrote: | | > We should check if we have ESR register before writting to it. | > | > Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> | > --- | > | > Please review! | > it seems the same nit in do_boot_cpu - checking now. | > | > Index: linux-2.6.git/arch/x86/kernel/smpboot.c | > =================================================================== | > --- ...

[Cyrill Gorcunov - Mon, Sep 15, 2008 at 02:01:19PM +0400] | [Ingo Molnar - Mon, Sep 15, 2008 at 09:56:55AM +0200] | | | | * Cyrill Gorcunov <gorcunov@gmail.com> wrote: | | | | > We should check if we have ESR register before writting to it. | | > | | > Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> | | > --- | | > | | > Please review! | | > it seems the same nit in do_boot_cpu - checking now. | | > | | > Index: linux-2.6.git/arch/x86/kernel/smpboot.c | | > ...

Up to Frank and Roland, but I think we can make the cleanups incrementally, on top of this patch. Oleg. --

ok. I'd prefer incremental, as the current stuff seems stable in practice. Ingo --

Yes, the existing code doesn't seem quite right - if !CONFIG_MM_OWNER then we don't need to even define a trivial version of cgroup_mm_owner_callbacks() But your patch is too specific - tying the existance of cgroup_mm_owner_callbacks() to the memory controller would break other controllers (e.g. the memrlimit or swap controllers, which also want to use it) How about: - any cgroup that needs mm-owner callbacks selects an option CGROUP_MM_OWNER_CALLBACK - CGROUP_MM_OWNER_CALLBACK ...

On Mon, 15 Sep 2008 13:32:26 +0200 As far as I can see it's ok, but if not I obviously like to hear about having a second check is actually not a bad thing per se; in terms of programming pattern, doing the quick checks before the lock, but doing the final check inside the lock makes sense to me. If there's real objections to doing the match the second time (it's cheap!) I'll remove it, but this way, you can call the "heavy" function always and from anywhere, and it'll just do the right thing ...

On Mon, 15 Sep 2008 07:06:44 -0700, I don't see any problem on the s390 busses, and pci and usb look OK as OK, you have a point. I just find it a bit ugly; especially as the ->probe function will check if the device matches as well (by poking at the device). But I'd be fine with either way :) --

applied --

applied --

This needs to check for drive->scsi or the subtle bugs will happen. Also why not use dev_is_idecd() static inline function instead? --

If you move info->last_block to ide_drive_t it is possible to factor out xferlen setup from ide_cd_do_request() to a separate handler and move it here. Then xferlen argument to ide_issue_pc() won't be necessary. How's about it? --

OK, that's fair enough. But, can we document it as such? "Only headers and things of known, static sizes can go in here. We don't use Yes, it does mean that there is a bug because someone either made a structure bigger, PAGE_SIZE smaller, or a call path got deeper than we expected. I'm just having visions of the email hitting my inbox in 18 months. :) The structures are sized consistently across all architectures and configurations. However, PAGE_SIZE and the size of that buffer are ...

This one has been bugging me a bit. This adds one net line of code and I think it's much easier to read: { struct cr_hdr h; int ret; ret = cr_read_obj(ctx, &h, buf, n); if (ret) return ret; ret = -EINVAL; if (h.type == type) ret = h.parent; return ret; } -- Dave --

All of the casting here is unnecessary. 'void *' behaves like 'char *' when you do arithmetic on it. I really do detest having a memory allocator BUG_ON() when it runs out of space. -- Dave --

This feels a litlte weird, since the ctx->crid actually was calculated in ctx_alloc() in sys_checkpoint(). I'd almost prefer do_checkpoint() return 0 on success. If h->len > n should we return -ENOSPC so the caller can theoretically Here I am getting confused about return values. cr_read_obj() says it returns size of payload. cr_read_obj_type() says it returns "object reference of the parent object", though if cr_read_obj() returned non-zero then it returns its return value, which ...

Could you explain why you're not using the slab here? -- Dave --

--

Andy, you are straight into it, at the point. Don't believe any other, or say it was me, giving you a bad hint. Hermann --

Julian First let me acknowledge jusst technologies contribution. It seems This is where you misrepresent my words: "I can't help but think..." is phrase that doesn't not imply certainty but indicates my *perception*. I did not assert this as fact, as the following statement started "If so, ..." which is a conditional clause. No. It was my ill researched, emotive response to Manu attacking My point was to suggest to Manu that there were more productive ways to further his cause ...

Because users should not be forced to wait 3 months for fixes, for admittedly serious bugs, which are ready for them right now. Small, self-contained, tested, obvious fixes. There is just something horribly wrong if you are not taking two-line fixes for memory corruption, even if the problem existed since kernel 1.2.13. July 13: 2.6.26 released, merge window opens July 29: 2.6.27-rc1 released, merge window closes Sept 20? 2.6.27 release (wild guess) Dec 25? 2.6.28 release (wild ...

From: Jeff Garzik <jeff@garzik.org> It adds more credence to the bug. Because it's usually reported I don't take that away from what I said. Why is it so important to fix something "RIGHT NOW" that has existed forever? Where were these fixes during the He wants the time outside of the merge window to work on fixing regressions and exploitable problems. This is so that the process And it's getting submitted now, because?!? Again, it's been there for quite some time, why is it ...

From: Jeff Garzik <jeff@garzik.org> Which of these have regression and/or bugzilla entries? This is too much and I want to see it trimmed down. Thanks. --

From: Jeff Garzik <jeff@garzik.org> I'll take another look at the queue and try to give you some more specific feedback. I can think of about 3 or 4 entries on the posted regression list that might be appropriate, so I essentially expected to see that many commits, give or take one or two. --

From: Jeff Garzik <jeff@garzik.org> I personally partly agree with you, but Linus put his foot down and I'm implementing the stated policy by doing the same. --

He continues to take non-regression fixes and minor cosmetic commits from other trees. The basic idea is to BALANCE the lateness of -rc with the seriousness of the problem being fixed, and the technical complexity of the fix itself. The later the -rc, the more you need to take into account how likely it is to create additional problems. But did you READ the patches and extended commit descriptions, to see if additional problems were likely? Late -rc does not mean "no bug fixes at all ...

My impression was that Linus was in Wrath of God(tm) mode <grin> and he was reacting strongly for effect not being specific. Well, obscure subsystems like PCI PCI: Fix printk warnings in setup-bus.c PCI: Fix printk warnings in probe.c or libata sata_inic162x: enable LED blinking ata: duplicate variable sparse warning or ia64 (this is not a regression, but a regular bug) ia64: fix panic during `modprobe -r xpc' or bugs that have existed for a long ...

From: David Miller <davem@davemloft.net> Thomas Bogendoerfer (1): tulip: Fix dead 21041 ethernet after ifconfig down Not a regression, that problem has been there forever. Adrian Bunk (1): [netdrvr/usb] hso_create_bulk_serial_device(): fix a double free This is a new driver in 2.6.27, so OK. Andrew Morton (1): drivers/net/mlx4/alloc.c needs mm.h Build bustage, so ok. Breno Leitao (1): s2io: Fix enabling VLAN tag stripping at driver ...

Ops, you are right, pfn is not in bytes ;) The patch works. -- Roberto De Ioris http://unbit.it JID: roberto@jabber.unbit.it --

Have you example output anywhere? --

On Mon, 15 Sep 2008 13:59:49 +0100 eh sure http://www.fenrus.org/before.svg http://www.fenrus.org/after.svg (before and after another patch ;-) -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org --

It's not clear that "ordinary users" ever have this problem. It seems to happen *only* when using a drive which has something which looks like a partition table but isn't, or is a defective partition table, or will only work when diddling with HPA magic. And should some naive user be trying to use such a drive, it seems better to tell them, to beat them over the head with the problem, because if you hide the problem those users are least likely to be able to recover when problems ...

Ack, that [attached] patch fixes the build. --- ~Randy Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA http://linuxplumbersconf.org/ --

Hi Adrian, Sorry. Here it is again. Cheers, Hannes -- Dr. Hannes Reinecke zSeries & Storage hare@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N

Naming is a private matter for udev anyway, independant of numbering for major/minor --

From: Alan Cox <alan@lxorguk.ukuu.org.uk> True. But I think there is some merit in having such a generic allocator for the current users of the ttySX minor space. --

ath9k has been recently introduced (i.e. it's new to 2.6.27). So I'm not certain how to answer. Correct me if I'm wrong but a regression is a new bug for a specific component that did not surface in the previous release, correct? But if the component didn't exist in the previous version, is it still a regression? - Steven --

Looks like a similar issue was raised sometime back. -- Regards, Ankita Garg (ankita@in.ibm.com) Linux Technology Center IBM India Systems & Technology Labs, Bangalore, India --

I've closed the bug. Thanks, Rafael --

Turns off all netfilter options except tables, etc. Since 2.6.22.19-cfs-v24.1 and 2.6.23.17-cfs-v24.1 schedulers are identical, and these are essentially identical with 2.6.24.7, what I read from numbers below is that cfs in 2.6.23 was somewhat less than wonderful for either netperf or tbench, Something happened somewhere other than the scheduler at 23->24 which cost us some performance, and another something happened at 26->27. I'll likely go looking again.. and likely regret it again ...

Well, it seems no one else is testing selinux ... --

Well, they are actually used in sched.h, in the inline routines account_group_user_time() and friends, which are in turn used by routines in sched.c. The point here is that the thread_group_cputime_account_xxx() routines are defined differently depending upon whether we're building for UP or SMP and the Agreed, but Roland and I were trying to make life easier for folks who have to maintain SMP and UP versions of this stuff, keeping it all in one place rather than scattering it about. If ...

The common part of all logs is that some code calls lock_kernel() to acquire The BKL is never released by __blkdev_put(), as the IPI initiated by smp_call_function_single() never seems to finish. So it keeps on spinning in csd_flag_wait(). Adding debug code to the PS3-specific IPI message_pass() routine ps3_smp_message_pass() seems to cause the problem to go away. I have lockdep enabled (as most other locking debug stuff), but CONFIG_PREEMPT is not set. As Bob McGwier sees it on ...

yes. your patch fixed the skip... Acked-by: Yinghai Lu <yhlu.kernel@gmail.com> YH --

Depends on what you are doing and what features you care about. You To be clear, the submission of AXFS has nothing at all to do with squashfs. It's not a || it's an && operation. But yeah, Christoph is right. 2.6.28 is iffy for AXFS anyway. --

There's nothing stopping you having several different configs for the same arch that don't produce all the required firmware either. I think the right answer if you're building lots of different kernels for different machines in testing is probably to build a linux-firmware-image that has everything in it, so that you don't have to worry about upgrading it most of the time. (Technically you could make the firmware image indicate which firmware it provides, but I think that gets overly ...

The relevant 9 changes are from: 7c1e76897492d92b6a1c2d6892494d39ded9680c to 72d43d9bc9210d24d09202eaf219eac09e17b339 Thanks, tglx --

I did cg-seek 7c1e76897492d92b6a1c2d6892494d39ded9680c cg-seek here, and problem is back. Good. I can get the /proc/timer_list ;-)... attached. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

This wake_up_all() has to go outside the if clause. I'll change this the next time round to be called right after drive->sleep has been set. The two nested if clauses will be unified and the conditions &&'ed. Regards, Elias --

Here's some data to support my claims. The first experiment consists of sending UDP packets on a dummy network interface. No interrupts are generated, so there should be no soft IRQs. Nevertheless, /proc/stat shows that a considerable share of CPU time is taken by soft IRQs: CPU %user %nice %sys %iowait %irq %soft %steal %guest %idle 0 4.52 0.00 67.84 0.00 0.00 27.64 0.00 0.00 0.00 0 4.00 0.00 70.00 0.00 0.00 26.00 0.00 ...

I searched through the archives and couldn't find a bug report that this patch may be the fix to. However, I understand that the initial leader -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab --

I'd hope to get around to some testing myself much earlier in the weekend, but alas... Did just mix in a quick peed at lirc_i2c though: ... lirc_dev: IR Remote Control driver registered, major 247 bttv: driver version 0.9.17 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture cx88/0: cx2388x v4l2 driver version 0.0.6 loaded lirc_i2c: chip 0x10020 found @ 0x18 (Hauppauge IR) lirc_dev: lirc_register_driver: sample_rate: 10 No register_chrdev failure reported, everything ...

.. Bruno, please also post the output from these commands: hdparm --Istdout /dev/sda smartctl -data -a /dev/sda .. Tejun, are we *sure* that's really a timeout? The status shows 0x40 "drive ready" there, aka. "command complete". I have a client who is also seeing this exact scenario on 750GB drives, using a patched SLES10 kernel (2.6.16 + libata from 2.6.18 or so). Smartctl output is clean (no logged errors), and the drives themselves are fine after a reboot -- necessary ...

Hello, Yeap, I was talking only about the text. Not wrapping outputs and Whee... That's unusally high realloc count but I'm not sure whether it indicates actual problem or it's just the drive's way of saying I'm Hmmm.. Do you happen to have drives of the same model? If so, can you please check what other drives are reporting? Thanks. -- tejun --

I didn't know this history. Thank you. Lai --

Hi, The only pertinent change is that I've added even more documentation to thinkpad_ec.c, explaining how we're just following the published H8S specs (plus some workarounds for experimentally observed bugs). As noted before, I'd be more than happy to assign away copyrights or discuss things further in private if this would help. Shem --

Aieee... didn't know that and was wondering why the hell this wasn't Shem Multinymous, I suppose nothing really has changd since the last time? Thanks. -- tejun --

It all really depends on what you're prioritizing. If your priority is speed and low RAM usage, you'd want to go with gzip. If your priority is low disk usage (for instance, if you're a kernel developer with dozens of kernels on /boot) and speed/RAM usage are less important, LZMA is a good choice. It's just a matter of priority in non-embedded machines. And in embedded machines, you just need to be -really- careful about the RAM usage. LZMA is pretty flexible, though, so you can customize the ...

[...] Apologies if I'm sidetracking the discussion, but I'd like to coin a remark. For kernel/ramfsimage etc the best choice is the one that has the fastest decompression (info on tukaani.org says gzip). Rationale: as it uncompresses faster the system will boot faster. Of course this only holds if the background memory can hold that image. For disk based systems, I assume this is not a problem at all, but for embedded systems with all software in flash a higher compression ration (e.g. ...

What exactly does that mean? Is there any point in fixing this particular bug for 2.6.28 or will the whole cmd-filter infrastructure have to be modified in a more general way in order to address other As far as I can make out, nothing has happened yet at this front. I've just verified that reverting the following commits (in that order) seems to be working nicely for me: 2dc75d3c3b4 bb23b431db7 a4a778971b9 4beab5c623f 14e507b852e abf54393704 06a452e5b95 2b272d4f795 0b07de85a76 Is ...

Right, so it really is only the sysfs interface of the command filter that causes problems, is it? Does that also mean that you are not unhappy with the command filter in linux-next either except for the sysfs interfae? I didn't realise that, sorry for the noise. Regards, Elias --

Does dmesg show anything when you run ifup? --

Hm, no, that should just be a call to kobject_put() instead of kobject_del(), can you try that instead and see if that solves the issue (am at a conference and can't test that at the moment, sorry.) thanks, greg k-h --

And that's about it (well, it also tears down the sysfs stuff.) If you call kobject_put() instead, and it's the last put, it will also call kobject_del() and do everything else that it needs to do. Try it and let me know if I'm right or not :) thanks, greg k-h --

Hi Steven and others, first a minor bug: it seems the units of /debug/tracing/trace_entries is different for read and write. This is confusing for the users, since I can't say "if you have problems, double it". If I read from it something like 16422, then write back 16422, next I read 214. I can't recall the exact numbers, but the difference really is two orders of magnitude. I have 1 GB RAM in this box, so that shouldn't be an issue. My other problem is with trace_pipe. It is again making ...

Yes. The only nastiness is around drivers/ide - there it gets a bunch of annoying conflicts from the ide-{disk,floppy}_ioctl.c splitoff. Other than that, it's trivially ported on top of current linux-next. Merge order is going to be interesting - depending on whether block merge happens before or after ide one. I'm going to put linux-next-based series on kernel.org tonight, before going to Portland... --

Well the first read takes 100ns (plus the other chipset overhead 300ns) but other reads in a page are only an extra 25ns each. So your benefit is not from having the entire executable in cache it's from having the next 7 instructions in the cacheline for only an extra 25ns Usually these things can be fixed in the bootloader or by hacking the kernel to tweak the relevant chipset registers. --

Yes, looking at the Spansion datasheet, if it were interfaced properly it should be quite fast. (25ns access time for in-page 16-bit reads, 100ns for random reads). I'll see if ioremap_cached() makes a difference to streaming read performance. The BSP suppliers have been quite cautious in places, flushing cache a bit too often. (I'm not surprised - we had disk ext3 filesystem Thanks. Oh, how I look forward to the day of working with current kernels and current hardware. -- ...

Update: The BOF will now be at the Aura Lounge at 20:30 (i.e. after dinner but before people have too much to drink ...). We also have Chris Mason as the 11th nominee. The elections for five of the ten members of the Linux Foundation Technical Advisory Board[TAB] are held every year, currently the election will be at the 2008 Kernel Summit in a BOF session. This year, in order to allow for wider participation, we thought we'd try holding the BOF during the Plumbers Conf Aura Lounge event at ...

Since the positions aren't due to be presented until then, it wouldn't be entirely fair. Of course, we can't prevent you from bribing an attendee who wasn't going to attend to be your proxy. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." --

Well, it doesn't change behavior and I think having ->clear_irq method independent from the transfer mode is a preffered approach. Thanks, Bart --

From: Jan Hudec <bulb@ucw.cz> That's not the case I'm running into. The initial GIT execution works, it's when GIT forks up sub processes and tries to execute other things that problem show up. I added tracing and on the ssh remote system, and my PATH had the GIT exec dir in my path when the problem triggers. --

According to the documentation gpio_free should only be called from task context only. To make this more explicit add a might sleep to all implementations. This patch changes the gpio_free implementations for the blackfin architecture. Signed-off-by: Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de> Cc: David Brownell <david-b@pacbell.net> Cc: Bryan Wu <cooloney@kernel.org Cc: uclinux-dist-devel@blackfin.uclinux.org Cc: Guennadi Liakhovetski <g.liakhovetski@pengutronix.de> Cc: Greg ...

Acked-by: David Brownell <dbrownell@users.sourceforge.net> Not dependent on anything else, FWIW (and Kevin already sent the DaVinci patch for review) ... so IMO this is ready to merge as soon as Russell agrees. Consider this also an ack for the MIPS, Blackfin, and x86 arch-specific updates. (Which are likewise ripe for merge.) --

According to the documentation gpio_free should only be called from task context only. To make this more explicit add a might sleep to all implementations. This patch changes the gpio_free implementations for the mips architecture. Signed-off-by: Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de> Cc: David Brownell <david-b@pacbell.net> Cc: Ralf Baechle <ralf@linux-mips.org> Cc: linux-mips@linux-mips.org Cc: Guennadi Liakhovetski <g.liakhovetski@pengutronix.de> Cc: Greg KH ...

Dear Penguins, Let me start of by saying my particular hardware must be buggy in some way. When I issue a sysrq (Ctrl A+ F from minicom) I get a lot of sysrq triggers. I have worked around the problem and I think this workaround is a viable patch even for platforms which do not exhibit this peculiar behavior. upon getting numerous interrupts which request sysrq the function uart_handle_break in include/linux/serial_core.h is hit multiple times. The current code which looks like ...