From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Matthew Wilcox <willy@infradead.org>, Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Ira Weiny <ira.weiny@intel.com>,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH v3 4/4] fs/sysv: Replace kmap() with kmap_local_page()
Date: Mon, 23 Jan 2023 18:14:15 +0100 [thread overview]
Message-ID: <3146373.5fSG56mABF@suse> (raw)
In-Reply-To: <Y8os8QR1pRXyu4N8@ZenIV>
On venerdì 20 gennaio 2023 06:56:01 CET Al Viro wrote:
> On Fri, Jan 20, 2023 at 05:07:48AM +0000, Al Viro wrote:
> > On Fri, Jan 20, 2023 at 04:54:51AM +0000, Matthew Wilcox wrote:
> > > > Sure, but... there's also this:
> > > >
> > > > static inline void __kunmap_local(const void *addr)
> > > > {
> > > > #ifdef ARCH_HAS_FLUSH_ON_KUNMAP
> > > >
> > > > kunmap_flush_on_unmap(addr);
> > > >
> > > > #endif
> > > > }
> > > >
> > > > Are you sure that the guts of that thing will be happy with address
that
> > > > is not page-aligned? I've looked there at some point, got scared of
> > > > parisc (IIRC) MMU details and decided not to rely upon that...
> > >
> > > Ugh, PA-RISC (the only implementer) definitely will flush the wrong
> > > addresses. I think we should do this, as having bugs that only manifest
> > > on one not-well-tested architecture seems Bad.
> > >
> > > static inline void __kunmap_local(const void *addr)
> > > {
> > > #ifdef ARCH_HAS_FLUSH_ON_KUNMAP
> > >
> > > - kunmap_flush_on_unmap(addr);
> > > + kunmap_flush_on_unmap(PAGE_ALIGN_DOWN(addr));
> > >
> > > #endif
> > > }
> >
> > PTR_ALIGN_DOWN(addr, PAGE_SIZE), perhaps?
>
> Anyway, that's a question to parisc folks; I _think_ pdtlb
> quietly ignores the lower bits of address, so that part seems
> to be safe, but I wouldn't bet upon that. And when I got to
> flush_kernel_dcache_page_asm I gave up - it's been a long time
> since I've dealt with parisc assembler.
There seems to be consensus that __kunmap_local() needs to be fixed for the
parisc case (ARCH_HAS_FLUSH_ON_KUNMAP).
Is anyone doing this task?
If you agree, I could make this change and give proper credits for the tip.
Thank you,
Fabio
next prev parent reply other threads:[~2023-01-23 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 15:32 [PATCH v3 0/4] fs/sysv: Replace kmap() with kmap_local_page() Fabio M. De Francesco
2023-01-19 15:32 ` [PATCH v3 1/4] fs/sysv: Use the offset_in_page() helper Fabio M. De Francesco
2023-01-19 15:32 ` [PATCH v3 2/4] fs/sysv: Change the signature of dir_get_page() Fabio M. De Francesco
2023-01-19 15:32 ` [PATCH v3 3/4] fs/sysv: Use dir_put_page() in sysv_rename() Fabio M. De Francesco
2023-01-19 15:32 ` [PATCH v3 4/4] fs/sysv: Replace kmap() with kmap_local_page() Fabio M. De Francesco
2023-01-20 0:54 ` Al Viro
2023-01-20 4:21 ` Al Viro
2023-01-20 4:28 ` Matthew Wilcox
2023-01-20 4:45 ` Al Viro
2023-01-20 4:54 ` Matthew Wilcox
2023-01-20 5:07 ` Al Viro
2023-01-20 5:56 ` Al Viro
2023-01-20 7:17 ` Helge Deller
2023-01-21 8:05 ` Ira Weiny
2023-01-21 10:57 ` Helge Deller
2023-01-21 19:26 ` Al Viro
2023-01-23 17:14 ` Fabio M. De Francesco [this message]
2023-01-24 20:16 ` Ira Weiny
2023-01-23 17:03 ` Fabio M. De Francesco
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=3146373.5fSG56mABF@suse \
--to=fmdefrancesco@gmail.com \
--cc=hch@infradead.org \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).