On Monday 2017-01-23 18:26, Borislav Petkov wrote: >On Mon, Jan 23, 2017 at 09:21:03AM -0800, Christoph Hellwig wrote: >> Or keep the exported version as-is and never changed it, and use >> a different copy for the kernel itself. > >I guess we'll have to do that if something in userspace has put its >sticky fingers on that file and cannot be fixed. Which I hardly doubt >but we can't break that damn userspace. The importance of uapi headers presence is a bit overrated. If you look at, for example, iptables (and further projects in that area), copies of uapi headers have been made (and this process is likely to continue) because it could be compiled on a variety of vintage systems that do not have all required #defines yet. Similarly, it may be built on a variety of _modern_ systems whose kernels no longer have a particular thing (e.g. ipt_SAME), so it also ships copies of those headers. So if some userspace component depends on that particular msr header (which, unlike ipt_SAME, was not intended for export), is it not reasonable to expect them to make a copy if and when they need it? -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
