From: "Chris Friesen" <cfriesen@nortel.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, akpm@linux-foundation.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: Resend: /proc/<pid>/maps offset output broken in 2.6.29
Date: Thu, 02 Apr 2009 14:45:47 -0600 [thread overview]
Message-ID: <49D523FB.2020504@nortel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0904021938270.25731@blonde.anvils>
Hugh Dickins wrote:
> This is a cosmetic matter, not worth more than a couple of lines of
> code: I suggested masking off the high bits in the display, but when
> KAMEZAWA-san suggested just showing 0, it was hard to argue against
> his brutal simplicity.
<snip>
> Consider this change a fix: it used to show 00000000 before 2.6.7.
>
> See http://lkml.org/lkml/2009/1/13/331 for one of the threads
> on the subject - but you've not tempted me to reopen it!
Okay, fair enough. I'll change my code to deal with it. Thanks for the
explanation.
Chris
WARNING: multiple messages have this Message-ID (diff)
From: "Chris Friesen" <cfriesen@nortel.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Michael Ellerman <michael@ellerman.id.au>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
peterz@infradead.org, akpm@linux-foundation.org
Subject: Re: Resend: /proc/<pid>/maps offset output broken in 2.6.29
Date: Thu, 02 Apr 2009 14:45:47 -0600 [thread overview]
Message-ID: <49D523FB.2020504@nortel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0904021938270.25731@blonde.anvils>
Hugh Dickins wrote:
> This is a cosmetic matter, not worth more than a couple of lines of
> code: I suggested masking off the high bits in the display, but when
> KAMEZAWA-san suggested just showing 0, it was hard to argue against
> his brutal simplicity.
<snip>
> Consider this change a fix: it used to show 00000000 before 2.6.7.
>
> See http://lkml.org/lkml/2009/1/13/331 for one of the threads
> on the subject - but you've not tempted me to reopen it!
Okay, fair enough. I'll change my code to deal with it. Thanks for the
explanation.
Chris
next prev parent reply other threads:[~2009-04-02 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 19:24 /proc/<pid>/maps offset output broken Chris Friesen
2009-04-01 23:18 ` Resend: /proc/<pid>/maps offset output broken in 2.6.29 Chris Friesen
2009-04-02 8:04 ` Michael Ellerman
2009-04-02 8:04 ` Michael Ellerman
2009-04-02 12:43 ` Hugh Dickins
2009-04-02 12:43 ` Hugh Dickins
2009-04-02 17:53 ` Chris Friesen
2009-04-02 17:53 ` Chris Friesen
2009-04-02 19:10 ` Hugh Dickins
2009-04-02 19:10 ` Hugh Dickins
2009-04-02 20:45 ` Chris Friesen [this message]
2009-04-02 20:45 ` Chris Friesen
2009-04-05 18:51 ` Hugh Dickins
2009-04-05 18:51 ` 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=49D523FB.2020504@nortel.com \
--to=cfriesen@nortel.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=peterz@infradead.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 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.