All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dlstevens@us.ibm.com
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org,
	netdev-owner@vger.kernel.org
Subject: Re: [GIT PULL] [IPV6] COMPAT: Fix SSM applications on 64bit kernels.
Date: Thu, 24 Apr 2008 23:31:59 -0700 (PDT)	[thread overview]
Message-ID: <20080424.233159.06679047.davem@davemloft.net> (raw)
In-Reply-To: <OF3A37018B.9EFE360C-ON88257435.00614684-88257435.00622448@us.ibm.com>

From: David Stevens <dlstevens@us.ibm.com>
Date: Thu, 24 Apr 2008 11:52:01 -0600

> I was looking at this problem too, and below is what I have at the
> moment. I've only tested the group_req portion, and I was looking
> at putting this in net/compat.c with hooks back, since the code is
> literally identical for IPv4 except the sockopt function you call at
> the end, but I've moved it to ipv6_sockglue.c for this patch.
> 
> This touches a lot less code and I think comes out a lot smaller.
> 
> Method is to translate to padded version on the user stack, make
> the call, and translate back (in the MSFILTER case) on return, as
> is done for some other compat functions.

I've looked at both approaches.

David's might be the better way to do this, as an initial
approximation.

I think we can combine ideas from both implementations, so why don't
we do the following:

1) Use copy_in_user() as that's the proper interaface to copy within
   userspace in COMPAT code.

2) Use aligned(4) attribute instead of packed, this will help RISC
   compat systems a lot

If you make these changes and do some testing, I think this is the
patch I will apply.

Thanks.

  parent reply	other threads:[~2008-04-25  6:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24  8:02 [GIT PULL] [IPV6] COMPAT: Fix SSM applications on 64bit kernels YOSHIFUJI Hideaki / 吉藤英明
2008-04-24  8:08 ` David Miller
2008-04-24  8:16   ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-24  8:49     ` David Miller
2008-04-24  9:28       ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-24  9:35         ` David Miller
2008-04-24 18:46     ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-24 20:01       ` David Stevens
2008-04-24 20:43         ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-24 20:59           ` David Stevens
2008-04-24 17:52 ` David Stevens
2008-04-25  5:38   ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-25  6:23     ` David Stevens
2008-04-25  6:27       ` David Miller
2008-04-25  6:31   ` David Miller [this message]
2008-04-25  6:37     ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-25  6:47       ` David Miller
2008-04-25  6:59         ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-25  7:04           ` David Miller
2008-04-25  7:24             ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-26  0:24               ` David Stevens
2008-04-26  3:33                 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-26  4:36                   ` David Stevens
2008-04-26  4:53                     ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-26  5:32                       ` David Miller
2008-04-26  5:56                         ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-26  6:01                           ` David Miller
2008-04-26  6:25                             ` David Stevens
2008-04-26  6:31                               ` David Miller
2008-04-26  7:13                                 ` David Stevens
2008-04-26  9:07                                   ` David Miller
2008-04-26  5:09                     ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-26  5:31                     ` David Miller
2008-04-26  7:00                       ` David Stevens
2008-04-26  7:09                         ` David Miller
2008-04-26 23:55                   ` David Stevens
2008-04-27  8:06                     ` David Miller
2008-04-26  5:14                 ` YOSHIFUJI Hideaki / 吉藤英明
2008-04-26  5:33                   ` David Miller

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=20080424.233159.06679047.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev-owner@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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.