LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Tom Spink" <tspink@gmail.com>
To: "Rick Jones" <rick.jones2@hp.com>
Cc: "Brent Casavant" <bcasavan@sgi.com>,
netdev@vger.kernel.org, "David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: AF_UNIX MSG_PEEK bug?
Date: Tue, 8 Jan 2008 22:53:59 +0000 [thread overview]
Message-ID: <7b9198260801081453s198af7efycc7c35668c65eaf1@mail.gmail.com> (raw)
In-Reply-To: <4783FBD6.1000004@hp.com>
On 08/01/2008, Rick Jones <rick.jones2@hp.com> wrote:
> Potential bugs notwithstanding, given that this is a STREAM socket, and
> as such shouldn't (I hope, or I'm eating toes for dinner again) have
> side effects like tossing the rest of a datagram, why are you using
> MSG_PEEK? Why not simply read the N bytes of the message that will have
> the message length with a normal read/recv, and then read that many
> bytes in the next call?
>
> rick jones
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hi,
Where in the code is the message length being sent across the socket?
--
Regards,
Tom Spink
University of Edinburgh
next prev parent reply other threads:[~2008-01-08 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 22:27 Brent Casavant
2008-01-08 22:40 ` Rick Jones
2008-01-08 22:53 ` Tom Spink [this message]
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 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=7b9198260801081453s198af7efycc7c35668c65eaf1@mail.gmail.com \
--to=tspink@gmail.com \
--cc=bcasavan@sgi.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--subject='Re: AF_UNIX MSG_PEEK bug?' \
/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
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).