On Mon, Dec 23, 2013 at 11:44:35PM +0100, Ludovic Desroches wrote: > On Fri, Dec 20, 2013 at 09:08:51AM +0100, Ludovic Desroches wrote: > > Hello, > > > > On Wed, Dec 18, 2013 at 04:21:17PM +0900, Joonsoo Kim wrote: > > > On Mon, Dec 16, 2013 at 03:43:43PM +0100, Ludovic Desroches wrote: > > > > Hello, > > > > > > > > On Fri, Dec 13, 2013 at 10:59:09AM +0900, Joonsoo Kim wrote: > > > > > On Thu, Dec 12, 2013 at 03:36:19PM +0100, Ludovic Desroches wrote: > > > > > > fix mmc mailing list address error > > > > > > > > > > > > On Thu, Dec 12, 2013 at 03:31:50PM +0100, Ludovic Desroches wrote: > > > > > > > Hi, > > > > > > > > > > > > > > With v3.13-rc3 I have an error when the atmel-mci driver calls > > > > > > > flush_dcache_page (log at the end of the message). > > > > > > > > > > > > > > Since I didn't have it before, I did a git bisect and the commit introducing > > > > > > > the error is the following one: > > > > > > > > > > > > > > 106a74e slab: replace free and inuse in struct slab with newly introduced active > > > > > > > > > > > > > > I don't know if this commit has introduced a bug or if it has revealed a bug > > > > > > > in the atmel-mci driver. > > > > > > > > > > Hello, > > > > > > > > > > I think that this commit may not introduce a bug. This patch remove one > > > > > variable on slab management structure and replace variable name. So there > > > > > is no functional change. > > > > > > > > > > > > > If I have reverted this patch and other ones you did on top of it and > > > > the issue disappear. > > > > > > Hello, > > > > > > Could you give me your '/proc/slabinfo' before/after this commit (106a74e)? > > > > > > And how about testing with artificially increasing size of struct slab on > > > top of this commit (106a74e)? > > > > > > I really wonder why the problem happens, because this doesn't cause any > > > functional change as far as I know. Only side-effect from this patch is > > > decreasing size of struct slab. > > > > Sorry I am not at the office, I have tried to reproduce it with a > > different device and a different sdcard but without success. I'll test > > it on Monday. > > I am still not at the office but I get the same device and the same > sdcard and I don't reproduce it. I am not totally in the same > conditions. It seems there is an extra parameter causing this bug but I > don't figure out which one at the moment. Okay. I will wait for you! Thanks for informing progress. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
