From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from webapps.arcom.com ([194.200.159.168]) by canuck.infradead.org with esmtp (Exim 4.52 #1 (Red Hat Linux)) id 1EDgh2-0003pq-Sl for linux-mtd@lists.infradead.org; Fri, 09 Sep 2005 07:05:40 -0400 Message-ID: <43216C69.2060404@arcom.com> Date: Fri, 09 Sep 2005 12:05:13 +0100 From: David Vrabel MIME-Version: 1.0 To: linux-mtd list Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Badness in do_exit after remounting JFFS2 read-only List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 [] (dump_stack+0x0/0x14) from [] (do_exit+0x44/0xb0c) [] (do_exit+0x0/0xb0c) from [] (sys_exit+0x0/0x18) [] (complete_and_exit+0x0/0x20) from [] (jffs2_garbage_collect_thread+0x124/0x12c) [] (jffs2_garbage_collect_thread+0x0/0x12c) from [] (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/