From: Roland Dreier <roland@topspin.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "David S. Miller" <davem@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RFC] increase MAX_ADDR_LEN
Date: 12 Nov 2002 12:36:10 -0800 [thread overview]
Message-ID: <52adkele4l.fsf@topspin.com> (raw)
In-Reply-To: <1037116836.8500.55.camel@irongate.swansea.linux.org.uk>
>>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
Alan> 1. Increase MAX_ADDR_LEN 2. Add some new address setting
Alan> ioctls, and ensure the old ones keep the old address length
Alan> limit. That is needed because the old caller wont have
Alan> allocated enough address space for a 20 byte address return.
Thanks to YOSHIFUJI Hideaki / 吉藤英明, I had a look at rtnetlink. It
seems like we would get the necessary address setting functionality if
I implemented the following:
1. Add an RTM_SETLINK message type that handles at least the
IFLA_ADDRESS attribute. This would replace SIOCSIFHWADDR for
interfaces with long hardware addresses.
2. Add code to handle receiving RTM_NEWNEIGH and RTM_DELNEIGH
messages from user space. This would replace SIOCSARP and
SIOCDARP for interfaces with long hardware addresses.
Dave, Alan, if I wrote a patch to do this would you accept it? (And
following that increase MAX_ADDR_LEN?)
(By the way the original patch I posted added code to the
SIOCSIFHWADDR/SIOCGIFHWADDR handler to prevent a long hardware address
from overrunning the ifr_data member that user space passed in)
Thanks,
Roland
next prev parent reply other threads:[~2002-11-12 20:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 18:25 [PATCH] flush_cache_page while pte valid Hugh Dickins
2002-11-11 18:35 ` Andrew Morton
2002-11-11 23:19 ` David S. Miller
2002-11-11 23:34 ` [PATCH] [RFC] increase MAX_ADDR_LEN Roland Dreier
2002-11-11 23:38 ` David S. Miller
2002-11-11 23:58 ` Roland Dreier
2002-11-12 0:18 ` Alan Cox
2002-11-12 0:01 ` Roland Dreier
2002-11-12 14:23 ` Alan Cox
2002-11-12 14:20 ` Folkert van Heusden
2002-11-12 15:14 ` Roland Dreier
2002-11-12 16:00 ` Alan Cox
2002-11-12 15:50 ` YOSHIFUJI Hideaki / 吉藤英明
2002-11-12 20:36 ` Roland Dreier [this message]
2002-11-12 22:31 ` David S. Miller
2002-11-12 22:39 ` Roland Dreier
2002-12-04 18:31 ` rtnetlink replacement for SIOCSIFHWADDR Roland Dreier
2002-12-04 20:11 ` Andi Kleen
2002-12-31 23:11 ` [PATCH] increase MAX_ADDR_LEN Roland Dreier
2003-01-06 15:52 ` [PATCH] increase MAX_ADDR_LEN (resend) Roland Dreier
2003-01-06 23:29 ` David S. Miller
2003-01-07 8:58 ` [PATCH] increase MAX_ADDR_LEN David S. Miller
2002-11-12 6:53 ` [PATCH] flush_cache_page while pte valid Hugh Dickins
2002-11-12 6:53 ` David S. Miller
2002-11-12 14:49 ` Rik van Riel
2002-11-12 21:45 ` David S. Miller
2002-11-12 17:43 ` Hugh Dickins
2002-11-12 21:51 ` David S. Miller
2002-11-12 22:59 ` Hugh Dickins
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=52adkele4l.fsf@topspin.com \
--to=roland@topspin.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome