On Fri, Jun 29, 2018 at 06:36:10PM +0200, Andrey Konovalov wrote: > On Fri, Jun 29, 2018 at 1:07 PM, Will Deacon <will.deacon@xxxxxxx> wrote: > > It might not seen sensible, but we could still be relying on this in the > > kernel and so this change would introduce a regression. I think we need > > a way to identify such pointer usage before these patches can seriously be > > considered for mainline inclusion. > > Another point that I have here is that KHWASAN is a debugging tool not > meant to be used in production. We're not trying to change the ABI or > something like that (referring to the other HWASAN patchset). We can > fix up the non obvious places where untagging is needed in a case by > case basis with additional patches when testing reveals it. Hmm, but elsewhere in this thread, Evgenii is motivating the need for this patch set precisely because the lower overhead means it's suitable for "near-production" use. So I don't think writing this off as a debugging feature is the right approach, and we instead need to put effort into analysing the impact of address tags on the kernel as a whole. Playing whack-a-mole with subtle tag issues sounds like the worst possible outcome for the long-term. Will -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
