On Mon, Nov 10, 2025 at 3:16 PM Richard Purdie <
[email protected]> wrote:

> On Mon, 2025-11-03 at 14:31 +0000, Niko Mauno via lists.openembedded.org
> wrote:
> > This should help to avoid problems that will occur if the modification
> > time of database file itself is altered e.g. by unassociated
> > process(es) on the file system which hosts the database file.
> >
> > Since this change updates the database structure by adding a new table,
> > bump the 'minor' version number in database file names to enforce full
> > database fetch. This should also iron out e.g. situation where the
> > database might have inconspicuously omitted entries due to way in which
> > the mtime of database file itself was relied upon.
> >
> > Signed-off-by: Niko Mauno <[email protected]>
> > ---
> >  meta/classes/cve-check.bbclass                |  2 +-
> >  .../recipes-core/meta/cve-update-db-native.bb |  3 +
> >  meta/recipes-core/meta/cve-update-native.inc  | 59 ++++++++++++-------
> >  .../meta/cve-update-nvd2-native.bb            |  3 +
> >  4 files changed, 46 insertions(+), 21 deletions(-)
>
> I am a bit worried about this since it takes what is a simple mtime
> comparison and means that to check the database you now have to lock
> and open it which is comparatively expensive.
>
> What kind of "unassociated processes" are updating the mtime?
>
>
I second Richard here. If we would really want to keep the date somewhere
else than the file
timestamp, we could create a simple file that stores it, what is way
simpler and doesn't require
to open the database just to see if you want to update it.

I second Richard's question: in what kind of a situation have you seen an
issue?

Kind regards,
Marta
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#226124): 
https://lists.openembedded.org/g/openembedded-core/message/226124
Mute This Topic: https://lists.openembedded.org/mt/116098343/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to