All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Brent Casavant <bcasavan@sgi.com>
Cc: netdev@vger.kernel.org
Subject: Re: AF_UNIX MSG_PEEK bug?
Date: Wed, 9 Jan 2008 19:05:56 -0800	[thread overview]
Message-ID: <20080109190556.468cbd6c@deepthought> (raw)
In-Reply-To: <alpine.BSF.1.00.0801092031290.35527@pkunk.americas.sgi.com>


> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index 060bba4..2ffdf5b 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -50,6 +50,9 @@
>   *	     Arnaldo C. Melo	:	Remove MOD_{INC,DEC}_USE_COUNT,
>   *	     				the core infrastructure is doing that
>   *	     				for all net proto families now (2.5.69+)
> + *		Brent Casavant	:	SOCK_STREAM MSG_PEEK should peek
> + *					far enough ahead to satisfy the request
> + *					rather than stop after the first skb.
>   *
>   *

The kernel doesn't use comments as a changlog anymore, that was so last century.


-- 
Stephen Hemminger <stephen.hemminger@vyatta.com>

  reply	other threads:[~2008-01-10  3:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 22:27 AF_UNIX MSG_PEEK bug? Brent Casavant
2008-01-08 22:40 ` Rick Jones
2008-01-08 22:53   ` Tom Spink
2008-01-08 23:18     ` Brent Casavant
2008-01-08 23:39       ` Tom Spink
2008-01-08 23:46         ` Tom Spink
2008-01-09  0:08           ` Brent Casavant
2008-01-08 23:20   ` Brent Casavant
2008-01-09 11:04 ` Tetsuo Handa
2008-01-09 18:01   ` Brent Casavant
2008-01-10  0:01     ` Herbert Xu
2008-01-10  1:19       ` Brent Casavant
2008-01-10  2:50       ` Brent Casavant
2008-01-10  3:05         ` Stephen Hemminger [this message]
2008-01-10 22:35         ` Brent Casavant
2008-01-10 22:36           ` Alan Cox

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=20080109190556.468cbd6c@deepthought \
    --to=shemminger@linux-foundation.org \
    --cc=bcasavan@sgi.com \
    --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 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.