From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: possible regression on 3.13 when calling flush_dcache_page
Date: Mon, 16 Dec 2013 15:43:43 +0100 [thread overview]
Message-ID: <20131216144343.GD9627@ldesroches-Latitude-E6320> (raw)
In-Reply-To: <20131213015909.GA8845@lge.com>
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.
> I doubt that side-effect of this patch reveals a bug in other place.
> Side-effect is reduced memory usage for slab management structure. It would
> makes some slabs have more objects with more density since slab management
> structure is sometimes on the page for objects. So if it diminishes, more
> objects can be in the page.
>
> Anyway, I will look at it more. If you have any progress, please let me know.
No progress at the moment.
Regards
Ludovic
>
> Thanks.
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-12-16 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 14:31 Ludovic Desroches
2013-12-12 14:36 ` Ludovic Desroches
2013-12-13 1:59 ` Joonsoo Kim
2013-12-16 14:43 ` Ludovic Desroches [this message]
2013-12-18 7:21 ` Joonsoo Kim
2013-12-20 8:08 ` Ludovic Desroches
2013-12-23 22:44 ` Ludovic Desroches
2013-12-24 6:38 ` Joonsoo Kim
2014-01-03 14:54 ` Ludovic Desroches
2014-01-06 0:26 ` Joonsoo Kim
2014-01-06 9:34 ` Ludovic Desroches
2014-01-09 7:16 ` Joonsoo Kim
2013-12-12 17:13 ` Russell King - ARM Linux
2013-12-16 10:49 ` Ludovic Desroches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131216144343.GD9627@ldesroches-Latitude-E6320 \
--to=ludovic.desroches@atmel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mmc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox