All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [bug report] firmware: arm_scmi: Call Raw mode hooks from the core stack
Date: Mon, 23 Jan 2023 15:46:27 +0300	[thread overview]
Message-ID: <Y86Bo/LD8u5rstpH@kadam> (raw)
In-Reply-To: <Y8geNvMFyXWIqUm2@e120937-lin>

On Wed, Jan 18, 2023 at 04:28:38PM +0000, Cristian Marussi wrote:
> On Wed, Jan 18, 2023 at 06:41:19PM +0300, Dan Carpenter wrote:
> > On Tue, Jan 17, 2023 at 02:14:30PM +0000, Cristian Marussi wrote:
> > > 
> > > I'm still puzzled why I regularly do not catch these errors on my smatch
> > > setup running kchecker which does only reports me a bunch of errors on
> > > core bitops code. (I have recently pulled updated smatch branch...)
> > 
> > This check requires the cross function database to work.  Building the
> > cross function database is easy enough, but takes overnight.
> > 
> > ~/smatch/smatch_scripts/build_kernel_data.sh
> > 
> 
> Thanks I'll try.
> 
> BTW I'm using v1.73 and I also see since a while a lot of errors like:
> 
> internal error: file too large:  db/kernel.return_fixes (limit 4096 bytes)
> 

That's an interesting thing.  I had to make db/kernel.return_fixes
larger a few months back, but why is the db/kernel.return_fixes out of
sync with the code to parse it in v1.73?

> internal error: dev/src/pdsw/linux/arch/arm64/include/asm/jump_label.h:38 SQL error #2: UNIQUE constraint failed: mtag_data.tag, mtag_data.offset, mtag_data.type, mtag_data.value
> 
> internal error: dev/src/pdsw/linux/arch/arm64/include/asm/jump_label.h:38 SQL: 'insert into mtag_data values (7179031484371304448, 0, 8041, '1:      b               %l[l_yes]               \n.pushsection     __jump_table, "aw"      \n              .align          3                       \n              .long           1b - ., %l[l_yes] - .   \n              .quad           %c0 - .                 \n.popsection                              \n      ');'
> 
> Trying to revert back a few months of commits and those errors disappear.
> Is it related to have stale DB ?

Yep.  Probably.

Can you retry on the latest git?

regards,
dan carpenter


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-01-23 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 10:29 [bug report] firmware: arm_scmi: Call Raw mode hooks from the core stack Dan Carpenter
2023-01-17 14:14 ` Cristian Marussi
2023-01-18 15:41   ` Dan Carpenter
2023-01-18 16:28     ` Cristian Marussi
2023-01-23 12:46       ` Dan Carpenter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y86Bo/LD8u5rstpH@kadam \
    --to=error27@gmail.com \
    --cc=cristian.marussi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.