From: David Miller <davem@davemloft.net>
To: gregory.v.rose@intel.com
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] rtnetlink: Fix problem with buffer allocation
Date: Fri, 10 Feb 2012 14:24:52 -0500 (EST) [thread overview]
Message-ID: <20120210.142452.2227318248629247303.davem@davemloft.net> (raw)
In-Reply-To: <C5551D9AAB213A418B7FD5E4A6F30A0702F88CF8@ORSMSX106.amr.corp.intel.com>
From: "Rose, Gregory V" <gregory.v.rose@intel.com>
Date: Fri, 10 Feb 2012 19:07:15 +0000
> OK, sounds good. How about I also add a field to indicate the
> application buffer size?
How can this help, we already have it. It's the length field to
the recvmsg() call.
Also, either the user provided a large enough buffer or he didn't. If
he didn't we return an error to the recvmsg() call, and the user can
increase the buffer size and try again.
next prev parent reply other threads:[~2012-02-10 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 15:05 [RFC PATCH] rtnetlink: Fix problem with buffer allocation Greg Rose
2012-02-10 18:51 ` David Miller
2012-02-10 19:07 ` Rose, Gregory V
2012-02-10 19:24 ` David Miller [this message]
2012-02-10 19:30 ` Rose, Gregory V
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=20120210.142452.2227318248629247303.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gregory.v.rose@intel.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 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).