Hi,
Tested-by: Tang Chen
Have tested this patch, and the problem is fixed.
Thanks.
On 02/04/2014 12:49 AM, kosaki.motoh...@gmail.com wrote:
From: KOSAKI Motohiro
During aio stress test, we observed the following lockdep warning.
This mean AIO+numa_balancing is currently deadlockable.
The
(2014/02/04 1:49), kosaki.motoh...@gmail.com wrote:
From: KOSAKI Motohiro
During aio stress test, we observed the following lockdep warning.
This mean AIO+numa_balancing is currently deadlockable.
The problem is, aio_migratepage disable interrupt, but
__set_page_dirty_nobuffers
unintentionall
> Indeed, good catch. Do we need the same treatment for
> __set_page_dirty_buffers() that can be called by way of
> clear_page_dirty_for_io()?
Indeed. I posted a patch fixed __set_page_dirty() too. plz see
Subject: [PATCH] __set_page_dirty uses spin_lock_irqsave instead of
spin_lock_irq
--
To un
On Mon, 3 Feb 2014, kosaki.motoh...@gmail.com wrote:
> From: KOSAKI Motohiro
>
> During aio stress test, we observed the following lockdep warning.
> This mean AIO+numa_balancing is currently deadlockable.
>
> The problem is, aio_migratepage disable interrupt, but
> __set_page_dirty_nobuffers
From: KOSAKI Motohiro
During aio stress test, we observed the following lockdep warning.
This mean AIO+numa_balancing is currently deadlockable.
The problem is, aio_migratepage disable interrupt, but
__set_page_dirty_nobuffers
unintentionally enable it again.
Generally, all helper function sho
5 matches
Mail list logo