On Wed, Dec 20, 2017 at 05:04:52PM -0800, Bjorn Helgaas wrote: > On Tue, Dec 19, 2017 at 02:06:40PM -0700, Keith Busch wrote: > > Getting the AER information is documented to return 0 when it failed to > > get the information. > > I think this case is either impossible (if we only call this function > for devices known to support AER), or it fixes an actual bug (the > caller would call aer_print_error() when it shouldn't, and potentially > print garbage). Right? > > If the former, I vote for removing the test. If the latter, the > changelog should mention that it fixes a bug. I just spotted this mistake when I was changing the function to non-static. I've never observed bogus data printed in real life. In the current AER handling, the only way we could incorrectly get there is if the root port's Error Source ID Register somehow contains the ID of a device that doesn't have AER capabilities, which would of course be broken. So if we trust hardware, we should are safe to remove the check.
