From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: missing bit from signal patches
Date: Thu, 30 May 2002 16:16:13 +0200 [thread overview]
Message-ID: <3CF6342D.7060905@loewe-komp.de> (raw)
In-Reply-To: <20020530220828.3c3192cd.sfr@canb.auug.org.au> <20020530232636.09d7b7eb.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Roman,
>
> On Thu, 30 May 2002 14:46:20 +0200 (CEST) Roman Zippel <zippel@linux-m68k.org> wrote:
>
>>On Thu, 30 May 2002, Stephen Rothwell wrote:
>>
>>
>>>Is the following a more ugly hack than yours?
>>>
>>Yes. :)
>>The problem is copy_siginfo(), which wants to access struct siginfo.
>>Copy the m68k version of siginfo.h and try to compile that.
>>
>
> OK, sorry, brain fart :-)
>
> It seems that is an architecture defines its own siginfo_t then it must
> also define its own copy_siginfo function (for now anyway).
>
> Try this ...
>
Why is that done so complicated?
Why not just copy the struct over?
When the kernel generates the signal, I hope the mem is zeroed
and we copy it to user. When a user sends a signal, you want to
prevent sending of arbitrary data? Why is that not done where
the permission check happens?
What do I miss?
next prev parent reply other threads:[~2002-05-30 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 0:18 [PATCH] missing bit from signal patches Stephen Rothwell
2002-05-30 8:04 ` Roman Zippel
2002-05-30 12:08 ` Stephen Rothwell
2002-05-30 12:46 ` Roman Zippel
2002-05-30 13:26 ` Stephen Rothwell
2002-05-30 14:16 ` Peter Wächtler [this message]
2002-05-30 19:57 ` Roman Zippel
2002-05-31 0:24 ` 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=3CF6342D.7060905@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=zippel@linux-m68k.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.