netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Smith <danms@us.ibm.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: containers@lists.osdl.org, netdev@vger.kernel.org,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [PATCH 5/5] c/r: Add AF_UNIX support (v8)
Date: Mon, 10 Aug 2009 14:06:47 -0700	[thread overview]
Message-ID: <87fxbz5qfs.fsf@caffeine.danplanet.com> (raw)
In-Reply-To: <20090810210235.GB24373@us.ibm.com> (Serge E. Hallyn's message of "Mon\, 10 Aug 2009 16\:02\:35 -0500")

SH> Thanks, Dan.  Apart from the double-free on error case in
SH> sock_copy_buffers(), this looks very good to me.  So with that
SH> change, please feel free to add:

Okay, thanks, I've got that fixed up now.

SH> Dan, do you have any testcases (even just descriptions of how to
SH> test, which i'll then try to script) i can add to cr_tests?

Yeah, I've got a big ugly test program that I've rolled automatic
tests for most scenarios into.  Here's the usage output of the test.
I'll get it cleaned up and posted too:

  Usage: ./testprog [-t (s|d)] [-wn] TEST
  Where:
    -t s, -t d:             Select STREAM or DGRAM sockets
    -w:                     Wait for a response before restarting
    -n:                     Don't terminate the test on successful restart
  
  Where TEST is one of:
    --unix_pair:            Pair of sockets using socketpair()
    --unix_unlinked:        Listen socket with an unlinked path
    --unix_pair_path:       Pair of sockets using paths
    --unix_pair_abstract:   Pair of sockets using abstract names
    --unix_inflight:        Pair of sockets with data in flight
    --unix_inflight_closed: Pair of sockets, one side closed after preflight
    --unix_midaccept:       Listen socket with unaccepted peer
    --unix_fdpass:          Attempt to pass an FD
    --unix_passcred:        Attempt to pass credentials
    --unix_path:            Post-restart path-based connect to listen socket
    --unix_abstract:        Post-restart abstract connect to listen socket
    --unix_path_unlink:     Like pair_path, but unlink socket before restart
    --unix_deadpeer:        Close peer socket with data in flight
    --unix_testopt:         Unix socket setting and testing for a sockopt
    --unix_anoninflight:    Inflight data with unconnected DGRAM sockets
    --inet_connected:       Pair of localhost INET4 sockets
    --inet6_connected:      Pair of localhost INET6 sockets
    --nonet:                No network, just a simple loop
    --sendmail:             Try to start up sendmail and checkpoint it

-- 
Dan Smith
IBM Linux Technology Center
email: danms@us.ibm.com

  reply	other threads:[~2009-08-10 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1249918379-29414-1-git-send-email-danms@us.ibm.com>
2009-08-10 15:32 ` [PATCH 3/5] Add common socket helpers to unify the security hooks Dan Smith
2009-08-10 15:32 ` [PATCH 5/5] c/r: Add AF_UNIX support (v8) Dan Smith
2009-08-10 21:02   ` Serge E. Hallyn
2009-08-10 21:06     ` Dan Smith [this message]
2009-08-12 15:29   ` Oren Laadan
2009-08-12 15:36     ` Dan Smith
2009-08-12 19:19       ` Oren Laadan

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=87fxbz5qfs.fsf@caffeine.danplanet.com \
    --to=danms@us.ibm.com \
    --cc=adobriyan@gmail.com \
    --cc=containers@lists.osdl.org \
    --cc=netdev@vger.kernel.org \
    --cc=serue@us.ibm.com \
    /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).