All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Kees Cook" <keescook@chromium.org>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"John Hubbard" <jhubbard@nvidia.com>,
	"Jérôme Glisse" <jglisse@redhat.com>, "Jan Kara" <jack@suse.cz>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, linux-media@vger.kernel.org,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/2] pci sysfs file iomem revoke support
Date: Mon, 8 Feb 2021 06:43:57 +1100	[thread overview]
Message-ID: <20210208064357.29b3df55@canb.auug.org.au> (raw)
In-Reply-To: <20210204165831.2703772-1-daniel.vetter@ffwll.ch>

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

Hi Daniel,

On Thu,  4 Feb 2021 17:58:29 +0100 Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> Hi all,
> 
> This is a revised version of patch 12 from my series to lock down some
> follow_pfn vs VM_SPECIAL races:
> 
> https://lore.kernel.org/dri-devel/CAKwvOdnSrsnTgPEuQJyaOTSkTP2dR9208Y66HQG_h1e2LKfqtw@mail.gmail.com/
> 
> Stephen reported an issue on HAVE_PCI_LEGACY platforms which this patch
> set tries to address. Previous patches are all still in linux-next.
> 
> Stephen, would be awesome if you can give this a spin.

OK, I applied the 2 patches on top of next-20210205 and it no longer
panics for my simple boot test (PowerPC pseries_le_defconfig under
qemu).

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: linux-samsung-soc@vger.kernel.org, "Jan Kara" <jack@suse.cz>,
	"Kees Cook" <keescook@chromium.org>,
	linux-mm@kvack.org, "John Hubbard" <jhubbard@nvidia.com>,
	linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Dan Williams" <dan.j.williams@intel.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 0/2] pci sysfs file iomem revoke support
Date: Mon, 8 Feb 2021 06:43:57 +1100	[thread overview]
Message-ID: <20210208064357.29b3df55@canb.auug.org.au> (raw)
In-Reply-To: <20210204165831.2703772-1-daniel.vetter@ffwll.ch>


[-- Attachment #1.1: Type: text/plain, Size: 726 bytes --]

Hi Daniel,

On Thu,  4 Feb 2021 17:58:29 +0100 Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> Hi all,
> 
> This is a revised version of patch 12 from my series to lock down some
> follow_pfn vs VM_SPECIAL races:
> 
> https://lore.kernel.org/dri-devel/CAKwvOdnSrsnTgPEuQJyaOTSkTP2dR9208Y66HQG_h1e2LKfqtw@mail.gmail.com/
> 
> Stephen reported an issue on HAVE_PCI_LEGACY platforms which this patch
> set tries to address. Previous patches are all still in linux-next.
> 
> Stephen, would be awesome if you can give this a spin.

OK, I applied the 2 patches on top of next-20210205 and it no longer
panics for my simple boot test (PowerPC pseries_le_defconfig under
qemu).

-- 
Cheers,
Stephen Rothwell

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: linux-samsung-soc@vger.kernel.org, "Jan Kara" <jack@suse.cz>,
	"Kees Cook" <keescook@chromium.org>,
	linux-mm@kvack.org, "John Hubbard" <jhubbard@nvidia.com>,
	linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Dan Williams" <dan.j.williams@intel.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 0/2] pci sysfs file iomem revoke support
Date: Mon, 8 Feb 2021 06:43:57 +1100	[thread overview]
Message-ID: <20210208064357.29b3df55@canb.auug.org.au> (raw)
In-Reply-To: <20210204165831.2703772-1-daniel.vetter@ffwll.ch>


[-- Attachment #1.1: Type: text/plain, Size: 726 bytes --]

Hi Daniel,

On Thu,  4 Feb 2021 17:58:29 +0100 Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>
> Hi all,
> 
> This is a revised version of patch 12 from my series to lock down some
> follow_pfn vs VM_SPECIAL races:
> 
> https://lore.kernel.org/dri-devel/CAKwvOdnSrsnTgPEuQJyaOTSkTP2dR9208Y66HQG_h1e2LKfqtw@mail.gmail.com/
> 
> Stephen reported an issue on HAVE_PCI_LEGACY platforms which this patch
> set tries to address. Previous patches are all still in linux-next.
> 
> Stephen, would be awesome if you can give this a spin.

OK, I applied the 2 patches on top of next-20210205 and it no longer
panics for my simple boot test (PowerPC pseries_le_defconfig under
qemu).

-- 
Cheers,
Stephen Rothwell

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2021-02-07 19:45 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 16:58 [PATCH 0/2] pci sysfs file iomem revoke support Daniel Vetter
2021-02-04 16:58 ` Daniel Vetter
2021-02-04 16:58 ` Daniel Vetter
2021-02-04 16:58 ` [PATCH 1/2] PCI: also set up legacy files only after sysfs init Daniel Vetter
2021-02-04 16:58   ` Daniel Vetter
2021-02-04 16:58   ` Daniel Vetter
2021-02-04 21:50   ` Bjorn Helgaas
2021-02-04 21:50     ` Bjorn Helgaas
2021-02-04 21:50     ` Bjorn Helgaas
2021-02-04 22:24     ` Pali Rohár
2021-02-04 22:24       ` Pali Rohár
2021-02-05  9:59       ` Daniel Vetter
2021-02-05  9:59         ` Daniel Vetter
2021-02-05 10:04         ` Pali Rohár
2021-02-05 10:04           ` Pali Rohár
2021-02-05 10:16           ` Daniel Vetter
2021-02-05 10:16             ` Daniel Vetter
2021-02-05 10:21             ` Pali Rohár
2021-02-05 10:21               ` Pali Rohár
2021-02-05  9:23     ` Daniel Vetter
2021-02-05  9:23       ` Daniel Vetter
2021-02-05  9:23       ` Daniel Vetter
2021-02-04 16:58 ` [PATCH 2/2] PCI: Revoke mappings like devmem Daniel Vetter
2021-02-04 16:58   ` Daniel Vetter
2021-02-04 16:58   ` Daniel Vetter
2021-02-10 22:20   ` Bjorn Helgaas
2021-02-10 22:20     ` Bjorn Helgaas
2021-02-10 22:20     ` Bjorn Helgaas
2021-03-13 21:57   ` Bjorn Helgaas
2021-03-13 21:57     ` Bjorn Helgaas
2021-03-13 21:57     ` Bjorn Helgaas
2021-03-13 22:36     ` Daniel Vetter
2021-03-13 22:36       ` Daniel Vetter
2021-03-13 22:36       ` Daniel Vetter
2021-02-07 19:43 ` Stephen Rothwell [this message]
2021-02-07 19:43   ` [PATCH 0/2] pci sysfs file iomem revoke support Stephen Rothwell
2021-02-07 19:43   ` Stephen Rothwell

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=20210208064357.29b3df55@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=bhelgaas@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=jgg@ziepe.ca \
    --cc=jglisse@redhat.com \
    --cc=jhubbard@nvidia.com \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-samsung-soc@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.