netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: chrisw@sous-sol.org, netdev@vger.kernel.org
Subject: Re: IPV6: make ipv6_getsockopt_sticky honor user's buffer size
Date: Thu, 08 Mar 2007 17:11:50 -0800 (PST)	[thread overview]
Message-ID: <20070308.171150.38709664.davem@davemloft.net> (raw)
In-Reply-To: <20070309.094932.11513849.yoshfuji@linux-ipv6.org>

From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date: Fri, 09 Mar 2007 09:49:32 +0900 (JST)

> We should give truncated result and return full length
> from the POSIX POV.

True, and the user would know what happened because it
knows both the original length it gave and the larger
one the kernel gave as the return value.

      reply	other threads:[~2007-03-09  1:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08  7:10 IPV6: make ipv6_getsockopt_sticky honor user's buffer size Chris Wright
2007-03-08 22:38 ` David Miller
2007-03-09  0:49   ` YOSHIFUJI Hideaki / 吉藤英明
2007-03-09  1:11     ` David Miller [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=20070308.171150.38709664.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=chrisw@sous-sol.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 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).