Badness in do_exit after remounting JFFS2 read-only

Hi,

With 2.6.13 remounting a JFFS2 filesystem read-only results in

Badness in do_exit at /home/dvrabel/embed/qed/linux-2.6-working/kernel/exit.c:787 [<c001c8f8>] (dump_stack+0x0/0x14) from [<c002f9d0>] (do_exit+0x44/0xb0c) [<c002f98c>] (do_exit+0x0/0xb0c) from [<c00304b8>] (sys_exit+0x0/0x18) [<c0030498>] (complete_and_exit+0x0/0x20) from [<c00a4c30>] (jffs2_garbage_collect_thread+0x124/0x12c)
[<c00a4b0c>] (jffs2_garbage_collect_thread+0x0/0x12c) from [<c002f98c>] (do_exit+0x0/0xb0c)
r6 = 00000000 r5 = 00000000 r4 = 00000000

This is the WARN_ON(atomic_read(&tsk->fs_excl)); in do_exit().

I can't work out where .fs_excl is being set though. It doesn't seem to be anywhere in the JFFS2 code.

David Vrabel

David Vrabel, Design Engineer

Arcom, Clifton Road           Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK         Web: http://www.arcom.com/

This no longer happens in (at least) 2.6.14-rc4.

David Vrabel

David Vrabel, Design Engineer

Arcom, Clifton Road           Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK         Web: http://www.arcom.com/