[Devel] Re: [PATCH 2/2] [RFC] Add c/r support for connected INET sockets
Dan Smith
danms at us.ibm.com
Wed Oct 7 10:22:26 PDT 2009
>> + CKPT_COPY(op, hh->daddr, sk->daddr);
>> + CKPT_COPY(op, hh->rcv_saddr, sk->rcv_saddr);
>> + CKPT_COPY(op, hh->dport, sk->dport);
>> + CKPT_COPY(op, hh->num, sk->num);
>> + CKPT_COPY(op, hh->saddr, sk->saddr);
>> + CKPT_COPY(op, hh->sport, sk->sport);
SH> This becomes an easy way around CAP_NET_BIND_SERVICE right? Or
SH> will that be caught by something already done in your listen patch
SH> after this step?
Actually, yeah, you're right. I was going to say that we'd catch it
because we also do a bind(), but there's no guarantee that the
sockaddr_in we use for bind() is the same as this :D
--
Dan Smith
IBM Linux Technology Center
email: danms at us.ibm.com
_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
More information about the Devel
mailing list