From: Baoquan He <bhe@redhat.com>
To: Stephen Brennan <stephen.s.brennan@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, urezki@gmail.com, hch@infradead.org
Subject: Re: [PATCH RFC 3/3] mm/vmalloc.c: allow vread() to read out vm_map_ram areas
Date: Thu, 10 Nov 2022 18:23:55 +0800 [thread overview]
Message-ID: <Y2zROzfhdR5UU+lv@MiWiFi-R3L-srv> (raw)
In-Reply-To: <87v8nnfwud.fsf@oracle.com>
On 11/09/22 at 04:59pm, Stephen Brennan wrote:
......
> > @@ -3569,12 +3609,14 @@ long vread(char *buf, char *addr, unsigned long count)
> > if (!count)
> > break;
> >
> > - if (!va->vm)
> > + if (!(va->flags & VMAP_RAM) && !va->vm)
> > continue;
> >
> > vm = va->vm;
> > - vaddr = (char *) vm->addr;
> > - if (addr >= vaddr + get_vm_area_size(vm))
> > + vaddr = (char *) va->va_start;
> > + size = vm ? get_vm_area_size(vm) : va_size(va);
>
> Hi Baoquan,
>
> Thanks for working on this. I tested your patches out by using drgn to
> debug /proc/kcore. I have a kernel module[1] to do a vm_map_ram() call
> and print the virtual address to the kernel log so I can try to read
> that memory address in drgn. When I did this test, I got a panic on the
> above line of code.
......
> Since flags is in a union, it shadows "vm" and causes the condition to
> be true, and then get_vm_area_size() tries to follow the pointer defined
> by flags. I'm not sure if the fix is to have flags be a separate field
> inside vmap_area, or to have more careful handling in the vread path.
Sorry, my bad. Thanks for testing this and catching the error, Stephen.
About the fix, both way are fine to me. I made a draft fix based on the
current patchset. To me, adding flags in a separate field makes code
easier, but cost extra memory. I will see what other people say about
this, firstly if the solution is acceptable, then reusing the union
field or adding anohter flags.
Could you try below code to see if it works?
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 5a8d5659bfb0..78cae59170d8 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -1890,6 +1890,7 @@ struct vmap_area *find_vmap_area(unsigned long addr)
#define VMAP_RAM 0x1
#define VMAP_BLOCK 0x2
+#define VMAP_FLAGS_MASK 0x3
struct vmap_block_queue {
spinlock_t lock;
@@ -3588,7 +3589,7 @@ long vread(char *buf, char *addr, unsigned long count)
struct vm_struct *vm;
char *vaddr, *buf_start = buf;
unsigned long buflen = count;
- unsigned long n, size;
+ unsigned long n, size, flags;
addr = kasan_reset_tag(addr);
@@ -3609,12 +3610,14 @@ long vread(char *buf, char *addr, unsigned long count)
if (!count)
break;
- if (!(va->flags & VMAP_RAM) && !va->vm)
+ if (!va->vm)
continue;
+ flags = va->flags & VMAP_FLAGS_MASK;
vm = va->vm;
+
vaddr = (char *) va->va_start;
- size = vm ? get_vm_area_size(vm) : va_size(va);
+ size = flags ? va_size(va) : get_vm_area_size(vm);
if (addr >= vaddr + size)
continue;
@@ -3630,9 +3633,9 @@ long vread(char *buf, char *addr, unsigned long count)
if (n > count)
n = count;
- if ((va->flags & (VMAP_RAM|VMAP_BLOCK)) == (VMAP_RAM|VMAP_BLOCK))
+ if ((flags & (VMAP_RAM|VMAP_BLOCK)) == (VMAP_RAM|VMAP_BLOCK))
vb_vread(buf, addr, n);
- else if ((va->flags & VMAP_RAM) || !(vm->flags & VM_IOREMAP))
+ else if ((flags & VMAP_RAM) || !(vm->flags & VM_IOREMAP))
aligned_vread(buf, addr, n);
else /* IOREMAP area is treated as memory hole */
memset(buf, 0, n);
next prev parent reply other threads:[~2022-11-10 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 3:35 [PATCH RFC 0/3] " Baoquan He
2022-11-09 3:35 ` [PATCH RFC 1/3] mm/vmalloc.c: add used_map into vmap_block to track space of vmap_block Baoquan He
2022-11-09 3:35 ` [PATCH RFC 2/3] mm/vmalloc.c: add flags to mark vm_map_ram area Baoquan He
2022-11-09 3:35 ` [PATCH RFC 3/3] mm/vmalloc.c: allow vread() to read out vm_map_ram areas Baoquan He
2022-11-10 0:59 ` Stephen Brennan
2022-11-10 10:23 ` Baoquan He [this message]
2022-11-10 18:48 ` Stephen Brennan
2022-11-14 10:06 ` Baoquan He
2022-11-18 8:01 ` Matthew Wilcox
2022-11-23 3:38 ` Baoquan He
2022-11-23 13:24 ` Matthew Wilcox
2022-11-24 9:52 ` Baoquan He
2022-11-30 13:06 ` Uladzislau Rezki
2022-12-01 4:46 ` Baoquan He
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=Y2zROzfhdR5UU+lv@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stephen.s.brennan@oracle.com \
--cc=urezki@gmail.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