These are false positives; lockdep is complaining about things that are safe It is just that annotations were missing or incorrect. -----Original Message----- From: David Woodhouse [mailto:dwmw2@xxxxxxxxxxxxx] Sent: Thursday, August 24, 2017 1:37 AM To: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>; KY Srinivasan <kys@xxxxxxxxxxxxx>; Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>; Stephen Hemminger <sthemmin@xxxxxxxxxxxxx> Cc: devel@xxxxxxxxxxxxxxxxxxxxxx; netdev@xxxxxxxxxxxxxxx Subject: Re: [PATCH net-next v3 2/7] netvsc: fix warnings reported by lockdep On Fri, 2017-07-28 at 08:59 -0700, Stephen Hemminger wrote: > This includes a bunch of fixups for issues reported by > lockdep. > * ethtool routines can assume RTNL > * send is done with RCU lock (and BH disable) > * avoid refetching internal device struct (netvsc) > instead pass it as a parameter. > > Signed-off-by: Stephen Hemminger <sthemmin@xxxxxxxxxxxxx> The subject and the commit message are inconsistent — is this fixing *warnings* (i.e. shut up a false positive), or is it fixing *issues*? It looks like it's actually fixing issues, not just warnings? It's really useful to get that right. FWIW the reason I'm looking in my netdev@ folder for lockdep warning fixes is because I was trying to confirm whether the commit message in https://patchwork.kernel.org/patch/4372391/ is actually telling the truth or not — in that case I think it *is* just a false positive being shut up (and thus it's OK to say "fix warning"), not really fixing a true issue. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
