>Hello!
>
>On Wed, Apr 09, 2003 at 02:18:02AM +0100, Dave Jones wrote:
>
>
>
>>Whilst running fsx.. (Though fsx didn't trigger any error,
>>and is still running)..
>>buffer layer error at fs/buffer.c:127
>>Call Trace:
>> [<c016d260>] __wait_on_buffer+0xd0/0xe0
>> [<c0121760>] autoremove_wake_function+0x0/0x50
>> [<c0121760>] autoremove_wake_function+0x0/0x50
>> [<c02886c8>] reiserfs_unmap_buffer+0x68/0xa0
>>
>>
>
>Andrew Morton said "That's not a bug. It is errant debugging code." because the page is locked by us,
>so buffers are safe.
>So I am not looking into this and hoping that somebody will fix the debugging code instead ;)
>
>Bye,
> Oleg
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
Oleg, if someone doesn't do it for you in 7 days, you must do it....
errant debugging code is a bug.... when users (reasonably) think our fs
has bugs, that needs to be fixed;-)
-- Hans
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/