From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: net/packet/af_packet.c:{1057,1073}: flags vs. msg->flags
Date: Mon, 10 Nov 2003 13:36:02 +0100 [thread overview]
Message-ID: <3FAF8632.8020906@softhome.net> (raw)
In-Reply-To: <Qifs.Pr.1@gated-at.bofh.it>
RTFM (man recv) brought the response:
MSG_TRUNC
Return the real length of the packet, even when it was longer
than the passed buffer. Only valid for packet sockets.
So packet socket is special case here.
Sorry for disturbing.
P.S. Wondering - is there any way to find a size of next queued
datagram? SIOCINQ? cannot find its description - not listed in man
ioctl_list - but implementation inside of ap_packet.c does exactly this.
Ihar 'Philips' Filipau wrote:
> Hi!
>
> [ I'm trying to cc: netdev - but they are not that welcome - and
> require subscription. I'm way too lazy (and my mail box is not that
> fast) to subscribe to send simple typo - if this is a case at all. ]
>
> [ kernel v2.6.0-test7 as found on lxr.linux.no, 2.4.{18,22} has the
> same - but line numbers are different. ]
>
> On line 1057 we have: "msg->msg_flags|=MSG_TRUNC;" to indicate that
> message was truncated.
>
> But on line 1073, where we make return status to user, we check
> against user suplied flags, but NOT msg->msg_flags.
>
> It looks like obvious typo.
>
--
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
-- _ _ _
"... and for $64000 question, could you get yourself |_|*|_|
vaguely familiar with the notion of on-topic posting?" |_|_|*|
-- Al Viro @ LKML |*|*|*|
next parent reply other threads:[~2003-11-10 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Qifs.Pr.1@gated-at.bofh.it>
2003-11-10 12:36 ` Ihar 'Philips' Filipau [this message]
2003-11-10 11:10 net/packet/af_packet.c:{1057,1073}: flags vs. msg->flags Ihar 'Philips' Filipau
2003-11-11 7:12 ` David S. 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=3FAF8632.8020906@softhome.net \
--to=filia@softhome.net \
--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