From: Lorenzo Stoakes <lstoakes@gmail.com>
To: Baoquan He <bhe@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Uladzislau Rezki <urezki@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
Liu Shixin <liushixin2@huawei.com>, Jiri Olsa <jolsa@kernel.org>,
Jens Axboe <axboe@kernel.dk>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v4 3/4] iov_iter: add copy_page_to_iter_atomic()
Date: Wed, 22 Mar 2023 11:06:14 +0000 [thread overview]
Message-ID: <a9e62a20-13eb-464b-9452-9d7bb2566e85@lucifer.local> (raw)
In-Reply-To: <a961ab9c-1ced-4db4-a76f-d886bd01c715@lucifer.local>
On Wed, Mar 22, 2023 at 10:32:47AM +0000, Lorenzo Stoakes wrote:
> > I am a little confused about the name of this new function. In its
> > conterpart, copy_page_from_iter_atomic(), kmap_atomic()/kunmpa_atomic()
> > are used. With them, if CONFIG_HIGHMEM=n, it's like below:
>
> The reason for this is that:-
>
> 1. kmap_atomic() explicitly states that it is now deprecated and must no longer
> be used, and kmap_local_page() should be used instead:-
>
> * kmap_atomic - Atomically map a page for temporary usage - Deprecated!
>
> * Do not use in new code. Use kmap_local_page() instead.
>
> 2. kmap_local_page() explicitly states that it can be used in any context:-
>
> * Can be invoked from any context, including interrupts.
>
> I wanted follow this advice as strictly as I could, hence the change. However,
> we do need preemption/pagefaults explicitly disabled in this context (we are
> happy to fail if the faulted in pages are unmapped in meantime), and I didn't
> check the internals to make sure.
>
> So I think for safety it is better to use k[un]map_atomic() here, I'll respin
> and put that back in, good catch!
>
Actually, given we have preemption disabled due to the held spinlock, I think
it'd be better to add a copy_page_to_iter_nofault() that uses
copy_to_user_nofault() which will disable pagefaults thus have exactly the
equivalent behaviour, more explicitly and without the use of a deprecated
function.
Thanks for raising this!!
> >
> > static inline void *kmap_atomic(struct page *page)
> > {
> > if (IS_ENABLED(CONFIG_PREEMPT_RT))
> > migrate_disable();
> > else
> > preempt_disable();
> > pagefault_disable();
> > return page_address(page);
> > }
> >
> > But kmap_local_page() is only having page_address(), the code block
> > between kmap_local_page() and kunmap_local() is also atomic, it's a
> > little messy in my mind.
> >
> > static inline void *kmap_local_page(struct page *page)
> > {
> > return page_address(page);
> > }
> >
> > > + char *p = kaddr + offset;
> > > + size_t copied = 0;
> > > +
> > > + if (!page_copy_sane(page, offset, bytes) ||
> > > + WARN_ON_ONCE(i->data_source))
> > > + goto out;
> > > +
> > > + if (unlikely(iov_iter_is_pipe(i))) {
> > > + copied = copy_page_to_iter_pipe(page, offset, bytes, i);
> > > + goto out;
> > > + }
> > > +
> > > + iterate_and_advance(i, bytes, base, len, off,
> > > + copyout(base, p + off, len),
> > > + memcpy(base, p + off, len)
> > > + )
> > > + copied = bytes;
> > > +
> > > +out:
> > > + kunmap_local(kaddr);
> > > + return copied;
> > > +}
> > > +EXPORT_SYMBOL(copy_page_to_iter_atomic);
> > > +
> > > static void pipe_advance(struct iov_iter *i, size_t size)
> > > {
> > > struct pipe_inode_info *pipe = i->pipe;
> > > --
> > > 2.39.2
> > >
> >
next prev parent reply other threads:[~2023-03-22 11:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 20:54 [PATCH v4 0/4] convert read_kcore(), vread() to use iterators Lorenzo Stoakes
2023-03-21 20:54 ` [PATCH v4 1/4] fs/proc/kcore: avoid bounce buffer for ktext data Lorenzo Stoakes
2023-03-21 20:54 ` [PATCH v4 2/4] fs/proc/kcore: convert read_kcore() to read_kcore_iter() Lorenzo Stoakes
2023-03-22 1:15 ` Baoquan He
2023-03-22 6:17 ` Lorenzo Stoakes
2023-03-22 11:12 ` David Hildenbrand
2023-03-21 20:54 ` [PATCH v4 3/4] iov_iter: add copy_page_to_iter_atomic() Lorenzo Stoakes
2023-03-22 10:17 ` Baoquan He
2023-03-22 10:32 ` Lorenzo Stoakes
2023-03-22 11:06 ` Lorenzo Stoakes [this message]
2023-03-22 13:21 ` Baoquan He
2023-03-22 13:08 ` Baoquan He
2023-03-21 20:54 ` [PATCH v4 4/4] mm: vmalloc: convert vread() to vread_iter() Lorenzo Stoakes
2023-03-22 11:18 ` David Hildenbrand
2023-03-22 11:31 ` Lorenzo Stoakes
2023-03-22 12:55 ` Baoquan He
2023-03-22 13:43 ` Lorenzo Stoakes
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=a9e62a20-13eb-464b-9452-9d7bb2566e85@lucifer.local \
--to=lstoakes@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bhe@redhat.com \
--cc=david@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=urezki@gmail.com \
--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