netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] xfrm: x86_64 CONFIG_COMPAT support
Date: Thu, 04 Feb 2010 20:22:35 -0800 (PST)	[thread overview]
Message-ID: <20100204.202235.186522102.davem@davemloft.net> (raw)
In-Reply-To: <20100205014744.GD28659@Chamillionaire.breakpoint.cc>

From: Florian Westphal <fw@strlen.de>
Date: Fri, 5 Feb 2010 02:47:44 +0100

> Unfortunately, the MSG_COMPAT flag seems to get lost along
> the way, so this uses x86_64 is_compat_task() for now.

You can't use is_compat_task() for this.  The current
execution context is not always the same as who is
going to get the message.

This is particularly the case for broadcast events, and
key manager event sending.

The wireless folks have their netlink bits working with
compat programs, you should go see how it works there.

  reply	other threads:[~2010-02-05  4:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  1:47 [RFC] xfrm: x86_64 CONFIG_COMPAT support Florian Westphal
2010-02-05  4:22 ` David Miller [this message]
2010-02-05 19:54   ` Florian Westphal
2010-02-05 19:59     ` David Miller
2010-02-05 21:13       ` Florian Westphal

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=20100204.202235.186522102.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).