From: ebiederm@xmission.com (Eric W. Biederman)
To: Miles Chen <miles.chen@mediatek.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <wsd_upstream@mediatek.com>
Subject: Re: [RESEND PATCH v1] proc: use untagged_addr() for pagemap_read addresses
Date: Tue, 24 Nov 2020 12:32:56 -0600 [thread overview]
Message-ID: <87lfeqsizr.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20201123063835.18981-1-miles.chen@mediatek.com> (Miles Chen's message of "Mon, 23 Nov 2020 14:38:35 +0800")
Miles Chen <miles.chen@mediatek.com> writes:
> When we try to visit the pagemap of a tagged userspace pointer, we find
> that the start_vaddr is not correct because of the tag.
> To fix it, we should untag the usespace pointers in pagemap_read().
>
> I tested with 5.10-rc4 and the issue remains.
>
> My test code is baed on [1]:
>
> A userspace pointer which has been tagged by 0xb4: 0xb400007662f541c8
Sigh this patch is buggy.
> === userspace program ===
>
> uint64 OsLayer::VirtualToPhysical(void *vaddr) {
> uint64 frame, paddr, pfnmask, pagemask;
> int pagesize = sysconf(_SC_PAGESIZE);
> off64_t off = ((uintptr_t)vaddr) / pagesize * 8; // off = 0xb400007662f541c8 / pagesize * 8 = 0x5a00003b317aa0
> int fd = open(kPagemapPath, O_RDONLY);
> ...
>
> if (lseek64(fd, off, SEEK_SET) != off || read(fd, &frame, 8) != 8) {
> int err = errno;
> string errtxt = ErrorString(err);
> if (fd >= 0)
> close(fd);
> return 0;
> }
> ...
> }
>
> === kernel fs/proc/task_mmu.c ===
>
> static ssize_t pagemap_read(struct file *file, char __user *buf,
> size_t count, loff_t *ppos)
> {
> ...
> src = *ppos;
> svpfn = src / PM_ENTRY_BYTES; // svpfn == 0xb400007662f54
> start_vaddr = svpfn << PAGE_SHIFT; // start_vaddr == 0xb400007662f54000
> end_vaddr = mm->task_size;
>
> /* watch out for wraparound */
> // svpfn == 0xb400007662f54
> // (mm->task_size >> PAGE) == 0x8000000
> if (svpfn > mm->task_size >> PAGE_SHIFT) // the condition is true because of the tag 0xb4
> start_vaddr = end_vaddr;
>
> ret = 0;
> while (count && (start_vaddr < end_vaddr)) { // we cannot visit correct entry because start_vaddr is set to end_vaddr
> int len;
> unsigned long end;
> ...
> }
> ...
> }
>
> [1] https://github.com/stressapptest/stressapptest/blob/master/src/os.cc#L158
>
> Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> ---
> fs/proc/task_mmu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
> index 217aa2705d5d..e9a70f7ee515 100644
> --- a/fs/proc/task_mmu.c
> +++ b/fs/proc/task_mmu.c
> @@ -1599,11 +1599,11 @@ static ssize_t pagemap_read(struct file *file, char __user *buf,
>
> src = *ppos;
> svpfn = src / PM_ENTRY_BYTES;
> - start_vaddr = svpfn << PAGE_SHIFT;
> + start_vaddr = untagged_addr(svpfn << PAGE_SHIFT);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Arguably the line above is safe, but unfortunately it has the
possibility of suffering from overflow.
> end_vaddr = mm->task_size;
>
> /* watch out for wraparound */
> - if (svpfn > mm->task_size >> PAGE_SHIFT)
> + if (start_vaddr > mm->task_size)
> start_vaddr = end_vaddr;
Overflow handling you are removing here.
>
> /*
I suspect the proper way to handle this is to move the test for
overflow earlier so the code looks something like:
end_vaddr = mm->task_size;
src = *ppos;
svpfn = src / PM_ENTRY_BYTES;
/* watch out for wraparound */
start_vaddr = end_vaddr;
if (svpfn < (ULONG_MAX >> PAGE_SHIFT))
start_vaddr = untagged_addr(svpfn << PAGE_SHIFT);
/* Ensure the address is inside the task */
if (start_vaddr > mm->task_size)
start_vaddr = end_vaddr;
Eric
next prev parent reply other threads:[~2020-11-24 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 6:38 [RESEND PATCH v1] proc: use untagged_addr() for pagemap_read addresses Miles Chen
2020-11-24 18:32 ` Eric W. Biederman [this message]
2020-11-27 1:55 ` Miles Chen
2020-11-26 7:16 ` Song Bao Hua (Barry Song)
2020-11-26 7:49 ` Miles Chen
2020-11-26 7:57 ` Song Bao Hua (Barry Song)
2020-11-26 9:29 ` Song Bao Hua (Barry Song)
2020-11-26 11:10 ` Catalin Marinas
2020-11-27 3:16 ` Miles Chen
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=87lfeqsizr.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=miles.chen@mediatek.com \
--cc=wsd_upstream@mediatek.com \
/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