On Thu, Aug 22, 2024 at 07:35:20AM +0800, Greg Kroah-Hartman wrote: > On Wed, Aug 21, 2024 at 03:10:56PM -0300, Jason Gunthorpe wrote: > > Requesting a fwctl scope of access that includes mutating device debug > > data will cause the kernel to be tainted. Changing the device operation > > through things in the debug scope may cause the device to malfunction in > > undefined ways. This should be reflected in the TAINT flags to help any > > debuggers understand that something has been done. > > I know naming is hard, but the word "fwctl" is rough, don't you think? > It's become much more than just a random driver in the kernel tree, it's > now a taint flag and is exposed to userspace. So I think you need to > rename it to something that is at least pronouncable when talking about > it (i.e. something with vowels...) Okay, that makes sense to me. We could also choose a different name for the taint flag. Let's see if some people have some ideas, I don't have a ready alternative.. We've just been calling it "firwmare control" in conversation Thanks, Jason
