From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Dan Smith <danms@us.ibm.com>
Cc: containers@lists.osdl.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] Set socket flags on restore using sock_setsockopt() where possible (v2)
Date: Mon, 24 Aug 2009 10:48:10 -0700 [thread overview]
Message-ID: <1251136090.22398.7523.camel@nimitz> (raw)
In-Reply-To: <1251134884-24491-2-git-send-email-danms@us.ibm.com>
On Mon, 2009-08-24 at 10:28 -0700, Dan Smith wrote:
>
> +static int sock_restore_flags(struct socket *sock,
> + struct ckpt_hdr_socket *h)
> +{
> + int ret;
> + int v = 1;
> + unsigned long sk_flags = h->sock.flags;
> + unsigned long sock_flags = h->socket.flags;
> +
> + if (test_and_clear_bit(SOCK_URGINLINE, &sk_flags)) {
> + ret = sock_setsockopt(sock, SOL_SOCKET, SO_OOBINLINE,
> + (char *)&v, sizeof(v));
> + if (ret)
> + return ret;
> + }
> +
> + if (test_and_clear_bit(SOCK_KEEPOPEN, &sk_flags)) {
> + ret = sock_setsockopt(sock, SOL_SOCKET, SO_KEEPALIVE,
> + (char *)&v, sizeof(v));
> + if (ret)
> + return ret;
> + }
Would it make more sense to do this programatically?
cr_sock_restore_flag(struct socket *sock, unsigned long sck_flag,
struct ckpt_hdr_socket *h, unsigned long sock_flag)
{
unsigned long sk_flags = h->sock.flags;
unsigned long sock_flags = h->socket.flags;
if (!test_and_clear_bit(sk, &sk_flags))
return 0;
return sock_setsockopt(sock, sock_flag, SO_OOBINLINE,
(char *)&v, sizeof(v));
}
Then, each call becomes:
ret = cr_sock_restore_flag(sock, cr_sock, SOCK_URGINLINE, SO_OOBINLINE);
if (ret)
return ret;
ret = cr_sock_restore_flag(sock, cr_sock, SOCK_KEEPOPEN, SO_KEEPALIVE);
if (ret)
return ret;
Or, you could spell the flags out in a (better named) structure:
struct sock_flagpair
{
unsigned long sock_flag;
unsigned long sk_flag;
}
struct sock_flagpair sock_flagpairs[] = {
{ SOCK_URGINLINE, SO_OOBINLINE },
{ SOCK_KEEPOPEN, SO_KEEPALIVE},
...
};
And just walk through the array to do the restore:
static int sock_restore_flags(struct socket *sock,
struct ckpt_hdr_socket *h)
{
int i;
for (i = 0; i < ARRAY_SIZE(sock_flagpairs); i++) {
int ret;
unsigned long sock_flag = sock_flagpairs[i].sock_flag;
unsigned long sk_flag = sock_flagpairs[i].sk_flag;
ret = cr_sock_restore_flag(sock, cr_sock, sock_flag, sk_flag);
if (ret)
break;
}
...
}
-- Dave
next prev parent reply other threads:[~2009-08-24 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 17:28 Socket C/R additional features Dan Smith
2009-08-24 17:28 ` [PATCH 1/3] Set socket flags on restore using sock_setsockopt() where possible (v2) Dan Smith
2009-08-24 17:48 ` Dave Hansen [this message]
2009-08-24 18:03 ` Dan Smith
2009-08-24 17:28 ` [PATCH 2/3] Expose may_setuid() in user.h and add may_setgid() (v2) Dan Smith
2009-08-25 5:53 ` Oren Laadan
2009-08-24 17:28 ` [PATCH 3/3] Save and restore UNIX socket peer credentials (v2) Dan Smith
2009-08-25 5:54 ` Oren Laadan
-- strict thread matches above, loose matches on Subject: below --
2009-08-18 19:57 Socket C/R additional features Dan Smith
2009-08-18 19:57 ` [PATCH 1/3] Set socket flags on restore using sock_setsockopt() where possible (v2) Dan Smith
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=1251136090.22398.7523.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=danms@us.ibm.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).