mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Denys Vlasenko <vda.linux@googlemail.com>,
	Oleg Nesterov <oleg@redhat.com>, Amerigo Wang <amwang@redhat.com>,
	"Jonathan M. Foote" <jmfoote@cert.org>,
	Roland McGrath <roland@hack.frob.com>,
	Pedro Alves <palves@redhat.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] Include asm/siginfo.h in linux/coredump.h
Date: Thu, 11 Oct 2012 00:20:56 +0200	[thread overview]
Message-ID: <20121011002056.09c7c2bb@spider.haslach.nod.at> (raw)
In-Reply-To: <20121010151659.029b2a46.akpm@linux-foundation.org>

Am Wed, 10 Oct 2012 15:16:59 -0700
schrieb Andrew Morton <akpm@linux-foundation.org>:

> On Thu, 11 Oct 2012 00:04:07 +0200
> Richard Weinberger <richard@nod.at> wrote:
> 
> > commit 5ab1c30 (coredump: pass siginfo_t* to do_coredump() and
> > below, not merely signr) added siginfo_t to linux/coredump.h but
> > forgot to include asm/siginfo.h. This breaks the build for UML/i386.
> > (And any other arch where asm/siginfo.h is not magically
> > preincluded...)
> > 
> > In file included from arch/x86/um/elfcore.c:2:0:
> > include/linux/coredump.h:15:25: error: unknown type name 'siginfo_t'
> > make[1]: *** [arch/x86/um/elfcore.o] Error 1
> > 
> > Cc: Denys Vlasenko <vda.linux@googlemail.com>
> > Cc: Oleg Nesterov <oleg@redhat.com>
> > Cc: Amerigo Wang <amwang@redhat.com>
> > Cc: "Jonathan M. Foote" <jmfoote@cert.org>
> > Cc: Roland McGrath <roland@hack.frob.com>
> > Cc: Pedro Alves <palves@redhat.com>
> > Cc: Fengguang Wu <fengguang.wu@intel.com>
> > Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Richard Weinberger <richard@nod.at>
> > ---
> >  include/linux/coredump.h | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/include/linux/coredump.h b/include/linux/coredump.h
> > index 1775eb8..1d73993 100644
> > --- a/include/linux/coredump.h
> > +++ b/include/linux/coredump.h
> > @@ -4,6 +4,7 @@
> >  #include <linux/types.h>
> >  #include <linux/mm.h>
> >  #include <linux/fs.h>
> > +#include <asm/siginfo.h>
> >  
> >  /*
> >   * These are the only things you should do on a core-file: use
> > only these
> 
> hm, yes.  It would be nice to jsut forward-declare the struct but we
> can't do that because it's a pesky typedef.

I know. :-\

> I wonder if it would be cleaner to just include linux/signal.h?
> Diving down into the arch layer is a bit unusual.  Doesn't matter, I
> guess.

I chose asm/siginfo.h because other users of siginfo_t also just
include this file and linux/signal.h includes much more than we
actually need...

Thanks,
//richard

  reply	other threads:[~2012-10-10 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 22:04 Richard Weinberger
2012-10-10 22:16 ` Andrew Morton
2012-10-10 22:20   ` Richard Weinberger [this message]
2012-10-10 22:34     ` Roland McGrath

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=20121011002056.09c7c2bb@spider.haslach.nod.at \
    --to=richard@nod.at \
    --cc=akpm@linux-foundation.org \
    --cc=amwang@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=jmfoote@cert.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=palves@redhat.com \
    --cc=roland@hack.frob.com \
    --cc=sfr@canb.auug.org.au \
    --cc=vda.linux@googlemail.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

all inboxes | Powered by JetHome®