[PATCH v7 2/3] VFIO-AER: Vfio-pci driver changes for supporting AER

- New VFIO_SET_IRQ ioctl option to pass the eventfd that is signaled when an error occurs in the vfio_pci_device - Register pci_error_handler for the vfio_pci driver - When the device encounters an error, the error handler registered by the vfio_pci dr

[PATCH v7 3/3] QEMU-AER: Qemu changes to support AER for VFIO-PCI devices

- Create eventfd per vfio device assigned to a guest and register an event handler - This fd is passed to the vfio_pci driver through the SET_IRQ ioctl - When the device encounters an error, the eventfd is signalled and the qemu eventfd handler gets inv

[PATCH v7 0/3] AER-KVM: Error containment of VFIO devices assigned to KVM guests

Add support for error containment when a VFIO device assigned to a KVM guest encounters an error. This is for PCIe devices/drivers that support AER functionality. When the host OS is notified of an error in a device either through the firmware first approach or through an interrupt handled by the A

[PATCH v7 1/3] VFIO: Wrapper for getting reference to vfio_device from device

- Added vfio_device_get_from_dev() as wrapper to get reference to vfio_device from struct device. - Added vfio_device_data() as a wrapper to get device_data from vfio_device. Signed-off-by: Vijay Mohan Pandarathil --- drivers/vfio/vfio.c | 30 +++

Re: lockdep trace from prepare_bprm_creds

On 2013/3/9 11:29, Tejun Heo wrote: > Hello, Li. > > On Sat, Mar 09, 2013 at 10:11:51AM +0800, Li Zefan wrote: >> On 2013/3/8 3:38, Tejun Heo wrote: >>> On Thu, Mar 07, 2013 at 08:12:42PM +0100, Oleg Nesterov wrote: Well yes, I agree. I think that perfomance-wise threadgroup_change_begin() >>

Re: [PATCH v2 02/26] x86, irq: Modify irq chip once for irq remapping

On Fri, Mar 8, 2013 at 12:10 PM, Thomas Gleixner wrote: > > And just for clarification. If you are not going to provide proper > changelogs for _all_ patches of the series, this stuff is going > directly towards /dev/null. I'm not wasting my time to review any of > that otherwise. ok, will try to

Re: [PATCH v2 12/26] x86, irq: Add realloc_irq_and_cfg_at()

On Fri, Mar 8, 2013 at 11:53 AM, Konrad Rzeszutek Wilk wrote: >> + * irq_realloc_desc - allocate irq descriptor for irq that is already >> reserved > > Which begs the question - why was it not allocated when it was reserved? The reasons for not allocating them during reserving: 1. only several p

Re: epoll: possible bug from wakeup_source activation

Arve Hjønnevåg wrote: > On Fri, Mar 8, 2013 at 12:49 PM, Eric Wong wrote: > > What happens if ep_modify calls ep_destroy_wakeup_source > > while __pm_stay_awake is running on the same epi->ws? > > Yes, that looks like a problem. I think calling > ep_destroy_wakeup_source with ep->lock held shoul

[PATCH] x86: kvm: reset the bootstrap processor when it gets an INIT

After receiving an INIT signal (either via the local APIC, or through KVM_SET_MP_STATE), the bootstrap processor should reset immediately and start execution at 0xfff0. Also, SIPIs have no effect on the bootstrap processor. However, KVM currently does not differentiate between the BSP and APs

[PATCH 1/1] scripts/gen_sendmail.py: Script Added: Generate git send-email arguments automatically!

I guess this script won't be merged upstream, but I think it could be useful for someone else. Description borrowed from the header: --- !# This script generates the git send-email automatically !# by looking at the output generated by scripts/get_maintainer.pl !# !# You can pass as m

Re: [PATCH] [Timer][Trivial] __clocksource_register_scale return value use?

ping On Thu, Mar 7, 2013 at 4:41 PM, anish kumar wrote: > __clocksource_register_scale() currently returns int but it should > return void as there are no error paths in that function. > Making it void would help some amount of code to be removed at various > places. > > clocksource_register_hz/k

Re: Suggestion for fixing the variable length array used in the kernel.

On Fri, Mar 08, 2013 at 04:29:22PM -0800, Andrew Morton wrote: > On Wed, 6 Mar 2013 20:46:35 -0800 Christopher Li wrote: > > > Hi, > > > > I am looking at the current sparse warning on the kernel source. > > One category of those warning are produce by the variable length array. > > We all know

BUG in get_next_timer_interrupt

Hello - I am seeing the following crash on a older kernel (2.6.32-200) but thought I would share as I couldn't find earlier reports of this. Please let me know if any more information will help. BUG: unable to handle kernel NULL pointer dereference at 0028 IP: [] get_next_timer_interr

Re: BUG_ON(nd->inode != parent->d_inode);

On Sat, Mar 09, 2013 at 12:13:16AM -0500, Sasha Levin wrote: > On 03/08/2013 11:39 PM, Dave Jones wrote: > > On Fri, Mar 08, 2013 at 08:31:48PM -0800, Linus Torvalds wrote: > > > On Fri, Mar 8, 2013 at 7:50 PM, Dave Jones wrote: > > > > > > > > > > > > I have a feeling there were some sy

Re: BUG_ON(nd->inode != parent->d_inode);

On 03/08/2013 11:39 PM, Dave Jones wrote: > On Fri, Mar 08, 2013 at 08:31:48PM -0800, Linus Torvalds wrote: > > On Fri, Mar 8, 2013 at 7:50 PM, Dave Jones wrote: > > > > > > > > > > I have a feeling there were some sysfs ones that may still be > unfixed. > > > > > > I was right.. > > > >

Re: [PATCH v4] Quirk for buggy dma source tags with Intel IOMMU.

On Fri, Mar 8, 2013 at 7:43 PM, Gaudenz Steinlin wrote: > > Hi Andrew > > Andrew Cooks writes: > >> This patch creates a quirk to allow the Intel IOMMU to be enabled for devices >> that use incorrect tags during DMA. It is similar to the quirk for Ricoh >> devices, but allows mapping multiple fun

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 08:31:48PM -0800, Linus Torvalds wrote: > On Fri, Mar 8, 2013 at 7:50 PM, Dave Jones wrote: > > > > > > > > I have a feeling there were some sysfs ones that may still be unfixed. > > > > I was right.. > > > > [ 425.836722] general protection fault: [#1] PREEM

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 8, 2013 at 7:50 PM, Dave Jones wrote: > > > > > > I have a feeling there were some sysfs ones that may still be unfixed. > > I was right.. > > [ 425.836722] general protection fault: [#1] PREEMPT SMP You forgot to enable DEBUG_PAGE_ALLOC again, but I don't think it much matter

Re: [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process

From: Jingbai Ma Subject: Re: [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process Date: Fri, 8 Mar 2013 18:06:31 +0800 > On 03/07/2013 11:21 PM, Vivek Goyal wrote: >> On Thu, Mar 07, 2013 at 10:58:18PM +0800, Jingbai Ma wrote: ... >> First of all 64MB pe

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 07:38:33PM -0800, Eric W. Biederman wrote: > Dave Jones writes: > > > On Fri, Mar 08, 2013 at 07:16:09PM -0800, Linus Torvalds wrote: > > > Goodie. Your bug reports gave me heartburn. But it sounds like we have > > an > > > angle on all of the ones you've seen now

Re: epoll: possible bug from wakeup_source activation

On Fri, Mar 8, 2013 at 12:49 PM, Eric Wong wrote: > Arve Hjønnevåg wrote: >> On Thu, Mar 7, 2013 at 5:30 PM, Eric Wong wrote: >> > Eric Wong wrote: >> >> Hi Arve, looking at commit 4d7e30d98939a0340022ccd49325a3d70f7e0238 >> >> (epoll: Add a flag, EPOLLWAKEUP, to prevent suspend ...) >> >> >> >

Re: [nsproxy] BUG: unable to handle kernel NULL pointer dereference at 0000000000000024

On Fri, Mar 8, 2013 at 10:01 PM, Eric W. Biederman wrote: > > When a new task is created one of two things needs to happen. > A) A reference count needs to be added to the current nsproxy. > B) B a new nsproxy needs to be created. > > The way that code works today is far from a shiny example of to

Re: [PATCH] mm: page_alloc: remove branch operation in free_pages_prepare()

Hi Hugh, On 03/08/2013 10:01 AM, Hugh Dickins wrote: On Fri, 8 Mar 2013, Joonsoo Kim wrote: On Thu, Mar 07, 2013 at 10:54:15AM -0800, Hugh Dickins wrote: On Thu, 7 Mar 2013, Joonsoo Kim wrote: When we found that the flag has a bit of PAGE_FLAGS_CHECK_AT_PREP, we reset the flag. If we always r

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 07:36:34PM -0800, Linus Torvalds wrote: > Note that my tree does not have the pipe changes. Um still not sure about > the cause, see the patch with a warn-on-once in it. I don't like just > adding the NULL pointer checks willy nilly without understanding why they > made.

Re: [PATCH v2 15/20] kexec: fill note buffers by NT_VMCORE_PAD notes in page-size boundary

From: Yanfei Zhang Subject: Re: [PATCH v2 15/20] kexec: fill note buffers by NT_VMCORE_PAD notes in page-size boundary Date: Fri, 8 Mar 2013 21:02:50 +0800 > 2013/3/8 HATAYAMA Daisuke : >> From: Zhang Yanfei >> Subject: Re: [PATCH v2 15/20] kexec: fill note buffers by NT_VMCORE_PAD >> notes in

Re: BUG_ON(nd->inode != parent->d_inode);

Dave Jones writes: > On Fri, Mar 08, 2013 at 07:16:09PM -0800, Linus Torvalds wrote: > > Goodie. Your bug reports gave me heartburn. But it sounds like we have an > > angle on all of the ones you've seen now? > > > > Or have I forgotten about some case? > > To be honest I've lost track of

Re: lockdep trace from prepare_bprm_creds

Hello, Li. On Sat, Mar 09, 2013 at 10:11:51AM +0800, Li Zefan wrote: > On 2013/3/8 3:38, Tejun Heo wrote: > > On Thu, Mar 07, 2013 at 08:12:42PM +0100, Oleg Nesterov wrote: > >> Well yes, I agree. I think that perfomance-wise threadgroup_change_begin() > >> in de_thread() is fine, and perhaps it i

Re: mmap vs fs cache

Hi Johannes, On 03/09/2013 12:16 AM, Johannes Weiner wrote: On Fri, Mar 08, 2013 at 07:00:55AM -0800, Howard Chu wrote: Chris Friesen wrote: On 03/08/2013 03:40 AM, Howard Chu wrote: There is no way that a process that is accessing only 30GB of a mmap should be able to fill up 32GB of RAM. Th

Re: BUG_ON(nd->inode != parent->d_inode);

Dave Jones writes: > On Fri, Mar 08, 2013 at 09:56:31PM -0500, Dave Jones wrote: > > On Fri, Mar 08, 2013 at 09:26:23PM -0500, Dave Jones wrote: > > > On Fri, Mar 08, 2013 at 06:08:52PM -0800, Linus Torvalds wrote: > > > > On Fri, Mar 8, 2013 at 6:03 PM, Dave Jones wrote: > > > > > > >

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 07:16:09PM -0800, Linus Torvalds wrote: > Goodie. Your bug reports gave me heartburn. But it sounds like we have an > angle on all of the ones you've seen now? > > Or have I forgotten about some case? To be honest I've lost track of the whole collection. Let me repull

Re: [PATCH 2/2] PCI: fix system hang issue of Marvell SATA host controller

On Thu, Mar 7, 2013 at 11:51 PM, Xiangliang Yu wrote: > Hi, Bjorn > >> >> > Fix system hang issue: if first accessed resource file of BAR0 ~ >> >> > BAR4, system will hang after executing lspci command >> >> >> >> This needs more explanation. We've already read the BARs by the time >> >> header q

Re: [PATCH V2] cpufreq: ARM big LITTLE: Add generic cpufreq driver and its DT glue

On 8 March 2013 14:11, Guennadi Liakhovetski wrote: > Also in your driver you're doing > > cpufreq_notify_transition(&freqs, CPUFREQ_PRECHANGE); > ... > cpufreq_notify_transition(&freqs, CPUFREQ_POSTCHANGE); > > So, theoretically you could install su

Re: [PATCH 1/3] intel_idle: changing the continue to break in intel_idle_cpu_init()

On 03/08/2013 04:03 PM, Chuansheng Liu wrote: > > According to commit e022e7eb9, the .enter == NULL is the last one in > state_tables[]. > > So just like intel_idle_cpuidle_driver_init(), in case of .enter == NULL, > breaking the for(;;) loop directly. > > Signed-off-by: liu chuansheng > --- S

Re: [PATCH 3/3] intel_idle: set the state_tables array as __initdata to save mem

On 03/08/2013 04:06 PM, Chuansheng Liu wrote: > > Currently, in intel_idle.c, there are 5 state_tables array, every > array size is sizeof(struct cpuidle_state) * CPUIDLE_STATE_MAX. > > As in intel_idle_cpuidle_driver_init(), we have copied the data into > intel_idle_driver->state[], so do not ne

Re: [PATCH 2/3] intel_idle: Removing the redundant calculating for dev->state_count

On 03/08/2013 04:04 PM, Chuansheng Liu wrote: > > In function intel_idle_cpu_init() and intel_idle_cpuidle_driver_init(), > they are having the same for(;;) loop. > > Here in intel_idle_cpu_init(), the dev->state_count can be assigned by > drv->state_count directly. > > Signed-off-by: liu chuans

sunrpc ODEBUG assertion.

restarted my nfs server, and mounted it from a Mac, and got this.. [47433.585266] WARNING: at lib/debugobjects.c:260 debug_print_object+0x8c/0xb0() [47433.585269] Hardware name: [47433.585273] ODEBUG: assert_init not available (active state 0) object type: timer_list hint: stub_timer+0x

Re: [PATCH] usb/core/devio.c: Don't use GFP_KERNEL while we cannot reset a storage device

On Fri, 8 Mar 2013, Oliver Neukum wrote: > On Friday 08 March 2013 12:55:08 Alan Stern wrote: > > On Sat, 9 Mar 2013, Alexey Khoroshilov wrote: > > > > > As it was described by Oliver Neukum in commit acbe2fe > > > "USB: Don't use GFP_KERNEL while we cannot reset a storage device": > > > > > >

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 09:56:31PM -0500, Dave Jones wrote: > On Fri, Mar 08, 2013 at 09:26:23PM -0500, Dave Jones wrote: > > On Fri, Mar 08, 2013 at 06:08:52PM -0800, Linus Torvalds wrote: > > > On Fri, Mar 8, 2013 at 6:03 PM, Dave Jones wrote: > > > > > > > > existing pathname + 'a'

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 09:26:23PM -0500, Dave Jones wrote: > On Fri, Mar 08, 2013 at 06:08:52PM -0800, Linus Torvalds wrote: > > On Fri, Mar 8, 2013 at 6:03 PM, Dave Jones wrote: > > > > > > existing pathname + 'a' = fine. > > > > > > existing pathname + '/' + 'a' = boom. > > > >

Re: mmap vs fs cache

Hi Johannes, On 03/08/2013 10:08 AM, Johannes Weiner wrote: On Thu, Mar 07, 2013 at 04:43:12PM +0100, Jan Kara wrote: Added mm list to CC. On Tue 05-03-13 09:57:34, Howard Chu wrote: I'm testing our memory-mapped database code on a small VM. The machine has 32GB of RAM and the size of the D

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 06:08:52PM -0800, Linus Torvalds wrote: > On Fri, Mar 8, 2013 at 6:03 PM, Dave Jones wrote: > > > > existing pathname + 'a' = fine. > > > > existing pathname + '/' + 'a' = boom. > > Good. > > > Looks like if I do this.. > > > >if (isdigit(newpath[len])

Re: [3.9-rc1] irq 16: nobody cared (was [3.9-rc1] very poor interrupt responses)

On Fri, 8 Mar 2013, Peter Hurley wrote: > [ +linux-usb ] > > On Fri, 2013-03-08 at 14:12 -0500, Shawn Starr wrote: > > Hello folks, > > > > I am noticing since rc0 and now rc1, very poor interrupt handling. Keyboard > > response, mouse movements, display refreshing etc. General input/display >

[3.9-rc1] Locking dependency problem

In kernel 3.9-rc1, I get the following lockdep warning. This kernel is from the wireless-testing tree, but I have seen the same message from the mainline kernel. [ 4199.401157] [ 4199.401159] == [ 4199.401160] [ INFO: possible circular locking

Re: lockdep trace from prepare_bprm_creds

On 2013/3/8 3:38, Tejun Heo wrote: > Hello, > > On Thu, Mar 07, 2013 at 08:12:42PM +0100, Oleg Nesterov wrote: >> Well yes, I agree. I think that perfomance-wise threadgroup_change_begin() >> in de_thread() is fine, and perhaps it is even more clean because we are >> going to do the thread-group c

Re: Inactive memory keep growing and how to release it?

Cc experts. Hugh, Johannes, On 03/04/2013 08:21 PM, Lenky Gao wrote: 2013/3/4 Zlatko Calusic : The drop_caches mechanism doesn't free dirty page cache pages. And your bash script is creating a lot of dirty pages. Run it like this and see if it helps your case: sync; echo 3 > /proc/sys/vm/drop_

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 8, 2013 at 6:03 PM, Dave Jones wrote: > > existing pathname + 'a' = fine. > > existing pathname + '/' + 'a' = boom. Good. > Looks like if I do this.. > >if (isdigit(newpath[len]) != 0) { > newpath[len] = '/'; >newpath[len+1] = 'A'; >

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 05:18:29PM -0800, Linus Torvalds wrote: > On Fri, Mar 8, 2013 at 4:36 PM, Dave Jones wrote: > > > > Ok, it's definitly the 'append something on the end of a valid pathname' > > changeset. 'something' can be anything it seems. > > Ok. so maybe the way to "bisect" this

screen failing to display after resume from hibernate

Machine resumes and fails to power on the screen. Trace: Mar 7 23:35:09 lenovo kernel: [33562.808041] [drm:intel_lvds_disable] *ERROR* timed out waiting for panel to power off Mar 7 23:35:09 lenovo kernel: [33562.808052] [ cut here ] Mar 7 23:35:09 lenovo kernel: [33562

Re: Re: [PATCH] Kprobes blacklist: Conditionally add x86-specific symbols

(2013/03/08 22:15), oskar.and...@sonymobile.com wrote: > On 05:23 Fri 08 Mar , Masami Hiramatsu wrote: >> (2013/03/07 19:44), oskar.and...@sonymobile.com wrote: >>> From: Bjorn Davidsson >>> >>> The kprobes blacklist contains x86-specific symbols. >>> Looking for these in kallsyms takes unnece

Re: mmap vs fs cache

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/08/2013 10:00 AM, Howard Chu wrote: > Yes, that's what I was thinking. I added a > posix_madvise(..POSIX_MADV_RANDOM) but that had no effect on the > test. Yep, that's because it isn't implemented. You might try MADV_WILLNEED to schedule it to

Re: [PATCH] power: make goldfish option have a dependency on goldfish

Hi Paul, On Fri, Mar 08, 2013 at 11:38:41AM -0500, Paul Gortmaker wrote: > > I see. In that case, please feel free to send the patch to akpm with my > > Nack and pointing to this discussion. If Andrew agrees and I was wrong > > (and I'm really curious whether I am right or wrong), I will start > >

Re: [PATCH 11/12] rwsem: wake all readers when first waiter is a reader

On Fri, Mar 8, 2013 at 4:32 PM, Dave Chinner wrote: > On Wed, Mar 06, 2013 at 03:21:50PM -0800, Michel Lespinasse wrote: >> When the first queued waiter is a reader, wake all readers instead of >> just those that are at the front of the queue. There are really two >> motivations for this change: >

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 8, 2013 at 4:36 PM, Dave Jones wrote: > > Ok, it's definitly the 'append something on the end of a valid pathname' > changeset. 'something' can be anything it seems. Ok. so maybe the way to "bisect" this is to play with that. For example, does it happen even if the "something" does n

Re: [PATCH] add extra free kbytes tunable

Hi Hugh, On 03/02/2013 11:08 AM, Hugh Dickins wrote: On Sat, 2 Mar 2013, Simon Jeons wrote: On 03/02/2013 09:42 AM, Hugh Dickins wrote: On Sat, 2 Mar 2013, Simon Jeons wrote: In function __add_to_swap_cache if add to radix tree successfully will result in increase NR_FILE_PAGES, why? This is a

Re: [PATCH 03/10] ARM: smp_twd: Divorce smp_twd from local timer API

On 03/08/13 12:29, Tony Lindgren wrote: > Applying that does not seem to help, but you might want to get vexpress > running anyways for some multiplatform sanity checks. > > I just built and installed qemu-linaro from their git, then ran the > command above. Looks like stock qemu does not work for

[PATCH net-next] drivers:net: Remove unnecessary OOM messages after netdev_alloc_skb

Emitting netdev_alloc_skb and netdev_alloc_skb_ip_align OOM messages is unnecessary as there is already a dump_stack after allocation failures. Other trivial changes around these removals: Convert a few comparisons of pointer to 0 to !pointer. Change flow to remove unnecessary label. Remove now u

[ANNOUNCE] 3.9-rc1-nohz1

Hi, Several fixes there. And this version should have much lesser spurious warnings. Your testing and reviews is very appreciated. The 5 first patches of the series are pending on a pull request for -tip (3.10 material). I'm now considering how I should upstream the rest of the series. All the p

[PATCH] epoll: comment + BUILD_BUG_ON to prevent epitem bloat

This will prevent us from accidentally introducing a memory bloat regression here in the future. Signed-off-by: Eric Wong Cc: Andrew Morton Cc: Davide Libenzi , Cc: Al Viro --- Andrew Morton wrote: > On Thu, 7 Mar 2013 10:32:40 + Eric Wong wrote: > > > Andrew Morton wrote: > >

[GIT PULL] Btrfs updates

Hi Linus, Please grab my for-linus: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus These are scattered fixes and one performance improvement. The biggest functional change is in how we throttle metadata changes. The new code bumps our average file creation rate u

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 07:19:17PM -0500, Dave Jones wrote: > On Fri, Mar 08, 2013 at 04:02:02PM -0800, Linus Torvalds wrote: > > On Fri, Mar 8, 2013 at 3:55 PM, Dave Jones wrote: > > > > > > That one was printed out with %s > > > > Ok, so those random pathnames you generate? They're f

Re: ipc/testmsg GPF.

On Fri, Mar 08, 2013 at 07:27:01PM -0500, Peter Hurley wrote: > [ +Andrew Morton ] > > On Thu, 2013-03-07 at 16:38 -0500, Dave Jones wrote: > > Trying to reproduce that nd_jump_link trace, but I keep hitting other bugs > > instead. It's like whackamole. Except these are even more annoying >

Re: [PATCH 11/12] rwsem: wake all readers when first waiter is a reader

On Wed, Mar 06, 2013 at 03:21:50PM -0800, Michel Lespinasse wrote: > When the first queued waiter is a reader, wake all readers instead of > just those that are at the front of the queue. There are really two > motivations for this change: Isn't this a significant change of semantics for the rwsem

Re: Suggestion for fixing the variable length array used in the kernel.

On Wed, 6 Mar 2013 20:46:35 -0800 Christopher Li wrote: > Hi, > > I am looking at the current sparse warning on the kernel source. > One category of those warning are produce by the variable length array. > We all know that the kernel stack has a limit so we don't want to allocate > too much sta

Re: ipc/testmsg GPF.

[ +Andrew Morton ] On Thu, 2013-03-07 at 16:38 -0500, Dave Jones wrote: > Trying to reproduce that nd_jump_link trace, but I keep hitting other bugs > instead. It's like whackamole. Except these are even more annoying > than moles. Dave, I thought I copied you on the 'ipc MSG_COPY fixes' patchse

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 04:02:02PM -0800, Linus Torvalds wrote: > On Fri, Mar 8, 2013 at 3:55 PM, Dave Jones wrote: > > > > That one was printed out with %s > > Ok, so those random pathnames you generate? They're funky. I just did a test with just a page of 'A's, and got the same result, so

Re: [PATCH] ARM: OMAP: drop "select MACH_NOKIA_RM696"

On Fri, Mar 08, 2013 at 07:02:44PM +0100, Paul Bolle wrote: > On Fri, 2013-03-08 at 09:55 -0800, Tony Lindgren wrote: > > * Paul Bolle [130308 09:24]: > > > Should I draft a patch? > > > > Sure that would be nice. > > One thing I couldn't determine is how the generated mach-types.h header > hand

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 8, 2013 at 3:55 PM, Dave Jones wrote: > > That one was printed out with %s Ok, so those random pathnames you generate? They're funky. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.or

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 03:45:37PM -0800, Linus Torvalds wrote: > On Fri, Mar 8, 2013 at 3:30 PM, Dave Jones wrote: > > [ 100.729401] nd->last.name = > > (\xffd2.W._.N.".\xfffe.\xff80.^N.?.\xffe4.E.8.g.\xffd2.N.\xffb6.^G.\xfff1.\xffcc.U.\xffda.^_.h.^M.1.\xf

Re: [PATCH] epoll: trim epitem by one cache line on x86_64

On Thu, 7 Mar 2013 10:32:40 + Eric Wong wrote: > Andrew Morton wrote: > > It's going to be hard to maintain this - someone will change something > > sometime and break it. I suppose we could add a runtime check if we > > cared enough. Adding a big fat comment to struct epitem might help. >

Basic perf PMU support for Haswell v9

This is based on v7 of the full Haswell PMU support, rebased, reviewer-optimized and stripped down to the bare bones Most interesting new features are not in this patchkit (full version is git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git hsw/pmu5) Contains support for: - Basic Has

[PATCH 5/5] perf, x86: Support Haswell v4 LBR format

From: Andi Kleen Haswell has two additional LBR from flags for TSX: intx and abort, implemented as a new v4 version of the LBR format. Handle those in and adjust the sign extension code to still correctly extend. The flags are exported similarly in the LBR record to the existing misprediction fl

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 8, 2013 at 3:47 PM, Dave Jones wrote: > > That didn't take long.. Ok, thanks, so it's not something new to this merge window. Not that I expected it to be, but better safe than sorry. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the bo

[PATCH 4/5] perf, x86: Move NMI clearing to end of PMI handler after the counter registers are reset

From: Andi Kleen This avoids some problems with spurious PMIs on Haswell. Haswell seems to behave more like P4 in this regard. Do the same thing as the P4 perf handler by unmasking the NMI only at the end. Shouldn't make any difference for earlier family 6 cores. Tested on Haswell, IvyBridge, We

[PATCH 3/5] perf, x86: Basic Haswell PEBS support v4

From: Andi Kleen Add basic PEBS support for Haswell. The constraints are similar to SandyBridge with a few new events. v2: Readd missing pebs_aliases v3: Readd missing hunk. Fix some constraints. v4: Fix typo in PEBS event table (Stephane Eranian) Reviewed-by: Stephane Eranian Signed-off-by: An

[PATCH 1/5] perf, x86: Add Haswell PEBS record support v4

From: Andi Kleen Add support for the Haswell extended (fmt2) PEBS format. It has a superset of the nhm (fmt1) PEBS fields, but has a longer record so we need to adjust the code paths. The main advantage is the new "EventingRip" support which directly gives the instruction, not off-by-one instru

[PATCH 2/5] perf, x86: Basic Haswell PMU support v6

From: Andi Kleen Add basic Haswell PMU support. Similar to SandyBridge, but has a few new events and two new counter bits. There are some new counter flags that need to be prevented from being set on fixed counters, and allowed to be set for generic counters. Also we add support for the counte

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 03:28:01PM -0800, Linus Torvalds wrote: > Oh, btw, I'm assuming you're testing current git like you usually do. > > If so, just to humor me, can you try plain 3.8 (or 3.8.2 or whatever > the current stable kernel is). Because while the oopses may be due to > your exten

Re: [Announce] open ath9k_htc firmware

Many thanks to Adrian for his hard work on all this and to everyone else who volunteered to help make this happen, including the understanding by our management at QCA and even Tensilica requires some handsome applause for their commitment, understanding on letting us get this out. We now have a pu

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 8, 2013 at 3:30 PM, Dave Jones wrote: > [ 100.729401] nd->last.name = > (\xffd2.W._.N.".\xfffe.\xff80.^N.?.\xffe4.E.8.g.\xffd2.N.\xffb6.^G.\xfff1.\xffcc.U.\xffda.^_.h.^M.1.\xffc5.\xff82.%.B.\xffe0.\xffad.^U.8.^L.c.Z.^K.\xffe4.h.

Re: 8250.nr_uarts broken in 3.7

On Fri, Mar 08, 2013 at 06:28:09PM -0500, Josh Boyer wrote: > On Sat, Mar 09, 2013 at 12:14:23AM +0100, Jiri Slaby wrote: > > On 03/09/2013 12:10 AM, Jiri Slaby wrote: > > > On 03/08/2013 11:58 PM, Jiri Slaby wrote: > > >> On 03/08/2013 11:49 PM, Josh Boyer wrote: > > >>> On Fri, Mar 08, 2013 at 11

Re: [PATCH v3] fat: editions to support fat_fallocate

On Thu, 7 Mar 2013 22:56:57 +0900 Namjae Jeon wrote: > From: Namjae Jeon > > Implement preallocation via the fallocate syscall on VFAT partitions. > > Change Log: > v3: Release preallocated blocks at file release. > > With FALLOC_FL_KEEP_SIZE, there is no way to distinguish if the mismatch >

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 03:28:01PM -0800, Linus Torvalds wrote: > Oh, btw, I'm assuming you're testing current git like you usually do. yes. > If so, just to humor me, can you try plain 3.8 (or 3.8.2 or whatever > the current stable kernel is). Because while the oopses may be due to > your e

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 03:20:40PM -0800, Linus Torvalds wrote: > On Fri, Mar 8, 2013 at 3:07 PM, Dave Jones wrote: > > > > Ok, got something more meaningful out of the lookup_slow trace. > > > > [ 66.082984] parent->dname.name (06b6b6b6b6b6b6b) > > [ 66.083637] parent = > > > > At fi

Re: 8250.nr_uarts broken in 3.7

On Sat, Mar 09, 2013 at 12:14:23AM +0100, Jiri Slaby wrote: > On 03/09/2013 12:10 AM, Jiri Slaby wrote: > > On 03/08/2013 11:58 PM, Jiri Slaby wrote: > >> On 03/08/2013 11:49 PM, Josh Boyer wrote: > >>> On Fri, Mar 08, 2013 at 11:47:01PM +0100, Jiri Slaby wrote: > Yeah, I agree this is ugly. J

Re: BUG_ON(nd->inode != parent->d_inode);

Oh, btw, I'm assuming you're testing current git like you usually do. If so, just to humor me, can you try plain 3.8 (or 3.8.2 or whatever the current stable kernel is). Because while the oopses may be due to your extensions to trinity, let's make sure. Maybe something bad happened in the merge wi

Re: [patch] [SCSI] scsi_transport_sas: check for allocation failure

On 13-03-08 05:50 PM, James Bottomley wrote: On Fri, 2013-03-08 at 12:57 -0500, Douglas Gilbert wrote: On 13-03-08 07:02 AM, Dan Carpenter wrote: Static checkers complain that this allocation isn't checked. We should return zero if the allocation fails. Signed-off-by: Dan Carpenter diff --g

[PATCH] perf: Enable function tracing for perf core

From: Andi Kleen According to Steven R. there is no reason left to not support function tracing for the perf core. This makes it easier to debug perf. Don't remove -pg for the x86 and generic perf core. Cc: rost...@goodmis.org Signed-off-by: Andi Kleen --- arch/x86/kernel/cpu/Makefile |1

[PATCH] perf, x86: Allow setting period 1

From: Andi Kleen I had some requests for setting period 1, so that every event of something is caught. To my knowledge there is no limit to 1 on Intel hardware. Just remove the check for minimum 2 If specific CPUs have problems we can black list them. Signed-off-by: Andi Kleen --- arch/x86/k

[PATCH] perf, x86: Add Sandy Bridge constraints for CYCLE_ACTIVITY.*

From: Andi Kleen Add CYCLE_ACTIVITY.CYCLES_NO_DISPATCH/CYCLES_L1D_PENDING These recently documented events have restrictions to counter 0-3 and counter 2 respectively. The scheduler needs to know that to schedule them correctly. IvyBridge already has the necessary constraints. Signed-off-by: A

Re: kswapd craziness round 2

On 03/08/2013 07:42 AM, Hillf Danton wrote: > On Fri, Mar 8, 2013 at 3:37 AM, Jiri Slaby wrote: >> On 03/01/2013 03:02 PM, Hillf Danton wrote: >>> On Fri, Mar 1, 2013 at 1:02 AM, Jiri Slaby wrote: Ok, no difference, kswap is still crazy. I'm attaching the output of "grep -vw '0' /p

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 8, 2013 at 3:07 PM, Dave Jones wrote: > > Ok, got something more meaningful out of the lookup_slow trace. > > [ 66.082984] parent->dname.name (06b6b6b6b6b6b6b) > [ 66.083637] parent = > > At first I thought AH-HA! SLAB POISON! > But look closer.. it's shifted by 8 bits. Or just t

[PATCH 1/1] kernel/pid.c: Improve flow of a loop inside alloc_pidmap.

Notes: find_next_offset searches for an available "cleaned bit" in the respective pid bitmap (page), so returns the offset if found, otherwise it returns a value equals to BITS_PER_PAGE (invalid offset). For example, suppose find_next_offset didn't find any available bit, so there's no purpose to

[PATCH wq/for-3.9-fixes] workqueue: fix possible pool stall bug in wq_unbind_fn()

From: Lai Jiangshan Since multiple pools per cpu have been introduced, wq_unbind_fn() has a subtle bug which may theoretically stall work item processing. The problem is two-fold. * wq_unbind_fn() depends on the worker executing wq_unbind_fn() itself to start unbound chain execution, which wo

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 06:07:34PM -0500, Dave Jones wrote: > parent seems to be a pointer to "\0". Ignore that last part, it's wrong. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo inf

Re: 8250.nr_uarts broken in 3.7

On 03/09/2013 12:10 AM, Jiri Slaby wrote: > On 03/08/2013 11:58 PM, Jiri Slaby wrote: >> On 03/08/2013 11:49 PM, Josh Boyer wrote: >>> On Fri, Mar 08, 2013 at 11:47:01PM +0100, Jiri Slaby wrote: Yeah, I agree this is ugly. Just re-definining MODULE_PARAM_PREFIX at the end of the file shou

Re: 8250.nr_uarts broken in 3.7

On Fri, Mar 08, 2013 at 11:58:39PM +0100, Jiri Slaby wrote: > On 03/08/2013 11:49 PM, Josh Boyer wrote: > > On Fri, Mar 08, 2013 at 11:47:01PM +0100, Jiri Slaby wrote: > >> Yeah, I agree this is ugly. Just re-definining MODULE_PARAM_PREFIX at > >> the end of the file should do the trick (followed b

Re: 8250.nr_uarts broken in 3.7

On 03/08/2013 11:58 PM, Jiri Slaby wrote: > On 03/08/2013 11:49 PM, Josh Boyer wrote: >> On Fri, Mar 08, 2013 at 11:47:01PM +0100, Jiri Slaby wrote: >>> Yeah, I agree this is ugly. Just re-definining MODULE_PARAM_PREFIX at >>> the end of the file should do the trick (followed by >>> "module_param(n

Re: BUG_ON(nd->inode != parent->d_inode);

On Fri, Mar 08, 2013 at 02:41:19PM -0800, Linus Torvalds wrote: > On Fri, Mar 8, 2013 at 1:04 PM, Dave Jones wrote: > > > > queue up the sad trombone noises. > > > > One of the things trinity passes syscalls is a page of deformed unicode. > > Apparently this page is so fucked up, that it cra

[PATCH V7 -next 00/33] loop: Issue O_DIRECT aio using bio_vec

Zach, I've had to alter some of these patches to build against the linux-next due to your cleanup of the aio code. Could you please look at patches 14, 15 and 19 in particular to check if I did anything insane? This patch series adds a kernel interface to fs/aio.c so that kernel code can issue con

[PATCH V7 -next 14/33] aio: add aio_kernel_() interface

This adds an interface that lets kernel callers submit aio iocbs without going through the user space syscalls. This lets kernel callers avoid the management limits and overhead of the context. It will also let us integrate aio operations with other kernel apis that the user space interface doesn

  1   2   3   4   5   >