From: Matthew Wilcox <willy@infradead.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: luto@amacapital.net, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
brajeswar.linux@gmail.com, sabyasachi.linux@gmail.com
Subject: Re: [PATCH v2] x86/vdso: Change return type to vm_fault_t for fault handlers
Date: Tue, 3 Jul 2018 04:17:35 -0700 [thread overview]
Message-ID: <20180703111735.GA3544@bombadil.infradead.org> (raw)
In-Reply-To: <20180625175737.GA20042@jordon-HP-15-Notebook-PC>
On Mon, Jun 25, 2018 at 11:27:37PM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for both fault handler
> vdso_fault() and vvar_fault(). Previously vm_insert_pfn()
> returns err which has to mapped into VM_FAULT_* type.
> The new function vmf_insert_pfn() will replace this
> inefficiency by returning correct VM_FAULT_* type.
> @@ -105,10 +105,10 @@ static int vvar_fault(const struct vm_special_mapping *sm,
> * the page past the end of the vvar mapping.
> */
> if (sym_offset == 0)
> - return VM_FAULT_SIGBUS;
> + return ret;
>
> if (sym_offset == image->sym_vvar_page) {
> - ret = vm_insert_pfn(vma, vmf->address,
> + ret = vmf_insert_pfn(vma, vmf->address,
> __pa_symbol(&__vvar_page) >> PAGE_SHIFT);
> } else if (sym_offset == image->sym_pvclock_page) {
> struct pvclock_vsyscall_time_info *pvti =
> @@ -124,14 +124,11 @@ static int vvar_fault(const struct vm_special_mapping *sm,
Haven't you missed converting vm_insert_pfn_prot() at line 117?
Did you test-compile this?
next prev parent reply other threads:[~2018-07-03 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 17:57 Souptick Joarder
2018-07-03 11:17 ` Matthew Wilcox [this message]
2018-07-03 11:48 ` Souptick Joarder
2018-07-03 12:11 ` Matthew Wilcox
2018-07-03 15:16 ` Souptick Joarder
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=20180703111735.GA3544@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=brajeswar.linux@gmail.com \
--cc=hpa@zytor.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=sabyasachi.linux@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®