From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8302 invoked by alias); 26 Jan 2013 18:16:14 -0000 Received: (qmail 8294 invoked by uid 22791); 26 Jan 2013 18:16:13 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 26 Jan 2013 18:15:41 +0000 Received: by mail.ecoscentric.com (Postfix, from userid 48) id 5643C468000A; Sat, 26 Jan 2013 18:15:39 +0000 (GMT) From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001732] fs-ecos bug/assertion X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Filesystem support X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: bernd.edlinger@hotmail.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: high X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: References: X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Sat, 26 Jan 2013 18:16:00 -0000 Message-Id: <20130126181534.9C1BC468000A@mail.ecoscentric.com> Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-bugs-owner@sourceware.org X-SW-Source: 2013/txt/msg00036.txt.bz2 Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001732 --- Comment #4 from Bernd Edlinger 2013-01-26 18:15:32 GMT --- Hi Praveen, somehow on my fs-ecos.c the line numbers are different than on yours. But when I interpret it right what happens here, this might have happened: The file system traverses a directory entry, and the metadata on the flash are changed which points to an uninitialized inode. When the invalid data are hit, the BUG is raised. Probably that should have happened earlier... IF your flash changes its contents when the file system is mounted, the file system may fail. Especially if a flash is removed and another flash inserted, you should unmount the file system when the flash is removed, and re-mount the file system again, when the flash is inserted again. Once the file system has validated the flash content, the flash should never be changed without the file system knowing that. Regards, Bernd. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.