public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ovidiu Panait <ovidiu.panait@windriver.com>
Cc: stable@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Halil Pasic <pasic@linux.ibm.com>,
	Oleksandr Natalenko <oleksandr@natalenko.name>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 4.14 2/2] Reinstate some of "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""
Date: Mon, 23 May 2022 18:01:42 +0200	[thread overview]
Message-ID: <Youv5m8L4FmP1zQf@kroah.com> (raw)
In-Reply-To: <20220523154624.1141489-2-ovidiu.panait@windriver.com>

On Mon, May 23, 2022 at 06:46:24PM +0300, Ovidiu Panait wrote:
> From: Linus Torvalds <torvalds@linux-foundation.org>
> 
> commit 901c7280ca0d5e2b4a8929fbe0bfb007ac2a6544 upstream.
> 
> Halil Pasic points out [1] that the full revert of that commit (revert
> in bddac7c1e02b), and that a partial revert that only reverts the
> problematic case, but still keeps some of the cleanups is probably
> better.  
> 
> And that partial revert [2] had already been verified by Oleksandr
> Natalenko to also fix the issue, I had just missed that in the long
> discussion.
> 
> So let's reinstate the cleanups from commit aa6f8dcbab47 ("swiotlb:
> rework "fix info leak with DMA_FROM_DEVICE""), and effectively only
> revert the part that caused problems.
> 
> Link: https://lore.kernel.org/all/20220328013731.017ae3e3.pasic@linux.ibm.com/ [1]
> Link: https://lore.kernel.org/all/20220324055732.GB12078@lst.de/ [2]
> Link: https://lore.kernel.org/all/4386660.LvFx2qVVIh@natalenko.name/ [3]
> Suggested-by: Halil Pasic <pasic@linux.ibm.com>
> Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name>
> Cc: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> [OP: backport to 4.14: apply swiotlb_tbl_map_single() changes in lib/swiotlb.c]
> Signed-off-by: Ovidiu Panait <ovidiu.panait@windriver.com>
> ---
>  Documentation/DMA-attributes.txt | 10 ----------
>  include/linux/dma-mapping.h      |  8 --------
>  lib/swiotlb.c                    | 13 ++++++++-----
>  3 files changed, 8 insertions(+), 23 deletions(-)
> 

Both now queued up, thanks.

greg k-h

      reply	other threads:[~2022-05-23 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 15:46 [PATCH 4.14 1/2] swiotlb: fix info leak with DMA_FROM_DEVICE Ovidiu Panait
2022-05-23 15:46 ` [PATCH 4.14 2/2] Reinstate some of "swiotlb: rework "fix info leak with DMA_FROM_DEVICE"" Ovidiu Panait
2022-05-23 16:01   ` Greg KH [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=Youv5m8L4FmP1zQf@kroah.com \
    --to=greg@kroah.com \
    --cc=hch@lst.de \
    --cc=oleksandr@natalenko.name \
    --cc=ovidiu.panait@windriver.com \
    --cc=pasic@linux.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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