All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samir Bellabes <sam@synack.fr>
To: Joe Damato <joe@boundary.com>
Cc: zbr@ioremap.net, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] Create a new connector proc_event for successful calls to accept.
Date: Wed, 03 Aug 2011 17:02:55 +0200	[thread overview]
Message-ID: <87r55235cw.fsf@synack.fr> (raw)
In-Reply-To: <1312221865-3012-3-git-send-email-joe@boundary.com> (Joe Damato's message of "Mon, 1 Aug 2011 11:04:25 -0700")

Joe Damato <joe@boundary.com> writes:

> diff --git a/net/socket.c b/net/socket.c
> index b4f9a6c..d21a266 100644
> --- a/net/socket.c
> +++ b/net/socket.c
> @@ -1544,6 +1544,9 @@ SYSCALL_DEFINE4(accept4, int, fd, struct sockaddr __user *, upeer_sockaddr,
>  			goto out_fd;
>  	}
>  
> +	proc_accept_connector(current, newsock,
> +			      (struct sockaddr *)&address, len);
> +
>  	/* File flags are not inherited via accept() unlike another OSes. */
>  
>  	fd_install(newfd, newfile);

Hi Joe,
adding a specific function here is not very suitable.
I have already proposed such a patch by adding my own hooks, then I
moved to the LSM hooks
http://www.mail-archive.com/netdev@vger.kernel.org/msg33814.html

I have rewrite the projet to directly use netlink socket (in fact
generic netlink socket) and move to a new protocol between userspace and
kernel
you can find patch here :
http://www.synack.fr/project/snet/snet.html

sam


      reply	other threads:[~2011-08-03 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 18:04 [PATCH 0/2] connector: Add proc_events for connect/accept Joe Damato
2011-08-01 18:04 ` [PATCH 1/2] Create a new connector proc_event for successful calls to connect Joe Damato
2011-08-01 18:04 ` [PATCH 2/2] Create a new connector proc_event for successful calls to accept Joe Damato
2011-08-03 15:02   ` Samir Bellabes [this message]

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=87r55235cw.fsf@synack.fr \
    --to=sam@synack.fr \
    --cc=joe@boundary.com \
    --cc=netdev@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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.