From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Smith Subject: Re: [PATCH 3/4] Update the UNIX buffer restore code to match the new format saved in the image file Date: Wed, 18 Nov 2009 06:28:02 -0800 Message-ID: <876397vrf1.fsf@caffeine.danplanet.com> References: <1258471590-29768-1-git-send-email-danms@us.ibm.com> <1258471590-29768-4-git-send-email-danms@us.ibm.com> <20091118043920.GD19841@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20091118043920.GD19841-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> (Serge E. Hallyn's message of "Tue\, 17 Nov 2009 22\:39\:20 -0600") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Serge E. Hallyn" Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org List-Id: containers.vger.kernel.org sk-> sk_sndbuf = sysctl_wmem_max; SH> Again, should you check whether h->len_len < sysctl_wmem_max SH> before doing the capable(CAP_NET_ADMIN)? The goal is to prevent SH> setting PF_SUPERPRIV in task->flags if it wasn't absolutely SH> necessary. Yes, I think we agreed that we should, I just wasn't going to fold that into these other unrelated changes. I'll spin another small patch for that right away. -- Dan Smith IBM Linux Technology Center email: danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org