All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: "David S. Miller" <davem@davemloft.net>,
	Linux Network Development list <netdev@vger.kernel.org>
Subject: question on netlink_overrun()
Date: Wed, 04 Mar 2009 19:18:41 -0600	[thread overview]
Message-ID: <49AF2871.10804@nortel.com> (raw)

Hi all,

Currently we set netlink_overrun() on the socket in both the unicast and 
broadcast paths.  If I understand things correctly this should result in 
the receiver getting ENOBUFS the next time they try a socket-related 
syscall.

However, in the netlink_dump() code we don't call it--was this an 
oversight or an intentional design decision?

I have a userspace app that would like to know if it ran out of buffer 
space in the receive socket (and hence lost some packets) while dumping 
SA information in xfrm_user_rcv_msg().

Thanks,

Chris

             reply	other threads:[~2009-03-05  1:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05  1:18 Chris Friesen [this message]
2009-03-05  5:56 ` question on netlink_overrun() Patrick McHardy

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=49AF2871.10804@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=davem@davemloft.net \
    --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.