public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Ken Chen <kenchen@google.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: proc tree build failure
Date: Mon, 10 Nov 2008 08:53:11 +0300	[thread overview]
Message-ID: <20081110055311.GA3138@x200.localdomain> (raw)
In-Reply-To: <20081110162941.e9e9ef3a.sfr@canb.auug.org.au>

On Mon, Nov 10, 2008 at 04:29:41PM +1100, Stephen Rothwell wrote:
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
> 
> fs/proc/base.c:2547: error: 'pid_stack' undeclared here (not in a function)
> 
> Caused by an interaction of commits
> 078e9901c02d4899db5b24f708b8dfbca8935891 ("stacktrace:
> add /proc/<pid>/stack to dump task's stack trace") and
> 35f0b5fd7fab907a1119eaa614d9b24e5e225755 ("stacktrace:
> convert /proc/<pid>/stack to seqfiles") from the tip-core tree with commit
> 5d8880e3e0fb96459c652ac5e1504b90c949b3b9 ("proc: remove '##' usage") from
> the proc tree.
> 
> The former added a new usage of INF (which the second converted to a
> ONE).  I added the following patch to the merge of the proc tree and can
> carry it.

Time to steal this /proc/*/stack from Ingo. :-)

> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -2544,7 +2544,7 @@ static const struct pid_entry tgid_base_stuff[] = {
>  	INF("wchan",      S_IRUGO, proc_pid_wchan),
>  #endif
>  #ifdef CONFIG_STACKTRACE
> -	ONE("stack",      S_IRUSR, pid_stack),
> +	ONE("stack",      S_IRUSR, proc_pid_stack),

correct

  reply	other threads:[~2008-11-10  5:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  5:29 linux-next: proc tree build failure Stephen Rothwell
2008-11-10  5:53 ` Alexey Dobriyan [this message]
2008-11-10  7:36   ` Ingo Molnar
2008-11-10  8:42     ` [PATCH v42] proc: add /proc/*/stack (was Re: linux-next: proc tree build failure) Alexey Dobriyan
2008-11-10  8:49       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2009-03-30  6:43 linux-next: proc tree build failure Stephen Rothwell
2009-01-23  6:15 Stephen Rothwell
2009-01-23  7:09 ` Cyrill Gorcunov
2009-01-23 18:48   ` Alexey Dobriyan
2009-01-23 19:26     ` Cyrill Gorcunov
2009-01-23 19:41       ` Cyrill Gorcunov
2009-01-23 20:26         ` Cyrill Gorcunov
2008-11-24  7:15 Stephen Rothwell
2008-11-28  8:05 ` Alexey Dobriyan
2008-11-28  9:00   ` David Miller
2008-11-28 10:25     ` David Miller
2008-11-20  6:24 Stephen Rothwell
2008-11-20  8:43 ` Eric W. Biederman
2008-10-21  7:21 Stephen Rothwell

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=20081110055311.GA3138@x200.localdomain \
    --to=adobriyan@gmail.com \
    --cc=kenchen@google.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    /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