All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: nic_swsd@realtek.com, kuba@kernel.org, davem@davemloft.net,
	netdev@vger.kernel.org, paulb@blazebox.homeip.net
Subject: Re: [PATCH net] r8169: fix DMA being used after buffer free if WoL is enabled
Date: Sun, 21 Mar 2021 02:10:08 +0000	[thread overview]
Message-ID: <161629260876.5230.4981674636008267669.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ed72d614-d6a2-a837-8faa-eaaef08ef6d8@gmail.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Sat, 20 Mar 2021 21:40:08 +0100 you wrote:
> IOMMU errors have been reported if WoL is enabled and interface is
> brought down. It turned out that the network chip triggers DMA
> transfers after the DMA buffers have been freed. For WoL to work we
> need to leave rx enabled, therefore simply stop the chip from being
> a DMA busmaster.
> 
> Fixes: 567ca57faa62 ("r8169: add rtl8169_up")
> Tested-by: Paul Blazejowski <paulb@blazebox.homeip.net>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> 
> [...]

Here is the summary with links:
  - [net] r8169: fix DMA being used after buffer free if WoL is enabled
    https://git.kernel.org/netdev/net/c/f658b90977d2

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-03-21  2:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20 20:40 [PATCH net] r8169: fix DMA being used after buffer free if WoL is enabled Heiner Kallweit
2021-03-21  2:10 ` patchwork-bot+netdevbpf [this message]

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=161629260876.5230.4981674636008267669.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=paulb@blazebox.homeip.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.