From: Christoph Hellwig <hch@infradead.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: vm_area at addr ffffffffc0800000 is not marked as VM_IOREMAP
Date: Fri, 8 Mar 2024 09:24:51 -0800 [thread overview]
Message-ID: <ZetJ4xfopatYstPs@infradead.org> (raw)
In-Reply-To: <CAADnVQL4JAUz-p-X9aEggeKNpYUqJZrzQKO7N0dnohE0r7mdpg@mail.gmail.com>
On Fri, Mar 08, 2024 at 09:20:24AM -0800, Alexei Starovoitov wrote:
> ok. Like the attached patch?
Looks sensibe, but I think the powerpc callers of ioremap_page_range
will need the same treatment.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Daniel Borkmann <daniel@iogearbox.net>, bpf <bpf@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: vm_area at addr ffffffffc0800000 is not marked as VM_IOREMAP
Date: Fri, 8 Mar 2024 09:24:51 -0800 [thread overview]
Message-ID: <ZetJ4xfopatYstPs@infradead.org> (raw)
In-Reply-To: <CAADnVQL4JAUz-p-X9aEggeKNpYUqJZrzQKO7N0dnohE0r7mdpg@mail.gmail.com>
On Fri, Mar 08, 2024 at 09:20:24AM -0800, Alexei Starovoitov wrote:
> ok. Like the attached patch?
Looks sensibe, but I think the powerpc callers of ioremap_page_range
will need the same treatment.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-08 17:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 17:42 vm_area at addr ffffffffc0800000 is not marked as VM_IOREMAP Miguel Ojeda
2024-03-07 17:42 ` Miguel Ojeda
2024-03-07 17:54 ` Alexei Starovoitov
2024-03-07 17:54 ` Alexei Starovoitov
2024-03-08 3:49 ` Alexei Starovoitov
2024-03-08 3:49 ` Alexei Starovoitov
2024-03-08 10:48 ` Manivannan Sadhasivam
2024-03-08 10:48 ` Manivannan Sadhasivam
2024-03-08 11:23 ` Miguel Ojeda
2024-03-08 11:23 ` Miguel Ojeda
2024-03-08 15:04 ` Christoph Hellwig
2024-03-08 15:04 ` Christoph Hellwig
2024-03-08 16:33 ` Alexei Starovoitov
2024-03-08 16:33 ` Alexei Starovoitov
2024-03-08 17:02 ` Christoph Hellwig
2024-03-08 17:02 ` Christoph Hellwig
2024-03-08 17:20 ` Alexei Starovoitov
2024-03-08 17:20 ` Alexei Starovoitov
2024-03-08 17:24 ` Christoph Hellwig [this message]
2024-03-08 17:24 ` Christoph Hellwig
2024-03-08 17:53 ` Alexei Starovoitov
2024-03-08 17:53 ` Alexei Starovoitov
2024-03-08 22:44 ` Alexei Starovoitov
2024-03-08 22:44 ` Alexei Starovoitov
2024-03-09 1:37 ` Alexei Starovoitov
2024-03-09 1:37 ` Alexei Starovoitov
2024-03-09 15:29 ` Christoph Hellwig
2024-03-09 15:29 ` Christoph Hellwig
2024-03-09 16:33 ` Alexei Starovoitov
2024-03-09 16:33 ` Alexei Starovoitov
2024-03-09 16:36 ` Christoph Hellwig
2024-03-09 16:36 ` Christoph Hellwig
2024-03-09 16:38 ` Alexei Starovoitov
2024-03-09 16:38 ` Alexei Starovoitov
2024-03-11 11:46 ` Miguel Ojeda
2024-03-11 11:46 ` Miguel Ojeda
2024-03-08 16:13 ` Bjorn Helgaas
2024-03-08 16:13 ` Bjorn Helgaas
2024-03-08 16:37 ` Alexei Starovoitov
2024-03-08 16:37 ` Alexei Starovoitov
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=ZetJ4xfopatYstPs@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bhelgaas@google.com \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=will@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.