From: Linus Torvalds <torvalds@linux-foundation.org>
To: Philippe Elie <phil.el@wanadoo.fr>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sami Farin <safari-kernel@safari.iki.fi>
Subject: Re: [patch 1/2] oProfile: oops when profile_pc() return ~0LU
Date: Tue, 23 Oct 2007 09:55:09 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0710230951170.30120@woody.linux-foundation.org> (raw)
In-Reply-To: <20071023161321.GA2884@zaniah>
On Tue, 23 Oct 2007, Philippe Elie wrote:
>
> For the signed-offs I thought the From: was an implicit Signed-offs.
No, there are no implicit sign-offs. The point of sign-offs is that it
makes the copyright and flow of patches explicit, so an "implicit
sign-off" would defeat the whole point.
> Test was done privately, Sami helped to narrow down the trouble, but
> he didn't test the last patch, nothing bad on Sami side, I was too
> confident the fix was obvious after narrowing it.
Well, I just wanted an ack that it was tested, since it seemed a bit
subtle and (like the sign-offs) that explicit "yes, this was tested" was
missing. Looks like I was right in asking for it:
> > The previous patch I tested by Philippe, oprof-fix-profile_pc-use.patch,
> > worked ok, but with this latest patch oprofiled aborts.
> > But kernel does not oops or print msgs.
>
> argh, I just moved the wrong eip from kernel to user space where the same
> problem occur too, *sighs*, since I can't reproduce Sami problem, my own
> test obviously worked...
>
> Sami, can you test this new patch. After testing can you report
> the contents of /dev/oprofile/stats/cpu*/sample_invalid_eip ?
>
> Linus, there is two way to fix this problem, the attached patch fix it
> by sanitizing the sampled eip,
I'm perfectly happy with the attached patch, I just want it to be
properly tested and have all the sign-offs (and explanations etc) in
place, and I can apply it.
Of course, I cannot think of a single architecture where an EIP of ~0UL is
valid anyway, so I'm also not opposed to just keeping ~0UL as the magic
value.
Linus
prev parent reply other threads:[~2007-10-23 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 12:08 Philippe Elie
2007-10-23 2:38 ` Linus Torvalds
2007-10-23 10:10 ` Sami Farin
2007-10-23 16:13 ` Philippe Elie
2007-10-23 16:49 ` Sami Farin
2007-10-23 16:55 ` Linus Torvalds [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=alpine.LFD.0.999.0710230951170.30120@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.el@wanadoo.fr \
--cc=safari-kernel@safari.iki.fi \
/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
all inboxes | Powered by JetHome®