[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120814100522.GL4177@suse.de>
Date: Tue, 14 Aug 2012 11:05:22 +0100
From: Mel Gorman <mgorman@...e.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc: David Miller <davem@...emloft.net>,
Ian Campbell <Ian.Campbell@...citrix.com>,
xen-devel@...ts.xensource.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
konrad@...nok.org, akpm@...ux-foundation.org
Subject: Re: [Xen-devel] [PATCH] netvm: check for page == NULL when
propogating the skb->pfmemalloc flag
On Mon, Aug 13, 2012 at 11:41:44AM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Aug 08, 2012 at 03:50:46PM -0700, David Miller wrote:
> > From: Mel Gorman <mgorman@...e.de>
> > Date: Tue, 7 Aug 2012 09:55:55 +0100
> >
> > > Commit [c48a11c7: netvm: propagate page->pfmemalloc to skb] is responsible
> > > for the following bug triggered by a xen network driver
> > ...
> > > The problem is that the xenfront driver is passing a NULL page to
> > > __skb_fill_page_desc() which was unexpected. This patch checks that
> > > there is a page before dereferencing.
> > >
> > > Reported-and-Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
> > > Signed-off-by: Mel Gorman <mgorman@...e.de>
> >
> > That call to __skb_fill_page_desc() in xen-netfront.c looks completely bogus.
> > It's the only driver passing NULL here.
>
> It looks to be passing a valid page pointer (at least by looking
> at the code) so I am not sure how it got turned in a NULL.
>
Are we looking at different code bases? I see this and I was assuming it
was the source of the bug.
__skb_fill_page_desc(skb, 0, NULL, 0, 0);
--
Mel Gorman
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists