Re: [PATCH] debug_check_no_locks_freed: fix in_range() checks

2007-11-24 Thread Alasdair G Kergon
On Sat, Nov 24, 2007 at 01:18:35PM +0100, Torsten Kaiser wrote: > I will reapply agk-dm-dm-crypt-move-bio-submission-to-thread.patch and > this patch and boot several times OK for a test system, but until the write loop problem is addressed I believe there's a risk of data corruption under low mem

Re: [PATCH] debug_check_no_locks_freed: fix in_range() checks

2007-11-24 Thread Oleg Nesterov
On 11/24, Torsten Kaiser wrote: > > On Nov 24, 2007 11:53 AM, Oleg Nesterov <[EMAIL PROTECTED]> wrote: > > Torsten, could you ack/nack this patch? > > From looking at the code I would ack it. Great. > I will reapply agk-dm-dm-crypt-move-bio-submission-to-thread.patch and > this patch and boot se

Re: [PATCH] debug_check_no_locks_freed: fix in_range() checks

2007-11-24 Thread Ingo Molnar
* Oleg Nesterov <[EMAIL PROTECTED]> wrote: > > But debug_check_no_locks_freed() seems does: > > const void *mem_to = mem_from + mem_len > > -> mem_to is the last byte of the freed range, that fits in_range > > lock_from = (void *)hlock->instance; > > -> first byte of the lock > > lock_to = (void

Re: [PATCH] debug_check_no_locks_freed: fix in_range() checks

2007-11-24 Thread Torsten Kaiser
On Nov 24, 2007 11:53 AM, Oleg Nesterov <[EMAIL PROTECTED]> wrote: > Torsten, could you ack/nack this patch? >From looking at the code I would ack it. I will reapply agk-dm-dm-crypt-move-bio-submission-to-thread.patch and this patch and boot several times, but as the message was not triggered on e