From mboxrd@z Thu Jan  1 00:00:00 1970
From: Richard Weinberger <richard@nod.at>
Date: Tue, 26 Jun 2018 15:18:49 +0200
Subject: [U-Boot] [PATCH] ubifs: avoid memory corruption during
	ubifsmount
In-Reply-To: <ac93d9bc-1273-3f00-c695-9aaabf8aeeca@st.com>
References: <1529927652-29344-1-git-send-email-patrice.chotard@st.com>
 <1770221.hggCJ2Af2R@blindfold> <ac93d9bc-1273-3f00-c695-9aaabf8aeeca@st.com>
Message-ID: <4959237.plF49sQWAW@blindfold>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Patrice,

Am Dienstag, 26. Juni 2018, 15:01:14 CEST schrieb Patrice CHOTARD:
> Following your remark, Christophe and i relaunched our test setup to go 
> deeper in the analysis of the issue we saw. Unfortunately we can't 
> reproduced it. We have now some doubt.

Ok.
 
> > 
> >> By checking ubifs source code, s_instances parameter is not used anymore.
> >> So, by setting this parameter and the associated source code under
> >> __UBOOT__ compilation switch solves this issue.
> > 
> > Yes, we can clean up this. But as I said, we need to dig deeper to explain
> > the corruption you see.
> 
> Nevertheless, do you think it's useful to clean this code and submit a 
> new patch with clean-up purpose only ?

Yes, this makes sense.

Thanks,
//richard