Linux中进程的行走页表

Mir*_*chi 21 linux kernel linux-kernel

我正在尝试浏览页面表以获取linux中的进程.在内核模块中,我实现了以下功能:

static struct page *walk_page_table(unsigned long addr)
{
    pgd_t *pgd;
    pte_t *ptep, pte;
    pud_t *pud;
    pmd_t *pmd;

    struct page *page = NULL;
    struct mm_struct *mm = current->mm;

    pgd = pgd_offset(mm, addr);
    if (pgd_none(*pgd) || pgd_bad(*pgd))
        goto out;
    printk(KERN_NOTICE "Valid pgd");

    pud = pud_offset(pgd, addr);
    if (pud_none(*pud) || pud_bad(*pud))
        goto out;
    printk(KERN_NOTICE "Valid pud");

    pmd = pmd_offset(pud, addr);
    if (pmd_none(*pmd) || pmd_bad(*pmd))
        goto out;
    printk(KERN_NOTICE "Valid pmd");

    ptep = pte_offset_map(pmd, addr);
    if (!ptep)
        goto out;
    pte = *ptep;

    page = pte_page(pte);
    if (page)
        printk(KERN_INFO "page frame struct is @ %p", page);

 out:
    return page;
}
Run Code Online (Sandbox Code Playgroud)

ioctl和调用此函数是addr进程地址空间中的虚拟地址:

static int my_ioctl(struct inode *inode, struct file *filp, unsigned int cmd, unsigned long addr)
{
   struct page *page = walk_page_table(addr);
   ...
   return 0;
}
Run Code Online (Sandbox Code Playgroud)

奇怪的是,调用ioctl用户空间进程,这段错误...但似乎我正在寻找页表条目的方式是正确的,因为dmesg我获得了例如每个ioctl调用:

[ 1721.437104] Valid pgd
[ 1721.437108] Valid pud
[ 1721.437108] Valid pmd
[ 1721.437110] page frame struct is @ c17d9b80
Run Code Online (Sandbox Code Playgroud)

那么为什么这个过程不能正确地完成'ioctl'调用呢?也许我必须在导航页面表之前锁定一些东西?

我正在使用内核2.6.35-22和三个级别的页表.

谢谢你们!

小智 11

pte_unmap(ptep); 
Run Code Online (Sandbox Code Playgroud)

在标签出来之前就丢失了.尝试以这种方式更改代码:

    ...
    page = pte_page(pte);
    if (page)
        printk(KERN_INFO "page frame struct is @ %p", page);

    pte_unmap(ptep); 

out:
Run Code Online (Sandbox Code Playgroud)


Pet*_*eoh 6

查看/proc/<pid>/smaps文件系统,可以看到用户空间内存:

cat smaps 
bfa60000-bfa81000 rw-p 00000000 00:00 0          [stack]
Size:                136 kB
Rss:                  44 kB
Run Code Online (Sandbox Code Playgroud)

以及它是如何打印的fs/proc/task_mmu.c(来自内核源代码):

http://lxr.linux.no/linux+v3.0.4/fs/proc/task_mmu.c

   if (vma->vm_mm && !is_vm_hugetlb_page(vma))
               walk_page_range(vma->vm_start, vma->vm_end, &smaps_walk);
               show_map_vma(m, vma.....);
        seq_printf(m,
                   "Size:           %8lu kB\n"
                   "Rss:            %8lu kB\n"
                   "Pss:            %8lu kB\n"
Run Code Online (Sandbox Code Playgroud)

而且你的函数有点像walk_page_range().查看walk_page_range(),您可以看到smaps_walk结构在行走时不应该改变:

http://lxr.linux.no/linux+v3.0.4/mm/pagewalk.c#L153

For eg:

                }
 201                if (walk->pgd_entry)
 202                        err = walk->pgd_entry(pgd, addr, next, walk);
 203                if (!err &&
 204                    (walk->pud_entry || walk->pmd_entry || walk->pte_entry
Run Code Online (Sandbox Code Playgroud)

如果要改变步行,那么上述所有检查可能会不一致.

所有这些只是意味着你必须在遍历页面表时锁定mmap_sem:

   if (!down_read_trylock(&mm->mmap_sem)) {
            /*
             * Activate page so shrink_inactive_list is unlikely to unmap
             * its ptes while lock is dropped, so swapoff can make progress.
             */
            activate_page(page);
            unlock_page(page);
            down_read(&mm->mmap_sem);
            lock_page(page);
    }
Run Code Online (Sandbox Code Playgroud)

然后解锁:

up_read(&mm->mmap_sem);
Run Code Online (Sandbox Code Playgroud)

当然,当您在内核模块中发出pagetable的printk()时,内核模块正在insmod进程的进程上下文中运行(只需printk"comm",你可以看到"insmod")意味着mmap_sem是锁定,这也意味着进程没有运行,因此在进程完成之前没有控制台输出(所有printk()输出仅进入内存).

听起来合乎逻辑?