From: Matthew Wilcox <willy@infradead.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: akpm@linux-foundation.org, mhocko@suse.com,
dan.j.williams@intel.com, kirill.shutemov@linux.intel.com,
pasha.tatashin@oracle.com, vbabka@suse.cz, riel@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Create the new vm_fault_t type
Date: Sat, 3 Nov 2018 05:02:36 -0700 [thread overview]
Message-ID: <20181103120235.GA10491@bombadil.infradead.org> (raw)
In-Reply-To: <20181103050504.GA3049@jordon-HP-15-Notebook-PC>
On Sat, Nov 03, 2018 at 10:35:04AM +0530, Souptick Joarder wrote:
> Page fault handlers are supposed to return VM_FAULT codes,
> but some drivers/file systems mistakenly return error
> numbers. Now that all drivers/file systems have been converted
> to use the vm_fault_t return type, change the type definition
> to no longer be compatible with 'int'. By making it an unsigned
> int, the function prototype becomes incompatible with a function
> which returns int. Sparse will detect any attempts to return a
> value which is not a VM_FAULT code.
> -/* Encode hstate index for a hwpoisoned large page */
> -#define VM_FAULT_SET_HINDEX(x) ((x) << 12)
> -#define VM_FAULT_GET_HINDEX(x) (((x) >> 12) & 0xf)
...
> +/* Encode hstate index for a hwpoisoned large page */
> +#define VM_FAULT_SET_HINDEX(x) ((__force vm_fault_t)((x) << 16))
> +#define VM_FAULT_GET_HINDEX(x) (((x) >> 16) & 0xf)
I think it's important to mention in the changelog that these values
have been changed to avoid conflicts with other VM_FAULT codes.
> +/**
> + * typedef vm_fault_t - __bitwise unsigned int
> + *
> + * vm_fault_t is the new unsigned int type to return VM_FAULT
> + * code by page fault handlers of drivers/file systems. Now if
> + * any page fault handlers returns non VM_FAULT code instead
> + * of VM_FAULT code, it will be a mismatch with function
> + * prototype and sparse will detect it.
> + */
The first line should be what the typedef *means*, not repeat the
compiler's definition. The rest of the description should be information
for someone coming to the type for the first time; what you've written
here is changelog material.
/**
* typedef vm_fault_t - Return type for page fault handlers.
*
* Page fault handlers return a bitmask of %VM_FAULT values.
*/
> +typedef __bitwise unsigned int vm_fault_t;
> +
> +/**
> + * enum - VM_FAULT code
Can you document an anonymous enum? I've never tried. Did you run this
through 'make htmldocs'?
> + * This enum is used to track the VM_FAULT code return by page
> + * fault handlers.
* Page fault handlers return a bitmask of these values to tell the
* core VM what happened when handling the fault.
next prev parent reply other threads:[~2018-11-03 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 5:05 Souptick Joarder
2018-11-03 5:11 ` Souptick Joarder
2018-11-03 12:02 ` Matthew Wilcox [this message]
2018-11-04 8:36 ` Mike Rapoport
2018-11-05 5:44 ` Souptick Joarder
2018-11-05 9:13 ` Mike Rapoport
2018-11-05 13:53 ` Souptick Joarder
2018-11-06 6:21 ` Mike Rapoport
2018-11-06 6:29 ` 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=20181103120235.GA10491@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jrdr.linux@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pasha.tatashin@oracle.com \
--cc=riel@redhat.com \
--cc=vbabka@suse.cz \
/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