linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Michael Leun <lkml20101129@newton.leun.net>
Cc: miklos@szeredi.hu, 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: Mon, 06 Dec 2010 13:36:30 +0100	[thread overview]
Message-ID: <E1PPaIw-0004pW-Mk@pomaz-ex.szeredi.hu> (raw)
In-Reply-To: <20101203085350.55f94057@xenia.leun.net> (message from Michael Leun on Fri, 3 Dec 2010 08:53:50 +0100)

On Fri, 3 Dec 2010, Michael Leun wrote:
> On Thu, 2 Dec 2010 11:57:22 +0100
> Michael Leun <lkml20101129@newton.leun.net> wrote:
> 
> > > Can you please describe in detail the workload that's causing this
> > > to happen?
> > 
> > Thats rather complicated, but I'll try. Basically it boils down to:
> > 
> > unshare -n -m /bin/bash
> > unionfs -o
> > cow,suid,allow_other,max_files=65536 /home/netenv/user1-union=RW:/=RO /home/netenv/user1
> > mount -n -t proc none /home/netenv/user1/proc mount -n -t sysfs
> > none /home/netenv/user1/sys mount -n -t devtmpfs
> > devtmpfs /home/netenv/user1/dev mount -n -t devpts
> > devpts /home/netenv/user1/dev/pts chroot /home/netenv/user1 /bin/su -
> > user1
> [...]
> > In some of this setups two or more environments share the same
> > writable branch, so the files in this environments changed against
> > real root of the machine are the same, e.g.:
> > 
> > [...]
> > unionfs -o
> > cow,suid,allow_other,max_files=65536 /home/netenv/commondir=RW:/=RO /home/netenv/user1
> > [...]
> > 
> > and another one
> > 
> > [...]
> > unionfs -o
> > cow,suid,allow_other,max_files=65536 /home/netenv/commondir=RW:/=RO /home/netenv/user2
> > [...]
> 
> Additional note: Happens also WITHOUT that "two unionfs mounts use the
> same branch dir" stuff.

Thanks.

For you the workaround would be to use the "kernel_cache" option which
disables cache invalidation on open.

I'll try to reproduce the BUG on my machine, and if I don't succeed
I'll need som more help from you.

Also could you please send me your kernel .config

> 
> Really seems to happen much more often in 2.6.36.1 than in 2.6.36.

Probably just coincidence.  Sometimes the frequency a bug shows up
depends on code layout (and hence cache layout) differences, which can
vary from compile to compile and even from one boot to the next.

Thanks,
Miklos

--
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-06 12:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101130194945.58962c44@xenia.leun.net>
2010-11-30 23:00 ` Hugh Dickins
2010-12-01 10:25   ` Miklos Szeredi
2010-12-01 11:45     ` Michael Leun
2010-12-01 17:22       ` Miklos Szeredi
2010-12-02  7:41         ` Michael Leun
2010-12-02  8:15           ` Michael Leun
2010-12-02  9:42             ` Miklos Szeredi
2010-12-02 10:57               ` Michael Leun
2010-12-03  7:53                 ` Michael Leun
2010-12-06 12:36                   ` Miklos Szeredi [this message]
2010-12-06 19:43                     ` Michael Leun
2010-12-11 14:14                       ` Miklos Szeredi
2010-12-11 19:50                         ` Michael Leun
2010-12-13 22:20                         ` Andrew Morton
2010-12-14  7:31                           ` Hugh Dickins
2010-12-14  9:10                             ` Peter Zijlstra
2010-12-14  9:11                             ` Peter Zijlstra
2010-12-14 10:45                           ` Miklos Szeredi
2010-12-15  4:32                             ` Hugh Dickins
2010-12-15 11:22                               ` Miklos Szeredi
2010-12-16  0:26                                 ` Hugh Dickins
2010-12-16 14:50                               ` Robert Święcki
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=E1PPaIw-0004pW-Mk@pomaz-ex.szeredi.hu \
    --to=miklos@szeredi.hu \
    --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 \
    /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