From: David Miller <davem@davemloft.net>
To: penguin-kernel@I-love.SAKURA.ne.jp
Cc: eric.dumazet@gmail.com, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
paul.moore@hp.com, netdev@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] LSM: Add post recvmsg() hook.
Date: Sun, 18 Jul 2010 14:25:50 -0700 (PDT) [thread overview]
Message-ID: <20100718.142550.25115105.davem@davemloft.net> (raw)
In-Reply-To: <201007181949.IFC00070.OMHQVSFOLJFFOt@I-love.SAKURA.ne.jp>
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: Sun, 18 Jul 2010 19:49:11 +0900
> Eric Dumazet wrote:
>> I read this patch and could not find out if an SNMP counter was
>> increased in the case a frame was not delivered but dropped in kernel
>> land.
>
> UDP_MIB_INDATAGRAMS and UDP_MIB_INERRORS will not be increased
> if dropped by security_socket_post_recvmsg()'s decision.
> Should we increment UDP_MIB_INDATAGRAMS and/or UDP_MIB_INERRORS?
This decision should be guided by what we do for in the case
of the other existing security hooks.
I don't think it makes any sense to make the post recvmsg() hook
behave any differently from the existing hooks in this regard.
next prev parent reply other threads:[~2010-07-18 21:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 16:14 [RFC] LSM hook for post recvmsg Tetsuo Handa
2010-07-16 19:35 ` David Miller
2010-07-17 1:17 ` [PATCH] LSM: Add post recvmsg() hook Tetsuo Handa
2010-07-17 20:34 ` Paul Moore
2010-07-18 8:33 ` Eric Dumazet
2010-07-18 10:49 ` Tetsuo Handa
2010-07-18 21:25 ` David Miller [this message]
2010-07-19 4:25 ` [PATCH] LSM: Add post accept() hook Tetsuo Handa
2010-07-19 22:15 ` Paul Moore
2010-07-20 1:36 ` Tetsuo Handa
2010-07-20 19:52 ` Paul Moore
2010-07-21 2:00 ` Tetsuo Handa
2010-07-21 16:06 ` Paul Moore
2010-07-21 18:45 ` [PATCH] LSM: Add post recvmsg() hook David Miller
2010-07-22 3:38 ` Tetsuo Handa
2010-07-22 4:06 ` David Miller
2010-07-22 4:41 ` Tetsuo Handa
2010-07-22 4:45 ` David Miller
2010-07-22 5:02 ` Tetsuo Handa
2010-07-22 5:06 ` David Miller
2010-07-22 12:46 ` Tetsuo Handa
2010-07-22 17:22 ` David Miller
2010-07-22 17:26 ` David Miller
2010-07-23 0:22 ` Tetsuo Handa
2010-07-23 5:44 ` David Miller
2010-07-23 7:21 ` Tetsuo Handa
2010-07-23 7:29 ` David Miller
2010-07-23 12:37 ` Tetsuo Handa
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=20100718.142550.25115105.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=pekkas@netcore.fi \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=yoshfuji@linux-ipv6.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).