From: Carl Love <cel@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix for OProfile callgraph for Power 64 bit user apps
Date: Fri, 16 May 2008 09:32:03 -0700 [thread overview]
Message-ID: <1210955523.20791.193.camel@carll-linux-desktop> (raw)
In-Reply-To: <1210874462.20791.54.camel@carll-linux-desktop>
On Thu, 2008-05-15 at 11:01 -0700, Carl Love wrote:
> On Thu, 2008-05-15 at 20:47 +1000, Paul Mackerras wrote:
> > Carl Love writes:
> >
> > > The following patch fixes the 64 bit user code backtrace
> > > which currently may hang the system.
> >
> > What exactly is wrong with it?
> >
> > Having now taken a much closer look, I now don't think Nate Case's
> > patch addresses this, since it only affects constant size arguments
> > <= 8 to copy_{to,from}_user_inatomic.
> >
> > However, I don't see why your patch fixes anything. It means we do
> > two access_ok calls and two __copy_from_user_inatomic calls, for 8
> > bytes, at sp and at sp + 16, rather than doing one access_ok and
> > __copy_from_user_inatomic for 24 bytes at sp. Why does that make any
> > difference (apart from being slower)?
> >
> > Paul
>
> When I tried testing the oprofile call graph on a 64 bit app the system
> consistently hung. I was able to isolate it to the
> __copy_from_user_inatomic() call. When I made the change in my patch to
> make sure I was only requesting one of the values (8bytes) listed in the
> case statement this fixed the issue. I do not know nor was I able to
> figure out why the __copy_from_user_inatomic() call failed trying to
> read 24 bytes. The system would hang and any attempt to use printk to
> see what was going on failed as the output of the print would not go to
> the console before the system hangs.
>
> I backed out my patch, put in Nate's patch. The call graph test ran
> fine. I then backed out Nate's patch to go back and try to re-validate
> that the system still hangs with the original code and it is not
> hanging. Not sure why it now seems to work. I have done some other
> work on the system but I don't see how that would have changed this.
> Argh, I hate chasing phantom bugs! I was working on 2.6.21. I believe
> the 2.6.21 kernel had not been changed. Let me load the latest 2.6.25
> and start over with a pristine kernel and see if I can reproduce the
> hang. Sorry for all the hassle.
>
> Carl Love
>
I installed the latest 2.6.25 kernel and tested OProfile call graph on
the 64 bit user application. I did not see any hangs for the tests that
I ran. I tried things multiple times. So, I guess we should drop the
OProfile callgraph patch. Clearly if there still is a problem it is not
in how the OProfile call graph code is written but is probably in the
underlying calls, i.e. __copy_from_user_inatomic(). I will continue to
test the functionality and see if I can find a example where the system
will hang so we can investigate the underlying cause.
Thank you for your time on this.
Carl Love
prev parent reply other threads:[~2008-05-16 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 18:12 [PATCH] Fix for OProfile callgraph for Power 64 bit user apps Carl Love
2008-05-15 10:47 ` Paul Mackerras
2008-05-15 18:01 ` Carl Love
2008-05-16 16:32 ` Carl Love [this message]
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=1210955523.20791.193.camel@carll-linux-desktop \
--to=cel@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).