From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga09.intel.com ([134.134.136.24]) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1Uopph-0006JN-VB for linux-mtd@lists.infradead.org; Tue, 18 Jun 2013 06:56:02 +0000 Message-ID: <51C005B8.3000709@intel.com> Date: Tue, 18 Jun 2013 10:01:12 +0300 From: Adrian Hunter MIME-Version: 1.0 To: "Prins Anton (ST-CO/ENG1.1)" Subject: Re: UBIFS failure & stable page writes References: <85D877DD6EE67B4A9FCA9B9C3A4865670C3E8CB9B7@SI-MBX14.de.bosch.com> <1369732266.5446.117.camel@sauron.fi.intel.com> <85D877DD6EE67B4A9FCA9B9C3A4865670C3E91DC9C@SI-MBX14.de.bosch.com> <1369810158.5446.208.camel@sauron.fi.intel.com> <85D877DD6EE67B4A9FCA9B9C3A4865670C3E91E697@SI-MBX14.de.bosch.com> <1370239282.21714.21.camel@sauron.fi.intel.com> <85D877DD6EE67B4A9FCA9B9C3A4865670C3EA0F38E@SI-MBX14.de.bosch.com> <51B82A1D.30009@intel.com> <85D877DD6EE67B4A9FCA9B9C3A4865670C3F1A3508@SI-MBX14.de.bosch.com> <51B862D6.2080807@intel.com> <85D877DD6EE67B4A9FCA9B9C3A4865670C3F1A3590@SI-MBX14.de.bosch.com> <51B87315.7090808@intel.com>, <85D877DD6EE67B4A9FCA9B9C3A4865670C3F1A36BC@SI-MBX14.de.bosch.com> , <85D877DD6EE67B4A9FCA9B9C3A4865670C3F1A3D7F@SI-MBX14.de.bosch.com> <85D877DD6EE67B4A9FCA9B9C3A4865670C3F4167DD@SI-MBX14.de.bosch.com> In-Reply-To: <85D877DD6EE67B4A9FCA9B9C3A4865670C3F4167DD@SI-MBX14.de.bosch.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "linux-mtd@lists.infradead.org" , =?ISO-8859-1?Q?Mats_K=E4rrman?= , "dedekind1@gmail.com" List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 18/06/13 09:31, Prins Anton (ST-CO/ENG1.1) wrote: > Last night I did do additional tests with create/remove of files in a > while loop on a synchronous mounted UBIFS. I did NOT get any node 0 or 1 > written over this night, but obvious enough I saw some strange node id in > the orphan area: 0xdead4ead > > 0xdead4ead Is known to me as SPINLOCK_MAGIC; but no glue why It is in the > orphan area if node number... Is something known about 0xdead4ead? I am afraid I have not had time to analyze the effects of the double-free but it is reasonable to assume that UBIFS may be writing an orphan from a structure that has been freed and therefore re-used by, for example in this case, a spinlock.