From: David Miller <davem@davemloft.net>
To: ashiduka@jp.fujitsu.com
Cc: fugang.duan@nxp.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: fec: Fixed panic problem with non-tso
Date: Tue, 17 Jan 2017 15:45:12 -0500 (EST) [thread overview]
Message-ID: <20170117.154512.612465430064515761.davem@davemloft.net> (raw)
In-Reply-To: <20170117074820.5106-1-ashiduka@jp.fujitsu.com>
From: Yuusuke Ashiduka <ashiduka@jp.fujitsu.com>
Date: Tue, 17 Jan 2017 16:48:20 +0900
> If highmem and 2GB or more of memory are valid,
> "this_frag-> page.p" indicates the highmem area,
> so the result of page_address() is NULL and panic occurs.
>
> This commit fixes this by using the skb_frag_dma_map() helper,
> which takes care of mapping the skb fragment properly. Additionally,
> the type of mapping is now tracked, so it can be unmapped using
> dma_unmap_page or dma_unmap_single when appropriate.
This patch submission is lacking a proper signoff.
next prev parent reply other threads:[~2017-01-17 20:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 7:48 [PATCH] net: fec: Fixed panic problem with non-tso Yuusuke Ashiduka
2017-01-17 11:02 ` Andy Duan
2017-01-18 3:12 ` Ashizuka, Yuusuke
2017-01-18 4:21 ` Eric Dumazet
2017-01-18 4:35 ` Eric Dumazet
2017-01-18 18:18 ` Pravin Shelar
2017-01-18 19:51 ` Eric Dumazet
2017-01-18 20:12 ` [PATCH net] net: fix harmonize_features() vs NETIF_F_HIGHDMA Eric Dumazet
2017-01-18 20:25 ` David Miller
2017-01-19 8:18 ` [PATCH] net: fec: Fixed panic problem with non-tso Andy Duan
2017-01-19 13:24 ` Eric Dumazet
2017-01-17 20:45 ` David Miller [this message]
2017-01-18 3:20 ` Ashizuka, Yuusuke
2017-01-18 4:11 ` [PATCH v2] " Yuusuke Ashiduka
2017-01-18 5:02 ` Eric Dumazet
2017-01-18 5:38 ` Andy Duan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170117.154512.612465430064515761.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ashiduka@jp.fujitsu.com \
--cc=fugang.duan@nxp.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox