From: "Rob Mueller" <robm@fastmail.fm>
To: "Chris Mason" <mason@suse.com>
Cc: <akpm@osdl.org>, "Lars Roland" <lroland@gmail.com>,
"Bron Gondwana" <brong@fastmail.fm>,
<linux-kernel@vger.kernel.org>,
"Vladimir Saveliev" <vs@namesys.com>,
"Jeremy Howard" <jhoward@fastmail.fm>
Subject: Re: 2.6.12.2 dies after 24 hours
Date: Wed, 13 Jul 2005 11:27:39 +1000 [thread overview]
Message-ID: <03e601c5874a$12613fa0$7c00a8c0@ROBMHP> (raw)
In-Reply-To: 200507122103.10159.mason@suse.com
> Sorry for the confusion, you're hitting the other mmap_sem -> transaction
> lock
> problem. This one should be solvable with an iget so we make sure not to
> do
> the final unlink until after the mmap sem is dropped.
>
> Lets see what I can do...
Oh dang.
I thought this last crash after upgrading to 2.6.12.2 was due to the IRQ
BALANCE issue Lars suggested, but you're saying that it's actually a whole
different bug, though similar to the previous "prepare_write ...
copy_from_user ... commit_write" lock problem?
Is this something new between 2.6.4-mm2 and 2.6.12.2? Or would it have
always been present, just for some reason we're hitting it in 2.6.12 now but
weren't hitting it in 2.6.4?
I feel we're moving backwards... :(
Rob
next prev parent reply other threads:[~2005-07-13 1:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 9:26 2.6.12.2 dies after 24 hours Rob Mueller
2005-07-12 9:43 ` Lars Roland
2005-07-12 11:46 ` Rob Mueller
2005-07-12 12:13 ` Lars Roland
2005-07-12 13:51 ` Bron Gondwana
2005-07-12 16:37 ` Lars Roland
2005-07-13 0:27 ` Rob Mueller
2005-07-13 0:42 ` Chris Mason
2005-07-13 0:50 ` Rob Mueller
2005-07-13 1:03 ` Chris Mason
2005-07-13 1:27 ` Rob Mueller [this message]
2005-07-13 1:00 ` Chris Mason
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='03e601c5874a$12613fa0$7c00a8c0@ROBMHP' \
--to=robm@fastmail.fm \
--cc=akpm@osdl.org \
--cc=brong@fastmail.fm \
--cc=jhoward@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=lroland@gmail.com \
--cc=mason@suse.com \
--cc=vs@namesys.com \
/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