From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH] Fix guest memory leak and panic Date: Tue, 18 Oct 2011 11:50:55 +0100 Message-ID: <1318935055.3385.0.camel@zakaz.uk.xensource.com> References: <20111018080523.16861.55402.sendpatchset@krkumar2.in.ibm.com> <1318927016.16132.49.camel@zakaz.uk.xensource.com> <1318931232.16132.65.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: "davem@davemloft.net" , "linux-kernel@vger.kernel.org" , "mst@redhat.com" , "netdev@vger.kernel.org" , "rusty@rustcorp.com.au" , "virtualization@lists.linux-foundation.org" To: Krishna Kumar2 Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tue, 2011-10-18 at 11:46 +0100, Krishna Kumar2 wrote: > Ian Campbell wrote on 10/18/2011 03:17:11 PM: > > > > I think the best thing might be to remove the additional ref taking > from > > > the setter function and audit the previous changes to ensure they > > > conform. I'll do that right away and post a fixup patch ASAP. > > > > Sigh, only one out of the ten callers of (__)skb_frag_set_page expects > > skb_frag_set_page to take a new reference. I think that's pretty > > comprehensive evidence that the current behaviour is unexpected and > > wrong. > > Looks good! Thanks. > Does it make sense to commit both of these patches? The > reason being - my patch becomes a cleanup of set_skb_frag() > in virtio_net driver. I think your patch remains a valid cleanup but I don't maintain that code. Ian.