linux-kernel - RE: [patch 3/8] x86 PAT: Add follow_pfnmp_pte routine to help tracking pfnmap pages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7E82351C108FA840AB1866AC776AEC46426F307E@orsmsx505.amr.corp.intel.com>
Date:	Wed, 12 Nov 2008 15:54:21 -0800
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	Nick Piggin <npiggin@...e.de>
CC:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	H Peter Anvin <hpa@...or.com>,
	Hugh Dickins <hugh@...itas.com>,
	Roland Dreier <rdreier@...co.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Arjan van de Ven <arjan@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Subject: RE: [patch 3/8] x86 PAT: Add follow_pfnmp_pte routine to help
 tracking pfnmap pages

 

>-----Original Message-----
>From: Nick Piggin [mailto:npiggin@...e.de] 
>Sent: Wednesday, November 12, 2008 3:27 PM
>To: Pallipadi, Venkatesh
>Cc: Ingo Molnar; Thomas Gleixner; H.Peter Anvin; Hugh Dickins; 
>Roland Dreier; Jesse Barnes; Jeremy Fitzhardinge; Arjan van de 
>Ven; linux-kernel@...r.kernel.org; Siddha, Suresh B
>Subject: Re: [patch 3/8] x86 PAT: Add follow_pfnmp_pte routine 
>to help tracking pfnmap pages
>
>On Wed, Nov 12, 2008 at 01:26:50PM -0800, Venkatesh Pallipadi wrote:
>> 
>> Add a generic interface to follow pfn in a pfnmap vma range. 
>This is used by
>> one of the subsequent x86 PAT related patch to keep track of 
>memory types
>> for vma regions across vma copy and free.
>> 
>> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
>> Signed-off-by: Suresh Siddha <suresh.b.siddha@...el.com>
>> 
>> ---
>>  include/linux/mm.h |    3 +++
>>  mm/memory.c        |   43 
>+++++++++++++++++++++++++++++++++++++++++++
>>  2 files changed, 46 insertions(+)
>> 
>> Index: tip/include/linux/mm.h
>> ===================================================================
>> --- tip.orig/include/linux/mm.h	2008-11-06 
>15:41:43.000000000 -0800
>> +++ tip/include/linux/mm.h	2008-11-10 09:44:45.000000000 -0800
>> @@ -1223,6 +1223,9 @@ struct page *follow_page(struct vm_area_
>>  #define FOLL_GET	0x04	/* do get_page on page */
>>  #define FOLL_ANON	0x08	/* give ZERO_PAGE if no pgtable */
>>  
>> +unsigned long follow_pfnmap_pte(struct vm_area_struct *vma,
>> +				unsigned long address, pte_t *ret_ptep);
>> +
>>  typedef int (*pte_fn_t)(pte_t *pte, pgtable_t token, 
>unsigned long addr,
>>  			void *data);
>>  extern int apply_to_page_range(struct mm_struct *mm, 
>unsigned long address,
>> Index: tip/mm/memory.c
>> ===================================================================
>> --- tip.orig/mm/memory.c	2008-11-06 15:41:43.000000000 -0800
>> +++ tip/mm/memory.c	2008-11-10 09:44:45.000000000 -0800
>> @@ -1111,6 +1111,49 @@ no_page_table:
>>  	return page;
>>  }
>>  
>> +unsigned long follow_pfnmap_pte(struct vm_area_struct *vma,
>> +			unsigned long address, pte_t *ret_ptep)
>> +{
>
>I think we'd typically return an int for functions like this. It
>probably wouldn't hurt to return more descriptive errors either.
>-EINVAL, perhaps, seems to fit best with what existing code there
>is doing.
>

Yes. Will change the return type to int with more appropriate
return values and update the patch.

Thanks,
Venki--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/