The STV0367 is a multi-standard demodulator which is capable of processing DVB-T as well as DVB-C signals. It is fully compliant with DVB-T and DVB-C recommendations for broadcast services. Signed-off-by: Igor M. Liplianin <liplianin@netup.ru> --- drivers/media/dvb/frontends/Kconfig | 7 + drivers/media/dvb/frontends/Makefile | 1 + drivers/media/dvb/frontends/stv0367.c | 3399 ++++++++++++++++++++++++++ drivers/media/dvb/frontends/stv0367.h | 62 + ...

Hi Linus, Second x86/uv batch, as promised. The following changes since commit 2be1f3a73dd02e38e181cf5abacb3d45a6a2d6b8: Merge branch 'for-linus' of git://git390.marist.edu/pub/scm/linux-2.6 (2010-08-13 10:54:04 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-uv-for-linus Cliff Wickman (3): x86, UV: Make kdump avoid stack dumps x86, UV: Initialize BAU hub map x86, UV: Make kdump avoid stack ...

2.6.27-stable review patch. If anyone has any objections, please let us know. ------------------ From: Linus Torvalds <torvalds@linux-foundation.org> commit 320b2b8de12698082609ebbc1a17165727f4c893 upstream. This is a rather minimally invasive patch to solve the problem of the user stack growing into a memory mapped area below it. Whenever we fill the first page of the stack segment, expand the segment down by one page. Now, admittedly some odd application might _want_ the stack to ...

Odd, it should be there. Here it is, attached below. It's small enough to send out this way. thanks, greg k-h

I will try it, Greg. If you want specific tests, do not hesitate to tell me which ones. Willy --

Hi Greg, I scraped the patches out of the messages and edited Makefile :) Machine is running, but there's a lot of these in the dmesg: WARNING: at include/linux/security.h:1826 acct_stack_growth+0xe7/0xf0() Modules linked in: Pid: 320, comm: khelper Not tainted 2.6.27.52-rc1a #57 [<c011b54f>] warn_on_slowpath+0x5f/0x90 [<c0145a53>] __alloc_pages_internal+0x93/0x420 [<c01456bd>] buffered_rmqueue+0x11d/0x210 [<c015e09a>] allocate_slab+0x4a/0xd0 [<c015e149>] setup_object+0x29/0x30 ...

I'm announcing the release of the 2.6.34.4 kernel. All users of the 2.6.34 kernel series must upgrade. Actually, you should switch to the .35 kernel releases, as there is only going to be one more .34-stable kernel release after this one. The updated 2.6.34.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.34.y.git and can be browsed at the normal kernel.org git web browser: ...

I'm announcing the release of the 2.6.32.19 kernel. All users of the 2.6.32 kernel series must upgrade. The updated 2.6.32.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.32.y.git and can be browsed at the normal kernel.org git web browser: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=summary thanks, greg k-h ------------ Makefile | 2 arch/arm/Kconfig ...

I'm announcing the release of the 2.6.27.51 kernel. All users of the 2.6.27 kernel series are very strongly encouraged to upgrade. The updated 2.6.27.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.27.y.git and can be browsed at the normal kernel.org git web browser: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.27.y.git;a=summary thanks, greg k-h ------------ Makefile | 2 - ...

I'm announcing the release of the 2.6.35.2 kernel. All users of the 2.6.35 kernel series must upgrade. I'm tired of people trying to parse my words like I'm the Federal Reserve Chairman, just go update already. If you use a kernel.org-based kernel, and you aren't updating to the latest -stable updates, well, why are you using a kernel.org kernel in the first place? The updated 2.6.35.y git tree can be found at: ...

Hi Linus, No other late-breaking bug reports/regressions have turned up, and since I want to get this fixed before -rc1 gets released, please pull: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus I fixed the compile warning basically as you suggested, but with a better name and with the comments moved to the inline function where they would make more sense. Thanks, - Ted Theodore Ts'o (1): ext4: clean up compiler warning in ...

Ingo, I had this sitting in my quilt queue, and did not realize I never committed it. This is on top of my previous two pull requests. Thanks, -- Steve Please pull the latest tip/perf/urgent-3 tree, which can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git tip/perf/urgent-3 Marcin Slusarz (1): tracing: Sanitize value returned from write(trace_marker, "...", len) ---- kernel/trace/trace.c | 11 ++++++++--- 1 files changed, 8 ...

--- On Fri, 8/13/10, Alan Stern <stern@rowland.harvard.edu> wrote: Agreed, and that's what I had asked for. I didn't see code faking up a serial ... did I miss such? If so, let's see a new patch with no faking. --

We use a dynamically allocated kfifo in the dma example, so we need to free it when unloading the module. Signed-off-by: Andrea Righi <arighi@develer.com> --- samples/kfifo/dma-example.c | 4 +--- 1 files changed, 1 insertions(+), 3 deletions(-) diff --git a/samples/kfifo/dma-example.c b/samples/kfifo/dma-example.c index 03433ca..3682278 100644 --- a/samples/kfifo/dma-example.c +++ b/samples/kfifo/dma-example.c @@ -105,9 +105,7 @@ static int __init example_init(void) static void ...

The scatterlist is used uninitialized in kfifo_dma_in_prepare(). This triggers the following bug if CONFIG_DEBUG_SG=y: ------------[ cut here ]------------ kernel BUG at include/linux/scatterlist.h:65! invalid opcode: 0000 [#1] PREEMPT SMP ... Call Trace: [<ffffffff810a1eab>] setup_sgl+0x6b/0xe0 [<ffffffffa03d7000>] ? example_init+0x0/0x265 [dma_example] [<ffffffff810a2021>] __kfifo_dma_in_prepare+0x21/0x30 [<ffffffffa03d7124>] example_init+0x124/0x265 [dma_example] ...

The scatterlist is used uninitialized in kfifo_dma_in_prepare(). This triggers the following bug if CONFIG_DEBUG_SG=y: ------------[ cut here ]------------ kernel BUG at include/linux/scatterlist.h:65! invalid opcode: 0000 [#1] PREEMPT SMP ... Call Trace: [<ffffffff810a1eab>] setup_sgl+0x6b/0xe0 [<ffffffffa03d7000>] ? example_init+0x0/0x265 [dma_example] [<ffffffff810a2021>] __kfifo_dma_in_prepare+0x21/0x30 [<ffffffffa03d7124>] example_init+0x124/0x265 [dma_example] ...

Currently sched_avg_update() (which updates rt_avg stats in the rq) is getting called from scale_rt_power() (in the load balance context) which doesn't take rq->lock. Fix it by moving the sched_avg_update() to more appropriate update_cpu_load() where the CFS load gets updated aswell. Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com> --- kernel/sched.c | 3 ++- kernel/sched_fair.c | 2 -- 2 files changed, 2 insertions(+), 3 deletions(-) Index: ...

TSC's get reset after suspend/resume and this leads to a scenario of rq->clock (sched_clock_cpu()) less than rq->age_stamp. This leads to a big value returned by scale_rt_power() and the resulting big group power set by the update_group_power() is causing improper load balancing between busy and idle cpu's after suspend/resume. This resulted in multi-threaded workloads (like kernel-compilation) go slower after suspend/resume cycle on core i5 laptops. Realign rq->age_stamp to rq->clock and ...

This problem took a while to track down, but it should be fixed in the commit below. Which linus merged today from the x86-urgent branch. Thank you for the excellent bug report, and my apologies for missing this the first time around. Can you please verify the commit below fixes your problem? Thanks, Eric commit 5989cd6a1cbf86587edcc856791f960978087311 Author: Eric W. Biederman <ebiederm@xmission.com> Date: Wed Aug 4 13:30:27 2010 -0700 x86, apic: Map the local apic when ...

There is a hack in the code someplace on ia64 to pass the virtual address efi was mapped at to the next kernel, and have the kernel make certain to use efi there, without calling set_virtual_address_map(). For similar kernels that is fine at some point I expect kernel divergence will make that scheme unworkable. Essentially this is the same as using physical addresses but starting with the virtual addresses. For ia64 I seem to recall some weird floating point fixup routines that benefited ...

Any hope to get a followon patch for i386 as well? That would make it largely a no-brainer. Tony, does this affect ia64 in any way? -hpa --

Another aspect of this... this plays well into the already-outstanding proposal to keep an identity-mapped set of page tables around at all times. Right now we do it ad hoc for 64 bits and not really for 32 bits, but that is being changed, see the thread starting at: http://marc.info/?i=1280940316-7966-1-git-send-email-bp@amd64.org This would definitely be better than keeping yet another private page table. -hpa --

If Eric's recollection about the "weird floating point fixup routines"[1] performance issues are correct - then ia64 won't want to do this. -Tony [1] more usually called FPSWA - floating point software assist - which handle a bunch or corner cases in denormalized floating point values that the h/w doesn't cover. --

The kfifo DMA sample driver is broken. It does not properly initialize the scatterlist, and therefore causes a kernel BUG with CONFIG_DEBUG_SG=y. Signed-off-by: Ira W. Snyder <iws@ovro.caltech.edu> --- samples/kfifo/dma-example.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/samples/kfifo/dma-example.c b/samples/kfifo/dma-example.c index b9482c2..baa5060 100644 --- a/samples/kfifo/dma-example.c +++ b/samples/kfifo/dma-example.c @@ -45,6 +45,9 @@ static int ...

From: Thomas Habets <thomas@habets.pp.se> If you didn't get an answer on netdev, sending your query again to linux-kernel isn't going to help. Networking experts generally do not read this list. Nobody has simply had an opportunity to look into your problem yet, that is all. I personally have it saved in my inbox and plan to look at it when I get a chance unless someone else gets to it first. --

For concreteness, let me start with the patch I have in mind. Call it "patch version 1". --- linux-2.6.32.13-0.4/kernel/time.c.orig 2010-08-13 10:52:50.000000000 -0700 +++ linux-2.6.32.13-0.4/kernel/time.c 2010-08-13 10:53:20.000000000 -0700 @@ -229,7 +229,7 @@ SYSCALL_DEFINE1(adjtimex, struct timex _ */ struct timespec current_fs_time(struct super_block *sb) { - struct timespec now = current_kernel_time(); + struct timespec now = getnstimeofday(); return ...

I'm not judging the idea as good/bad, just providing information for If you can show this does not affect performance in benchmarks, etc, I'm sure it will be easier to push the patch. As outside of performance, I don't think there's much of an issue with the change. So other then "show some numbers", my only thought that might make the patch more attractive is that rather than a global change, or a static CONFIG_ option, would it maybe make more sense as a mount ...

On Fri, Aug 13, 2010 at 11:25 AM, Patrick J. LoPresti Your stats are off here. The only fast clocksource on x86 is the TSC, and its busted on many, many systems. The cpu vendors have only recently taken it seriously and resolved the majority of problems (however, issues still remain on large numa systems, but its much better then the story was 3-7 years ago). On those TSC broken systems that use the hpet or acpi_pm, a getnstimeofday call can take 0.5-1.3us, so the penalty can be ...

It seems one of these commits in 8357422d4bf33bc2c35884d4016c3fc9efbbc1d2 is causing LVM2 (LVM2.2.02.72) to fail. Previously good logical volumes cannot be mounted anymore, and new one cannot be created. All failed with the error ... "device-mapper: version ioctl failed: Inappropriate ioctl for device" Is there a new LVM2 for this new dm ioctl or the dm is not right? Thanks, Jeff. --

Hello Hirofumi, I would like to export this symbol from the vfat code and add this patch to the Linux kernel. You are listed as the MAINTAINER for FAT and VFAT. As such, I need your approval to do it. The reason that I need to export this symbol is to allow for file based DMA in which the file needs to be pre-allocated. The pre-allocated block addresses are passed to a DMA engine which then directly transfers the data to non-volatile storage. Please let me know if you have any objections to ...

Wait, _I_ have an objection to exporting this symbol. I really don't think it is needed at this point in time, as we really need to figure out exactly what your driver is doing to want to need to call this function. So please, let's not export it for now, when we get to the point that we all agree that this driver is doing the "correct" thing, then we can export the symbol, ok? thanks, greg k-h --

Usually it takes a lot longer. West Bridge can do MTP transfers at the performance of the storage device. Thanks, I have seen this as well. This is not a driver though, it is an MTP protocol stack. This is similar to the applications I have worked with. The driver is not attempting to replace either the protocol stack or the use of gadgetfs. All that it is providing is a gadget peripheral controller driver (that can be used with gadgetfs) along with the ability to perform pre-allocation and allow ...

I think you misunderstand, the driver is not looking into the file system layout. The driver is requesting that the file system allocate a file and tell it where it allocated it to. This is the reason for the I am not sure I understand the question. The point of making the call into the filesytem rather than reading sectors and "looking into the file system layout" is to make sure that the filesystem is the arbiter of all storage requests. How would someone change the layout underneath That is a ...

Also, why do this at the FAT level, and not more correctly at the block layer level? What happens if this isn't a FAT partition on the device? thanks, greg k-h --

OK, I am trying to answer all questions on this topic that I am getting, Sure, I think that the driver is doing the correct thing, but that is mostly because I have not found another way to solve this issue. If The short answer is that the block level does not have the file system awareness needed to determine where a file should be stored on the NVM device. The longer answer is to consider the case of an MTP host, which operates at the file level. It sends the mobile (Linux) device ...

Hi, Did patch #7 make it to any mailing lists? I didn't receive it. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** --

Hi, The rados block device (rbd) implements a network block device backed by the Ceph distributed object store (think nbd/iSCSI, but distributed and fault tolerant). At the suggestion of Christoph and James, this version of the patchset factors out the common Ceph bits (the network protocol, cluster membership, and object storage parts) into a libceph module (currently in net/ceph/ and include/linux/ceph/) that is shared by the file system component (fs/ceph) and rbd ...

From: Yehuda Sadeh <yehuda@hq.newdream.net> Preparing grounds for rbd that doesn't need mds client. Signed-off-by: Yehuda Sadeh <yehuda@hq.newdream.net> Signed-off-by: Sage Weil <sage@newdream.net> --- fs/ceph/debugfs.c | 11 ++++++++--- fs/ceph/mon_client.c | 3 ++- fs/ceph/super.c | 18 ++++++++++++------ fs/ceph/super.h | 2 ++ 4 files changed, 24 insertions(+), 10 deletions(-) diff --git a/fs/ceph/debugfs.c b/fs/ceph/debugfs.c index 360c4f2..02536f7 ...

From: Yehuda Sadeh <yehuda@hq.newdream.net> This will be used for rbd snapshots administration. Signed-off-by: Yehuda Sadeh <yehuda@hq.newdream.net> --- fs/ceph/decode.h | 5 +++++ fs/ceph/osd_client.c | 18 ++++++++++++++++++ fs/ceph/osd_client.h | 6 ++++++ 3 files changed, 29 insertions(+), 0 deletions(-) diff --git a/fs/ceph/decode.h b/fs/ceph/decode.h index 3d25415..c5b6939 100644 --- a/fs/ceph/decode.h +++ b/fs/ceph/decode.h @@ -191,6 +191,11 @@ static inline void ...

From: Yehuda Sadeh <yehuda@hq.newdream.net> The rados block device (rbd), based on osdblk, creates a block device that is backed by objects stored in the Ceph distributed object storage cluster. Each device consists of a single metadata object and data striped over many data objects. The rbd driver supports read-only snapshots. Signed-off-by: Yehuda Sadeh <yehuda@hq.newdream.net> Signed-off-by: Sage Weil <sage@newdream.net> --- MAINTAINERS | 9 + drivers/block/Kconfig ...

__get/put_user_nocheck() requires 2nd arg should be a user pointer but was missing __user markup. Add it. Signed-off-by: Namhyung Kim <namhyung@gmail.com> --- arch/x86/lib/usercopy_64.c | 9 ++++++--- 1 files changed, 6 insertions(+), 3 deletions(-) diff --git a/arch/x86/lib/usercopy_64.c b/arch/x86/lib/usercopy_64.c index b7c2849..84b0c1b 100644 --- a/arch/x86/lib/usercopy_64.c +++ b/arch/x86/lib/usercopy_64.c @@ -170,14 +170,17 @@ copy_user_handle_tail(char *to, char *from, unsigned ...

From: Maxim Levitsky <maximlevitsky@gmail.com> Atheros PCIe wireless cards handled by ath5k do require L0s disabled. For distributions shipping with CONFIG_PCIEASPM (this will be enabled by default in the future in 2.6.36) this will also mean both L1 and L0s will be disabled when a pre 1.1 PCIe device is detected. We do know L1 works correctly even for all ath5k pre 1.1 PCIe devices though but cannot currently undue the effect of a blacklist, for details you can read pcie_aspm_sanity_check() ...

This set of RapidIO patches adds support for new IDT Gen2 sRIO switch devices - CPS-1848 and CPS-1616. Adding these sRIO switches required to implement standard error recovery mechanism defined by the RapidIO specification. --

The default error-stopped state handler provides recovery mechanism as defined by RIO specification. Signed-off-by: Alexandre Bounine <alexandre.bounine@idt.com> Reviewed-by: Thomas Moll <thomas.moll@sysgo.com> Cc: Matt Porter <mporter@kernel.crashing.org> Cc: Li Yang <leoli@freescale.com> Cc: Kumar Gala <galak@kernel.crashing.org> --- drivers/rapidio/rio.c | 191 +++++++++++++++++++++++++++++++------ drivers/rapidio/switches/idtcps.c | 10 ++ ...

Add callback that allows to create/remove switch-specific sysfs attributes. Signed-off-by: Alexandre Bounine <alexandre.bounine@idt.com> Reviewed-by: Thomas Moll <thomas.moll@sysgo.com> Cc: Matt Porter <mporter@kernel.crashing.org> Cc: Li Yang <leoli@freescale.com> Cc: Kumar Gala <galak@kernel.crashing.org> --- drivers/rapidio/rio-sysfs.c | 26 +++++++++++++++++++------- include/linux/rio.h | 2 ++ 2 files changed, 21 insertions(+), 7 deletions(-) diff --git ...

Add explicit device access check before performing device enumeration. This gives a chance to clear possible link error conditions by issuing safe maintenance read request(s). Signed-off-by: Alexandre Bounine <alexandre.bounine@idt.com> Reviewed-by: Thomas Moll <thomas.moll@sysgo.com> Cc: Matt Porter <mporter@kernel.crashing.org> Cc: Li Yang <leoli@freescale.com> Cc: Kumar Gala <galak@kernel.crashing.org> --- drivers/rapidio/rio-scan.c | 6 ++++++ drivers/rapidio/rio.c | 2 +- ...

A switch ingress port number has to be saved for software assisted error recovery from the error-stopped state. Saving this information also allows to remove several register reads from the RIO enumeration process. Signed-off-by: Alexandre Bounine <alexandre.bounine@idt.com> Reviewed-by: Thomas Moll <thomas.moll@sysgo.com> Cc: Matt Porter <mporter@kernel.crashing.org> Cc: Li Yang <leoli@freescale.com> Cc: Kumar Gala <galak@kernel.crashing.org> --- drivers/rapidio/rio-scan.c | 38 ...

There's nothing obviously wrong with this change. However based on all the preceding discussion, I now think the best approach may be _never_ to make up a fake serial number. Use the module parameter, if any, and otherwise issue a warning and don't have a serial number string descriptor (even though that violates the spec). At this point it should be easy to write a patch to implement and document the new behavior, for both file-storage and mass-storage. Alan Stern --

The kernel currently provides no functionality to analyze the RSS and swap space usage of each individual sysvipc shared memory segment. This patch adds this info for each existing shm segment by extending the output of /proc/sysvipc/shm by two columns for RSS and swap. This additional info about RSS/swap usage of shm segments is very useful for runtime analysis of the kernel. In my case, at work I'm taking care of a large ERP enterprise software, which uses lots of big shared memory segments ...

Hi, We manufacture an interface board for our product that utilizes the IDE interface. A couple of patches were made (back in 2008, kernel 2.6.30 series) to the IDE driver code that are now causing us some grief as we port our driver from kernel 2.6.15 to 2.6.32 (FC5 to Ubuntu LL). 1. Refer to http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=commit;h=dafd01c... A change was made to include/linux/hdreg.h that wrapped the WIN_xx macros in ...

Acked-by: Tejun Heo <tj@kernel.org> Thanks. -- tejun --

From: Raja-Mani <x0102026@ti.com> This is a common header used in all FM submodules (FM V4L2,FM common,FM Rx). Signed-off-by: Raja-Mani <x0102026@ti.com> Signed-off-by: Pramodh AG <pramodh_ag@ti.com> Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> --- drivers/staging/ti-st/fmdrv.h | 225 +++++++++++++++++++++++++++++++++++++++++ 1 files changed, 225 insertions(+), 0 deletions(-) create mode 100644 drivers/staging/ti-st/fmdrv.h diff --git a/drivers/staging/ti-st/fmdrv.h ...

From: Raja-Mani <x0102026@ti.com> This has implementation for FM RX functionality. It communicates with FM V4l2 module and FM common module. Signed-off-by: Raja-Mani <x0102026@ti.com> Signed-off-by: Pramodh AG <pramodh_ag@ti.com> Signed-off-by: Pavan Savoy <pavan_savoy@ti.com> --- drivers/staging/ti-st/fmdrv_rx.c | 805 ++++++++++++++++++++++++++++++++++++++ drivers/staging/ti-st/fmdrv_rx.h | 56 +++ 2 files changed, 861 insertions(+), 0 deletions(-) create mode 100644 ...

From: Raja-Mani <x0102026@ti.com> The following patches are FM V4L2-Radio drivers for WL128x (backward compatible for WL127x). TI's V4L2 based FM driver uses APIs and header files of TI's Shared Transport driver that is hosted in "staging/ti-st/" folder. I request to add TI FM driver to "staging/ti-st/" folder. This will help us keep track of changes to TI FM driver. V4L2 maintainers are fine to review TI FM driver from staging folder. Details of discussion can be found at ...

The commit ebabe9a9001af0af56c0c2780ca1576246e7a74b pass a struct path to vfs_statfs introduced the struct path initialization, and this seems to trigger an Oops on my machine. fh_dentry field may be NULL and set later in fh_verify(), thus the initialization of path must be after fh_verify(). Signed-off-by: Takashi Iwai <tiwai@suse.de> --- fs/nfsd/vfs.c | 14 ++++++++------ 1 files changed, 8 insertions(+), 6 deletions(-) diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c index ...

Hello, yet another trace: [ 5845.374558] CPU 1 is now offline [ 5845.376169] INFO: trying to register non-static key. [ 5845.376251] the code is fine but needs lockdep annotation. [ 5845.376327] turning off the locking correctness validator. [ 5845.376405] Pid: 6754, comm: bash Not tainted 2.6.36-rc0-git12-07921-g60bf26a-dirty #122 [ 5845.376521] Call Trace: [ 5845.376570] [<ffffffff81063e89>] __lock_acquire+0x2d1/0x17fd [ 5845.376657] [<ffffffff81132b2a>] ? sysfs_deactivate+0x3e/0xec [ ...

Hi, I currently am writing a block driver for Legacy Memory sticks. I have few questions about that type of data my ->request will receive from kernel. First of all I think that by default, driver receives requests that contains just one sector and it isn't in high memory. However I am opting in to allow to receive requests that have many sectors span several memory regions, and be in highmem). The request is converted to scatterlist upon which I operate. (Untill this point I did the ...

This functionality was stubbed out until recently. Now we support our normal backtracing API on TILE-Gx as well as on TILE64/TILEPro. This change includes a tweak to the instruction encoding caused by adding addxli for compat mode. Signed-off-by: Chris Metcalf <cmetcalf@tilera.com> --- arch/tile/include/asm/backtrace.h | 4 +- arch/tile/kernel/backtrace.c | 137 ++++++++++++++++++++++++++---------- arch/tile/kernel/stack.c | 8 -- arch/tile/kernel/traps.c | ...

First, the siginfo preamble wasn't quite right; we need to indicate that we are padding up to 4 ints of preamble for 64-bit code, and then for compat mode we need to pad differently, using only 3 ints. Second, the C ABI requires a save area of two registers, not two pointers, since in compat mode we have 64-bit registers all of which we need to save, even though we only have 32-bit VAs. Signed-off-by: Chris Metcalf <cmetcalf@tilera.com> --- arch/tile/include/arch/abi.h | 4 +--- ...

I took that function from ftdi_sio and stripped a lot out of it while developing the driver. I see I missed adding back in the logic dealing with setting flag correctly. I'll work up a patch to properly deal with it. -- Bill --

GCC complains about the original code, because we're using an unintialized variable "flag". I think we should be setting flag based on the UART_LSR_BRK_ERROR_BITS but I'm not sure... I don't have this hardware. Probably passing TTY_NORMAL is better than the current code? Signed-off-by: Dan Carpenter <error27@gmail.com> diff --git a/drivers/usb/serial/ssu100.c b/drivers/usb/serial/ssu100.c index 6e82d4f..494998c 100644 --- a/drivers/usb/serial/ssu100.c +++ b/drivers/usb/serial/ssu100.c @@ ...

A missing include in drivers/media/video/v4l2-ctrls.c makes the kernel (2.6.35-07788-g320b2b8) fail to build: CC drivers/media/video/v4l2-ctrls.o drivers/media/video/v4l2-ctrls.c: In function ‘v4l2_ctrl_handler_init’: drivers/media/video/v4l2-ctrls.c:766: error: implicit declaration of function ‘kzalloc’ drivers/media/video/v4l2-ctrls.c:767: warning: assignment makes pointer from integer without a cast drivers/media/video/v4l2-ctrls.c: In function ...

This commit adds a test application for the put_dec() and family of functions that are used by the previous two commits. Signed-off-by: Michal Nazarewicz <mina86@mina86.com> --- tools/put-dec/Makefile | 16 + tools/put-dec/put-dec-test.c | 927 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 943 insertions(+), 0 deletions(-) create mode 100644 tools/put-dec/Makefile create mode 100644 tools/put-dec/put-dec-test.c diff --git a/tools/put-dec/Makefile ...

Please take a lok at the thread named: Problem with commit deda2e81961e96be4f2c09328baca4710a2fd1a0 I think this is the same issue and there is a patch to fix it. Sam --

s/ending/sending, s/kobject_uevent()/kobject_uevent_env() in the comments. Signed-off-by: Xiaotian Feng <xtfeng@gmail.com> --- lib/kobject_uevent.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/kobject_uevent.c b/lib/kobject_uevent.c index b935795..70af0a7 100644 --- a/lib/kobject_uevent.c +++ b/lib/kobject_uevent.c @@ -123,7 +123,7 @@ static int kobj_usermode_filter(struct kobject *kobj) * @kobj: struct kobject that the action is happening to * ...

subscribe linux-mm --

Hello. WBR, Sergei --

wq->rescuer is not freed when wq is destroyed, leads a memory leak then. This patch also remove a redundant line. Signed-off-by: Xiaotian Feng <dfeng@redhat.com> Cc: Tejun Heo <tj@kernel.org> Cc: Oleg Nesterov <oleg@redhat.com> --- kernel/workqueue.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/kernel/workqueue.c b/kernel/workqueue.c index 2994a0e..1001b6e 100644 --- a/kernel/workqueue.c +++ b/kernel/workqueue.c @@ -2782,7 +2782,6 @@ struct workqueue_struct ...

The build failure was introduced by 13dd0c9 (USB: otg/ulpi: extend the generic ulpi driver.) Cc: Igor Grinberg <grinberg@compulab.co.il> Cc: Mike Rapoport <mike@compulab.co.il> Cc: Greg Kroah-Hartman <gregkh@suse.de> --- arch/arm/mach-imx/mach-cpuimx27.c | 4 ++-- arch/arm/mach-imx/mach-pca100.c | 4 ++-- arch/arm/mach-mx25/mach-cpuimx25.c | 2 +- arch/arm/mach-mx3/mach-cpuimx35.c | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git ...

Hello. Same question here... WBR, Sergei --

Save some bytes removing unused attributes of struct brd_device. Before: [arighi@linux: linux-2.6]$ pahole --cacheline 32 -C brd_device drivers/block/brd.o struct brd_device { int brd_number; /* 0 4 */ int brd_refcnt; /* 4 4 */ loff_t brd_offset; /* 8 8 */ loff_t brd_sizelimit; /* 16 8 */ unsigned int brd_blocksize; ...

2-configuration g_multi has configuration with RNDIS as the first one so that's pretty perfect for us. -- Best regards, _ _ .o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michal "mina86" Nazarewicz (o o) ooo +--<mina86-tlen.pl>--<jid:mina86-jabber.org>--ooO--(_)--Ooo-- --

Hi Matthew, Dennis help me to ported this patch to 2.6.35, and it works as expected. Could you please give me any suggestions for this patch? Thank's a lot! Joey Lee --

Hi Linus, please pull from 'for-linus' branch of git://git390.marist.edu/pub/scm/linux-2.6.git for-linus to receive the following updates: Heiko Carstens (6): [S390] dasd: fix format string types [S390] sys_personality: follow u_long to unsigned int conversion [S390] zcrypt: fix Kconfig dependencies [S390] wire up prlimit64 and fanotify* syscalls [S390] appldata: fix dev_get_stats 64 bit conversion [S390] partitions: fix build error in ibm partition ...

This matters for the lockless page cache, in particular find_get_pages implementation. In the following case, we get can get a deadlock: 0. The radix tree contains two items, one has the index 0. 1. The reader (in this case find_get_pages) takes the rcu_read_lock. 2. The reader acquires slot(s) for item(s) including the index 0 item. 3. The non-zero index item is deleted, and as a consequence the other item is moved to the root of the tree. The place where it used ...

Concur with Simon Reviewed-by: Neil Horman <nhorman@tuxdriver.com> --

FWIW, this looks good to me. --

ideapad-laptop is a new driver which enable hotkeys on Lenovo Ideapad laptops The driver will bind on ACPI HID:VPC2004. When hotkey pressed, the notify function will be called and query EC to tell which key pressed. Hotkeys enabled listed below: * LCD backlight switch - reports KEY_DISPLAY_OFF * One key restore - reports KEY_PROG1 * Brightness Up/down - reports KEY_BRIGHTNESS_CYCLE Both up/down keys reports the same event. Need to find other way to detect * Touchpad switch - reports ...

Cool, now we got two ideapad drivers :p. David just sent an rfkill driver to this list. Maybe you could merge your work ? Thanks, -- Corentin Chary http://xf.iksaif.net --

Here is the thread http://thread.gmane.org/gmane.linux.drivers.platform.x86.devel/471 -- Corentin Chary http://xf.iksaif.net --

That's interesting. I don't *ever* boot with the QS button; I get the keycodes when I boot normally. I tried the QS button precisely once, but only *after* I blew away the original contents of the hard drive with my MeeGo installation, so it didn't boot. Do you know how to restore it? Or do you have a copy of the 'lenovo-ec' module that it apparently contains? I did keep the Windows restore partition, just in case I needed to go back to it to get wireless working. But when I tried to ...

According to PXA3xx Processor Family Developer Manuall Vol1. section "Pin Descriptions and Control", PXA30x and PXA31x Processor Alternate Function Table shows the Alt FN 0 for GPIO51 is CI_HSYNC and for GPIO52 is CI_VSYNC. This patch fixes the MFP defines and also corrects the order of MFD defines. Signed-off-by: Axel Lin <axel.lin@gmail.com> --- arch/arm/mach-pxa/include/mach/mfp-pxa300.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git ...

Hi all, As the merge window is open, please do not add 2.6.37 material to your linux-next included trees until after 2.6.36-rc1. Changes since 20100812: The ceph tree gained a conflict against Linus' tree. The cifs tree lost its build failure. The ocfs2 tree gained a conflict against Linus' tree. The acpi tree gained a build failure for which I applied a patch. The swiotlb-xen tree lost its conflicts. The rr tree lost its merge fix patches. The battery tree lost its ...

I think this double indirection isn't useful and it would be simpler/better to use pr_<level> --

[PATCH v2 3/3] cxgb3i: change cxgb3i to use libcxgbi From: Karen Xie <kxie@chelsio.com> Changed cxgb3i to make use of libcxgbi. Signed-off-by: Karen Xie <kxie@chelsio.com> --- drivers/scsi/Kconfig | 1 drivers/scsi/Makefile | 2 drivers/scsi/cxgbi/Kconfig | 1 drivers/scsi/cxgbi/Makefile | 1 drivers/scsi/cxgbi/cxgb3i/Kbuild | 3 drivers/scsi/cxgbi/cxgb3i/Kconfig | 7 drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 1454 ...

[PATCH v2 0/3] cxgbi iscsi driver From: Karen Xie <kxie@chelsio.com> This patchset includes: 1. added libcxgbi as the common library for both cxgb4i and cxgb3i driver 2. added cxgb4i iscsi initiator v5. 3. changed cxgb3i to use libcxgbi. The version 2 includes the following changes: - Made dbg_level static to avoid compiling errors when both cxgb3i and cxgb4i are built into the kernel. - Deleted cxgbi_fill_iscsi_transport() and cxgbi_fill_scsi_host_template(). The iscsi_transport ...

You've won $485,000 and range rover suv. login:www.wenzhourvis.com User....win2 Password....yar2 Sign. Dr.Markson Brake. --

Hi Joel, Today's linux-next merge of the ocfs2 tree got a conflict in fs/ocfs2/file.c between commit 2c27c65ed0696f0b5df2dad2cf6462d72164d547 ("check ATTR_SIZE contraints in inode_change_ok") from Linus' tree and commit 7b2beb150acfe03445fc61c1302c4225c633776c ("ocfs2: Remove obscure error handling in direct_write") from the ocfs2 tree. The latter just removes that code that the former is modifying, so I did that. -- Cheers, Stephen Rothwell ...

The problem with this, which I've definitely done before, is I never know what paths in menuconfig to look down. The alldefconfig choice seems saner because it provides a dirt-simple CPU setup. Joel -- "Can any of you seriously say the Bill of Rights could get through Congress today? It wouldn't even get out of committee." - F. Lee Bailey Joel Becker Consulting Software Developer Oracle E-mail: joel.becker@oracle.com Phone: (650) 506-8127 --

Mr Chociej, some months ago I wrote a new command (called "btrfs"), with the aim to replace "btrfsctl" at all, for a lot of reasons: bugs, largely unmaintained, difficult to maintain. After a lot of review in the btrfs mailing list now btrfs is in the official source. I suggest to update your patches to using the btrfs command. If you need help in this change, please contact me. The experimental commands may be prefixed with the "test" verb, like $ btrfs test <whatYouWant ...

IMHO this policy is too inflexible. What if I have large array of slow SATA disks and some fast SAS ones ? --

This is very much just a first cut. Our goal here was to get a lot of the legwork and experimental coding out of the way to enable to Btrfs to *fully* tackle heterogeneous storage in the future. BC --

Hi Wolfram, I picked this specific approach because the type in the local rtc structure is unsigned char (matching the struct rtc_wkalrm type) while the passed parameter 'enabled' is unsigned long. I considered these.. rtc->alarm_enabled = (unsigned char) enabled; and rtc->alarm_enabled = !!enabled; The direct assignment seemed the best approach to avoid some type of cast or Hmm, this was a good find. If the key value isn't setup correctly, the boot ROM will clear the RTC counter on ...

On Fri, Aug 13, 2010 at 12:04 AM, Andreas Herrmann The reason for this patch was a breakage in the app that tries to build CPU maps for packages and cores (Nothing to do with Intel or AMD). The app is using info under /sys/devices/system//node/ and /sys/device/system/cpu/cpu0/cache to get the NUMA node and cache sharing info etc. And looking at cpuinfo for core package info. And is getting confused with NUMA overloaded package and core info in /proc/cpunfo. I can of course change this specific ...

Okay, thank you point this warning. Andrew , Could you please fix this warning directly for me? 'return rtc_valid_tm(t)' should be insteaded by 'return rtc_valid_tm(&t->time);'. -- *linux-arm-kernel mailing list mail addr:linux-arm-kernel@lists.infradead.org you can subscribe by: http://lists.infradead.org/mailman/listinfo/linux-arm-kernel * linux-arm-NUC900 mailing list mail addr:NUC900@googlegroups.com main web: https://groups.google.com/group/NUC900 you can subscribe it ...

Thank you. I will try all the suggestions soon. Best regards, Maxim Levitsky --

Hi Maxim, Could you please send us your .config file as well? It may crash before you get to this point. Anyway, there is no scanning taking place during booting - there is a specific 1 minute delay to avoid slowing down the boot process. Kmemleak shouldn't cause a panic, it just prints the message and This kmemleak warning tells us that the kmemleak_alloc() hook got called with a pointer (0xffff880079fe6000) that's already registered with kmemleak. The first trace tells us where the ...

This one builds for me with both compilers. It appears to run OK. As to the original issue - I don't think I ever saw the problem. I'll leave that question for Jason. Larry --

Thanks for the testing! I also managed to trigger the link issue with a 64bit gcc-4.3 cross compiling to 32bit. However both 32bit and 64bit gcc-4.4 didn't trigger the link issue, so it looks like its fixed in gcc. Regardless, after my own testing, the change looks good to me. Raw time is accumulating properly relative to monotonic time. Assuming Jason has no complaints it should be able to be pushed in. Thanks again for the quick reporting and verification. -john --

Sorry I'm just coming into this now that it is 'solved.' I just got back to my hotel from Linuxcon and haven't been checking e-mail. I guess noone (including me) is testing sound in linux-next :(. I wonder what kind of tom foolery it must be doing with f_count (like I am) to have hit problems. I certainly agree the revert patch you sent should be applied if the worst artifact for calling dentry_open() with an 'arbitrary dentry' is that it fails. An easier long term fix might be a ...

Eureka! This seems to solve my problem! My Dual P3-500MHZ is now booting with that patch. Good work guys!!!! Thank you very much, David C. Hill ----- Original Message ----- From: "H. Peter Anvin" <hpa@linux.intel.com> To: "Linus Torvalds" <torvalds@linux-foundation.org> Cc: <stable@kernel.org>; "David Hill" <hilld@binarystorm.net>; "Dieter Stussy" <kd6lvw+software@kd6lvw.ampr.org>; "Eric W. Biederman" <ebiederm@xmission.com>; "H. Peter Anvin" <hpa@linux.intel.com>; "H. Peter ...

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> - Ted --

PeterZ had some ideas in cleaning up the sched domain setup to avoid this maze of #ifdef's. I will let him comment on this. thanks, --

--

--

Dmitri, Thanks for supplying that serio driver. I just have a couple of questions. Even though the interface on the wpce775x EC happens to be a PS/2 interface, this is completely hidden by the firmware on that device. To the linux driver it looks like a dedicated i2c connection directly to the touchpad. You can't substitute any other device on that PS/2 interface without rewriting the firmware in the EC - it's not a generic interface. A manufacturer could even move the touchpad from the ...

The patchset looks functionally correct to me, and with a small patch to make use of WRITE_FUA_FLUSH survives xfstests, and instrumenting the underlying qemu shows that we actually get the flush requests where we should. No performance or power fail testing done yet. But I do not like the transition very much. The new WRITE_FUA_FLUSH request is exactly what filesystems expect from a current barrier request, so I'd rather move to that functionality without breaking stuff inbetween. So if ...

Hello, Do you want to change the whole thing in a single commit? That would be a pretty big invasive patch touching multiple subsystems. Also, I don't know what to do about drdb and would like to leave its conversion to the maintainer (in separate patches). Here's the combined patch I've been working on. I've verified loop and virtio_blk/loop. I just (like five mins ago) got dm/dm conversion compiling, so I'm sure they're broken. The neat part is that thanks to the separation ...

Hello Tejun, Have you seen Hannes Reinecke's and my measurements in http://marc.info/?l=linux-scsi&m=128110662528485&w=2 and http://marc.info/?l=linux-scsi&m=128111995217405&w=2 correspondingly? If yes, what else evidences do you need to see that the tag ordering is a big performance win? Vlad --

Hello, Christoph. There are two reason to avoid changing the meaning of REQ_HARDBARRIER and just deprecate it. One is to avoid breaking filesystems' expectations underneath it. Please note that there are out-of-tree filesystems too. I think it would be too dangerous to relax REQ_HARDBARRIER. Another is that pseudo block layer drivers (loop, virtio_blk, md/dm...) have assumptions about REQ_HARDBARRIER behavior and things would be broken in obscure ways between REQ_HARDBARRIER ...

It's not tag odering that is a win but big queue depth. That's what you measured and what I fully agree on. I haven't been able to get out of Hannes what he actually measured. And if you'd actually look at the patchset allowing deep queues is exactly what it allows us, and while I haven't done testing on this patchset but only on my previous version it does get us back to use the full potential of large arrays exactly because of that. --

Hello, Jan. Ah, okay, I was just trying to match the BH_Ordered usage but you're saying just requiring submit_bh() users to specify appropriate REQ_* (or WRITE_*) in @rw is okay, right? I'll drop the bh part then. Thanks. -- tejun --

In fact my patch going in that direction has been merged already and that code will likely be extended to cover some needs and cases I didn't have in mind when I was preparing it. However, having discussed the whole issue for many times and reconsidered it thoroughly, I think that it's inappropriate to identify the suspend blockers (or wakelocks) framework with the opportunistic suspend feature as proposed in the original submission of the "suspend blockers" patchset. IMO they really are not ...

Well, the problem is, with your /dev/suspend_blocker interface, multiple user space processes are supposed to decide whether or not system suspend should be started and in general there don't seem to be any particularly good criteria for choosing these applications, in general. So, application writers may be tempted to use this interface in all programs and then the decision whether or not to allow these programs to affect system power management will be delegated to users. In turn, the ...

Well firstly you want limits so SELinux says "No" (or rlimit or similar) and secondly you want sysfs views. This is like file permissions - its not hard --

fpu.state is allocated from task_xstate_cachep, the size of task_xstate_cachep is xstate_size. xstate_size is set from cpuid instruction, which is often smaller than sizeof(struct xsave_struct). kvm is using sizeof(struct xsave_struct) to fill in/out fpu.state.xsave, as what we allocated for fpu.state is xstate_size, kernel will write out of memory and caused poison/redzone/padding overwritten warnings. Signed-off-by: Xiaotian Feng <dfeng@redhat.com> Cc: Thomas Gleixner ...

Avi, do you want to take this one or should I? -hpa --

On Thu, 12 Aug 2010 15:50:09 +0800 Hi Carpenter, It looks ok to me, thanks, - Feng --

Hi, We do, I just have to remember to import the -mm tree manually. See: http://kisskb.ellerman.id.au/kisskb/branch/14/ Even better would be to get most of the -mm tree into linux-next itself ... ;-) -- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/

I've fixed this by matching for the filename in the diff line only when it's "diff --git". Also prevented a double-print of the "do not modify file in include/asm" error. From b854ea24f1bd5391a63d8d4e2aa63e1c10870816 Mon Sep 17 00:00:00 2001 From: Rabin Vincent <rabin.vincent@stericsson.com> Date: Wed, 11 Aug 2010 14:45:45 +0530 Subject: [PATCHv2] checkpatch: check for incorrect permissions Throw an error when a source file has been given execute permissions using the mode change line ...

First step is to post it to lkml for discussion, cc:ing the relevant maintainers. (I'm not really sure who that is at the moment. It will I think adding a global flag which the Xen balloon driver can disable should be sufficient. There's no need to make an separate user-settable Quite possibly a left-over from something else. You could just try making it __meminit, then compile with, erm, the option which shows you section conflicts (it shows the number of conflicts at the end of ...

Confirming that Linus's patch fixes it for me: commit 2069601b3f0ea38170d4b509b89f3ca0a373bdc1 Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Thu Aug 12 14:23:04 2010 -0700 Revert "fsnotify: store struct file not struct path" This reverts commit 3bcf3860a4ff9bbc522820b4b765e65e4deceb3e (and the accompanying commit c1e5c954020e "vfs/fsnotify: fsnotify_close can delay the final work in fput" that was a horribly ugly hack to make it work at all).

Sorry, I think the short answer will be that you should give up on this: You would have to add a function in mm/shmem.c to do this: it would need to check vma->vm_file to work out if this vma belongs to it, and use shmem_swp_alloc() to check if the page there is on swap. OTOH No, VM_MAYSHARE is set on many other kinds of mapping too; and is not set on all mappings of shmem objects - there is no good reason to include SysV shm segments here, yet omit other kinds of shmem object (/dev/shm ...

Patch applied. Thanks Steffen! -- Email: Herbert Xu <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt --

-- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum --

With an incorrect coherent_dma_mask, dma_alloc_coherent() will return memory outside of the 64MB window. This means that when dmabounce comes to allocate the replacement buffer, it gets a buffer which won't be accessible to the DMA controller - which is a condition it doesn't check for. Ergo, it breaks dmabounce. --

Actaully, I maintain the freezer, so please send it to me. Thanks, Rafael --

Thats not what I meant. Can you avoid other processors increasing refcounts (direct I/O etc?) on any page struct of the huge page while Migration with known races is really not what we want in the kernel. --

Because a different person (no one from the actual development team) wanted to have it for testing purposes. Maybe we just drop it again. thanks, Sven

If process doing the lookup doesn't have write permission on the top level directory then the lookup will fail. This is not intended, is it? Thanks, Miklos --

Hi Andreas, This doesn't look like an appropriate way to measure the throughput. You should use something like iperf [1] or netperf [2] for your measurements I wouldn't trust the link quality values that much, the calculation in rt61pi is most likely different from what the windows driver does. So it is not Could you elaborate please? Did you actually try to patch it or is this just hw crypto should be enabled by default in rt61pci, however, I don't know Please run proper ...

I suspect something like the attached would suffice. Or maybe moving the CONFIG_PCI_DOMAINS checkout outside CONFIG_PCI. Dave.

ok, updated the patch. In x86, access and dirty bits are set automatically by CPU when CPU accesses memory. When we go into the code path of below flush_tlb_nonprotect_page(), we already set dirty bit for pte and don't need flush tlb. This might mean tlb entry in some CPUs hasn't dirty bit set, but this doesn't matter. When the CPUs do page write, they will automatically check the bit and no software involved. On the other hand, flush tlb in below position is harmful. Test creates ...

Just added Andrea to the Cc list: he did that TLB flush in 1a44e149, I'd feel more comfortable noop-ing it on x86 if you've convinced him. Hugh --

On Wed, 4 Aug 2010 14:19:12 -0400 Fine with me if this stuff goes in with the rest of the Xen bits, presumably through the x86 tree. Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org> -- Jesse Barnes, Intel Open Source Technology Center --

I'm not sure what you mean here. Are you thinking about a third NMI source that triggers while we are still handling the first Well with the flag you also know which nmi you want to skip. --

That time based thing looks a bit complicated. I'm still not sure why you don't want to use a simple flag: After handled a perf NMI: if (handled more than one counter) __get_cpu_var(skip_unknown) = 1; While handling an unknown NMI: if (__get_cpu_var(skip_unknown)) { __get_cpu_var(skip_unknow) = 0; return NOTIFY_STOP; } --

REQ_SOFTBARRIER is indeed purely a reordering barrier inside the block That does indeed look incorrect to me. Any kind of explicit waits usually mean the caller provides ordering. Getting rid of BLKDEV_IFL_BARRIER in the swap code ASAP would indeed be beneficial given that we are trying to get rid of hard barriers completely soon. Auditing the existing blkdev_issue_discard callers in filesystems is high on the todo list for me. --

Fixed a minor error in v2 where a check was erronueously done twice. Original commit message follows: Applies to 2.6.35 (git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6.git perf/core branch) The new patch loads the ELF section headers from a separate file if necessary, to avoid getting confused by the different section file offsets seen in debug images. Invalid section headers are detected by checking for the presence of non- writable SHT_NOBITS sections, which don't make ...

On Fri, Aug 13, 2010 at 8:55 AM, Subrata Modak It would help if you would add in the cgroup maintainers and the --

Yes. --

Sorry about missing this, I have a patch to fix this up now. greg k-h --

> Why do people care that "android is forking the kernel"? A lot of us don't. That's what the GPL is about. It's a big pain if you start splitting it off into two entire things long term - because your maintenance grows harder exponentially but parallel forks are common - SuSE and RHEL Enterprise type editions are forks for example. As far as I can tell it all comes from one or two people with a big PR presence and almost no code in the kernel saying silly things years ago which the IT press ...

Glad we agree that both dynamic power management and opportunistic power management need applications to be written carefully. Of course, dynamic power management requires all of the code in those applications to be carefully written, while experience indicates that opportunistic A PM-driving application is one that exerts control over the system's power state. In the case of Android, a PM-driving application is one That is an excellent example, as it applies equally to dynamic ...

On Fri, Aug 13, 2010 at 6:22 PM, Paul E. McKenney I already mentioned that a "PM-driving application" might not have suspend-blockers; because the user denied them, or because the Huh? Certainly not days, which if Android guys are right, might be how Not really. Say you have 100 packages in your system, how do you know which ones would be PM-driving? Can you grep for something, or see if they open certain file? No, you have to analyze them one by one; they *all* are affected, although not ...

Can we stop arguing about the pointless? The facts are that suspend blockers identifies a race within our suspend to ram system that permeates from top to bottom (that's from server to mobile). The problem is that resume events are racy with respect to suspend and vice versa. This manifests itself most annoyingly on my laptop in the "double suspend" case: where I suspend with a pending suspend event, my laptop will resume and then immediately re-suspend (leading me to kick myself and remind ...

On Thu, Aug 12, 2010 at 10:52 PM, Dominik Brodowski A driver that sits in a corner and doesn't show in the 'menuconfig' of most people and is used by small fraction of user-space applications (perhaps even 0) is just fine. But we are talking of something centric, that can be enabled on all systems, and that affects all user-space. -- Felipe Contreras --

Or in time between keystrokes for most of the platform (backlight excepted). The Intel MID x86 devices are at the point that suspend/resume time on x86 is being hurt by the kernel rewriting smp alternatives as we go from 2 processors live to 1 and back. Alan --

I'd guess there are on the order of 20 users that have built and deployed a kernel with Android suspend blockers support. The total deployed systems is relatively meaningless. --

You are *one* user of the kernel. Let's suppose Android wasn't using suspend-blockers, and there was another equally successful linux mobile platform, Foobingo, and they were using them, and they were the only ones interested on implementing them. What does that change? Nothing. They still need to convince the community that what they are proposing to be merged is actually useful, and somebody will use it. If not, they can just keep the patch Nobody has expressed anything remotely like that ...

So when it comes to practice with suspend blockers, only the Android people have any experience, so theirs is the only experience with I am happy to let the Android guys determine the best use for their time. Thanx, Paul --

In fact, if you are going to port swiotlb, why not port the entire iommu support to x86_32 with PAE too? In fact, I am really irritated at how the x86-64 port was developed completely separate from mainline, when it is just a variant of the same x86 arch. For another example of this, look at the history of ACPI SRAT support in Linux. Yuhong Bao --

Hi Bruce, It returned 42, and after setting 0x40, LnkCtl now says "ASPM Disabled". I'll dock the system now and will report after the weekend or after the first crash. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 3221 ...

Benjamin, can you try the patch below? Thanks, -Robert From 4435322debc38097e9e863e14597ab3f78814d14 Mon Sep 17 00:00:00 2001 From: Robert Richter <robert.richter@amd.com> Date: Fri, 13 Aug 2010 16:29:04 +0200 Subject: [PATCH] oprofile: fix crash when accessing freed task structs This patch fixes a crash during shutdown reported below. The crash is caused be accessing already freed task structs. The fix changes the order for registering and unregistering notifier callbacks. All ...

POSIX ACLs -> RichACLs (NT-style). Not criticising Andreas here, people are asking for this. But Windows ACLs are a nightmare beyond human comprehension :-). In the "too complex to be RichACLs'll do it, but I feel sorry for the admins :-). Jeremy. --

Well, for one, ACLs in NT can be recursive IIRC. You can't say that of Linux ACLs - instead you have to setfacl -R and setfacl -Rd to give one user access to a directory and all its subdirs including future new inodes. --

Muuhh, I do not understand the motivation behind making cfq_io_context per cgroup. We can extract cgroup id from bio, use that to lookup cgroup and its async queues. What am I missing? --

One way to do it would be to get ioprio and class from the context that is used to submit the async request. IO priority and class is tied to a thread anyways. And the io context of that thread can be used to retrieve those values. Even if a thread is submitting IOs to different cgroups, I don't see how you can apply different IO priority and class to its async IOs for different cgroups. Please let me know --

On Sun, 4 Jul 2010 00:02:28 +0200 Oops, I had assumed this was going through some master 'kill the bkl' tree. Applied to my linux-next branch now though, sorry for the delay. -- Jesse Barnes, Intel Open Source Technology Center --

Hi, Sorry about that! Best regards, Maxim Levitsky --

My hung process is "make" (GNU Make 3.81). Stuck forever here: SYSCALL_DEFINE1(brk, unsigned long, brk) { unsigned long rlim, retval; unsigned long newbrk, oldbrk; struct mm_struct *mm = current->mm; unsigned long min_brk; down_write(&mm->mmap_sem); <<<<<<<<<<<<<<< Is make multi-threaded these days? If not, I'm confused about how anything complicated could have happened on mmap_sem. -Tony --

Aha!. I think I found it. This embarrassing declaration in ia64's asm/atomic.h: static __inline__ int ia64_atomic64_add (__s64 i, atomic64_t *v) looks to be the key. Obviously it would be better to return all 64 bits of the answer using "long" rather than just 32 bits with "int". The critical change in the rwsem code that exposed this silliness is: - (rwsem_atomic_update(0, sem) & RWSEM_ACTIVE_MASK)) - /* Someone grabbed the sem already */ + ...

----- Original Message ----- From: "Jonathan Cameron" <jic23@cam.ac.uk> To: "Hemanth V" <hemanthv@ti.com> Cc: <linux-input@vger.kernel.org>; <linux-kernel@vger.kernel.org>; <linux-omap@vger.kernel.org> Sent: Friday, May 21, 2010 5:27 PM Jonathan, Andrew Is there any way forward for this patch, I am unable to induce any response from the input maintainer Thanks Hemanth --

__sw_hweightX can exist even when generic hweight isn't in use per se, because the arch implementation can wrapper the software implementation. This is the case on x86, for example -- most x86 CPUs don't have popcnt yet, so on those the x86 implementation end up calling the __sw_hweight*() implementations. -hpa --

did this miss Blackfin because the original patch was against the 2.6.34 tree ? just wondering why it now build fails ... doing a simple grep shows that the new "tile" arch may also be broken as it uses "hweight32" ... considering __sw_hweightX only exist when the generic hweight is in play, wouldnt it make sense to have include/asm-generic/bitops/arch_hweight.h not always define things ? then most arches can simply pull in include/asm-generic/bitops/hweight.h without having to worry ...

Hi, With pwm zone I mean the number of different speeds which can be programmed for one output channel, the temps divide the entire temp range into zones (number of zones == number of temps + 1) and for each zone one can then tell at what speed / pwm setting the fan should operate when the temperature is in that zone. I have a V0.27P datasheet for the 71889, but yes the fg suffix does not seem to be mentioned anywhere in the datasheet not sure where it comes from. I do know however ...