On Tue, Jun 03, 2014 at 09:06:54AM -0400, Vivek Goyal wrote: > So far kexec_segment->buf was always a user space pointer as user space > passed the array of kexec_segment structures and kernel copied it. > > But with new system call, list of kexec segments will be prepared by > kernel and kexec_segment->buf will point to a kernel memory. > > So while I was adding code where I made assumption that ->buf is pointing > to kernel memory, sparse started giving warning. > > Make ->buf a union. And where a user space pointer is expected, access > it using ->buf and where a kernel space pointer is expected, access it > using ->kbuf. That takes care of sparse warnings. > > Signed-off-by: Vivek Goyal <[email protected]>
Acked-by: Borislav Petkov <[email protected]> -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
