Re: [Xen-devel] [PATCH net-next] xen-netfront: clean up code in xennet_release_rx_bufs

[annie li <annie.li@xxxxxxxxxx>]

On 2014-1-15 19:20, David Vrabel wrote:
> On 09/01/14 22:48, Annie Li wrote:
> > Current netfront only grants pages for grant copy, not for grant transfer, so
> > remove corresponding transfer code and add receiving copy code in
> > xennet_release_rx_bufs.
> While netfront only supports a copying backend, I don't see anything
> preventing the backend from retaining mappings to netfront's Rx buffers...
Right. This does not prevent backend from mappings.
Maybe my description is not clear. What I mean here is based on old 
2.6.18 netfront which uses "copying_receiver" to tell netback whether rx 
requires grant copy. Probably changing "grant copy" above into "grant 
access" vs "grant transfer" is more precise. And the 
"gnttab_end_foreign_transfer_ref" is the unnecessary code kept from old 
netfront.
> > Signed-off-by: Annie Li <Annie.li@xxxxxxxxxx>
> > ---
> >   drivers/net/xen-netfront.c |   60 ++-----------------------------------------
> >   1 files changed, 3 insertions(+), 57 deletions(-)
> >
> > diff --git a/drivers/net/xen-netfront.c b/drivers/net/xen-netfront.c
> > index e59acb1..692589e 100644
> > --- a/drivers/net/xen-netfront.c
> > +++ b/drivers/net/xen-netfront.c
> > @@ -1134,78 +1134,24 @@ static void xennet_release_tx_bufs(struct netfront_info 
> > *np)
> >   
> >   static void xennet_release_rx_bufs(struct netfront_info *np)
> >   {
> [...]
> > -               mfn = gnttab_end_foreign_transfer_ref(ref);
> > +               gnttab_end_foreign_access_ref(ref, 0);
> ... the gnttab_end_foreign_access_ref() may then fail and...
>
> >                 gnttab_release_grant_reference(&np->gref_rx_head, ref);
> >                 np->grant_rx_ref[id] = GRANT_INVALID_REF;
> [...]
> > +               kfree_skb(skb);
> ... this could then potentially free pages that the backend still has
> mapped.  If the pages are then reused, this would leak information to
> the backend.
Yes, it is possible. But doing kfree_skb is right thing from netfront 
point of view.
> Since only a buggy backend would result in this, leaking the skbs and
> grant refs would be acceptable here.
This is the same thing for tx side which uses similar process.

>    I would also print an error.
You mean add some print log here? Is it necessary?

Thanks
Annie
> While checking blkfront for how it handles this, it also doesn't appear
> to do the right thing either.
>
> David
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel