Re: kern/55958: pciback.hide parsing error

[Aleksey Arens <aza.sea.agenda%gmail.com@localhost>]

I wonder if the following solution may be acceptable.  Since the
change implies a difference in ABI, would it be possible to schedule
it for a next major release (for instance, release 10)?  I also
wonder, if the change could go into -current at this point; as I
understand, -current is not expected to maintain strict binary
compatibility.

I suppose that the proper approach to adding this might involve adding
#ifdef-s that checks for COMPAT_XX options.  Though, I think that a
more proper implementation would be to check at runtime for the module
version, and decide upon what buffer length for parameter passing
could be used accordingly.  I could work this code out, in principle;
I would appreciate a suggestion on what would be the best, most
compatible with the tradition, way to handle the hard-coded constant
in the header file.