All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Joerg M. Sigle" <joerg.sigle@jsigle.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] iommu/vt-d: Fix kernel panic caused by 416fa531c816: Preset Access/Dirty bits for IOVA over FL
Date: Thu, 20 May 2021 10:52:54 +0200	[thread overview]
Message-ID: <YKYjZivpfGivHqps@kroah.com> (raw)
In-Reply-To: <7827b043-7abe-de56-2a46-19d689f34120@jsigle.com>

On Thu, May 20, 2021 at 09:47:40AM +0200, Joerg M. Sigle wrote:
> Dear colleaguse
> 
> I've submitted a patch for 5.10.37 that wasn't included in 5.10.38,
> which would have corrected a patch that has been reverted instead.
> 
> More info:
> https://bugzilla.kernel.org/show_bug.cgi?id=213077
> 
> Now sending to the other kernel list, according to autoresponse
> from Greg Kroah-Hartman.
> 
> Thanks for any feedback & Kind regards, Joerg Sigle

Are you sure that 5.10.38 doesn't already fix this issue?  We resolved
an issue in this area.

And where is the patch, I can't find it in this email, can you submit it
"properly" so that it can be reviewed?

thanks,

greg k-h

      reply	other threads:[~2021-05-20  8:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-213077-5531-kGNQn2oCe1@https.bugzilla.kernel.org/>
     [not found] ` <8f485610-7560-239f-207b-cda3234869f2@jsigle.com>
     [not found]   ` <041d48f5-0c3c-a435-1980-33492c377e8b@linux.intel.com>
2021-05-17  6:49     ` [PATCH] iommu/vt-d: Fix kernel panic caused by 416fa531c816: Preset Access/Dirty bits for IOVA over FL Joerg M. Sigle
2021-05-20  7:47       ` Joerg M. Sigle
2021-05-20  8:52         ` 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=YKYjZivpfGivHqps@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=joerg.sigle@jsigle.com \
    --cc=stable@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 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.