On Thu, Aug 07, 2025 at 05:17:05PM +0200, Stefan Metzmacher wrote: > > > I'm typically doing a full kernel build a week after each rc. > > > My idea was to rebuild the whole db after doing that. > > > > Yeah. That's a good strategy. The data from the existing DB feeds > > into the new one when you rebuild the DB so don't delete the old > > DB at the start or anything. > > I mean I'm typically do a git clean -xdf . in order > to wipe everything in order to do a clean: > make -j33 bindeb-pkg > > So it would build a new DB, as I'm working based on > the new kernel I guess that's all I need or > are there other reasons to update the existing DB? You really want to keep the old smatch_db.sqlite DB file between rebuilds. Every time you rebuild the DB it adds more information to the call tree. Imagine a() passes a number to b() which passes it to c(). It takes two rebuilds for that information to be built out. regards, dan carpenter
