All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Leun <vb-contact@newton.leun.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Michael Leun <lkml20101129@newton.leun.net>,
	hughd@google.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kernel BUG at mm/truncate.c:475!
Date: Sat, 11 Dec 2010 20:50:16 +0100	[thread overview]
Message-ID: <4D03D5F8.4010206@newton.leun.net> (raw)
In-Reply-To: <E1PRQDn-0007jZ-5S@pomaz-ex.szeredi.hu>

Miklos Szeredi schrieb:
> On Mon, 6 Dec 2010, Michael Leun wrote:
>> At the moment I'm trying to create an easy to reproduce scenario.
>>

To be honest that somewhat sliddered down on my todo-list due to not
much time and kernel_cache worked around that...

> I've managed to reproduce the BUG.

...so I'm very happy you found a way to reproduce yourself.

[...]

> Attached patch attempts to do this without adding more fields to
> struct address_space.  It fixes the bug in my testing.

I'll add this patch on my work machine monday morning (happened for me
only on that quadcore, I realize now...) and turn off kernel_cache
again, of course, and let you know what happens.

Thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Michael Leun <vb-contact@newton.leun.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Michael Leun <lkml20101129@newton.leun.net>,
	hughd@google.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: kernel BUG at mm/truncate.c:475!
Date: Sat, 11 Dec 2010 20:50:16 +0100	[thread overview]
Message-ID: <4D03D5F8.4010206@newton.leun.net> (raw)
In-Reply-To: <E1PRQDn-0007jZ-5S@pomaz-ex.szeredi.hu>

Miklos Szeredi schrieb:
> On Mon, 6 Dec 2010, Michael Leun wrote:
>> At the moment I'm trying to create an easy to reproduce scenario.
>>

To be honest that somewhat sliddered down on my todo-list due to not
much time and kernel_cache worked around that...

> I've managed to reproduce the BUG.

...so I'm very happy you found a way to reproduce yourself.

[...]

> Attached patch attempts to do this without adding more fields to
> struct address_space.  It fixes the bug in my testing.

I'll add this patch on my work machine monday morning (happened for me
only on that quadcore, I realize now...) and turn off kernel_cache
again, of course, and let you know what happens.

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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-12-11 20:12 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 18:49 kernel BUG at mm/truncate.c:475! Michael Leun
2010-11-30 23:00 ` Hugh Dickins
2010-11-30 23:00   ` Hugh Dickins
2010-12-01 10:25   ` Miklos Szeredi
2010-12-01 10:25     ` Miklos Szeredi
2010-12-01 11:45     ` Michael Leun
2010-12-01 11:45       ` Michael Leun
2010-12-01 17:22       ` Miklos Szeredi
2010-12-01 17:22         ` Miklos Szeredi
2010-12-02  7:41         ` Michael Leun
2010-12-02  7:41           ` Michael Leun
2010-12-02  8:15           ` Michael Leun
2010-12-02  8:15             ` Michael Leun
2010-12-02  9:42             ` Miklos Szeredi
2010-12-02  9:42               ` Miklos Szeredi
2010-12-02 10:57               ` Michael Leun
2010-12-02 10:57                 ` Michael Leun
2010-12-03  7:53                 ` Michael Leun
2010-12-03  7:53                   ` Michael Leun
2010-12-06 12:36                   ` Miklos Szeredi
2010-12-06 12:36                     ` Miklos Szeredi
2010-12-06 19:43                     ` Michael Leun
2010-12-06 19:43                       ` Michael Leun
2010-12-11 14:14                       ` Miklos Szeredi
2010-12-11 19:50                         ` Michael Leun [this message]
2010-12-11 19:50                           ` Michael Leun
2010-12-13 22:20                         ` Andrew Morton
2010-12-13 22:20                           ` Andrew Morton
2010-12-14  7:31                           ` Hugh Dickins
2010-12-14  7:31                             ` Hugh Dickins
2010-12-14  9:10                             ` Peter Zijlstra
2010-12-14  9:10                               ` Peter Zijlstra
2010-12-14  9:11                             ` Peter Zijlstra
2010-12-14  9:11                               ` Peter Zijlstra
2010-12-14 10:45                           ` Miklos Szeredi
2010-12-14 10:45                             ` Miklos Szeredi
2010-12-15  4:32                             ` Hugh Dickins
2010-12-15  4:32                               ` Hugh Dickins
2010-12-15 11:22                               ` Miklos Szeredi
2010-12-15 11:22                                 ` Miklos Szeredi
2010-12-16  0:26                                 ` Hugh Dickins
2010-12-16  0:26                                   ` Hugh Dickins
2010-12-16 14:50                               ` Robert Święcki
2010-12-16 14:50                                 ` Robert Święcki
2010-12-16 19:05                                 ` Hugh Dickins
2010-12-16 19:05                                   ` Hugh Dickins

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=4D03D5F8.4010206@newton.leun.net \
    --to=vb-contact@newton.leun.net \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkml20101129@newton.leun.net \
    --cc=miklos@szeredi.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.