All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: ak@suse.de, hch@lst.de, akpm@osdl.org,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 3/3] sanitize building of fs/compat_ioctl.c
Date: Wed, 14 Dec 2005 03:40:37 +0100	[thread overview]
Message-ID: <20051214024037.GC23384@wotan.suse.de> (raw)
In-Reply-To: <20051213.182340.102535288.davem@davemloft.net>

> I suppose.  We could also funnel down ->compat_{read,write}() and
> so on down the call chain, but that would likely be even uglier.

The problem is that this would need to be done for all variants
(write, writev, aio_write, send{,msg,to} etc.) Same for read. I probably forgot
one or two. 


> I guess with is_compat_task() we can do the netlink and pfkeyv2 compat
> stuff on ia64/x86_64.  I don't look forward to reviewing a patch
> implementing that, however :-/

And iptables, although that would be probably *really* ugly.
It's a bit of a sore spot on x86-64 though. 64bit kernel with full
32bit userland works usually great except for iptables and ipsec.

-Andi

      reply	other threads:[~2005-12-14  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13 17:23 [PATCH 3/3] sanitize building of fs/compat_ioctl.c Christoph Hellwig
2005-12-13 17:34 ` Matthew Wilcox
2005-12-13 22:51   ` David S. Miller
2005-12-13 22:53     ` Matthew Wilcox
2005-12-13 23:00       ` David S. Miller
2005-12-14  1:41     ` Andi Kleen
2005-12-14  2:23       ` David S. Miller
2005-12-14  2:40         ` Andi Kleen [this message]

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=20051214024037.GC23384@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=hch@lst.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@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 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.