Re: vm_flags, vm_flags_t and __nocast

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 24 Jul 2015, Kirill A. Shutemov wrote:

> sparse complains on each and every vm_flags_t initialization, even with
> proper VM_* constants.
> 
> Do we really want to fix that?
> 
> To me it's too much pain and no gain. __nocast is not beneficial here.
> 
> And I'm not sure that vm_flags_t typedef was a good idea after all.
> Originally, it was intended to become 64-bit one day, but four years later
> it's still unsigned long. Plain unsigned long works fine for other bit
> field.
> 
> What is special about vm_flags?
> 

Maybe remove the __nocast until it's a different type?  Seems like all 
these sites would have to be audited when that happens anyway.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]