From: Dan Carpenter <dan.carpenter@linaro.org>
To: Alex Markuze <amarkuze@redhat.com>
Cc: Alex Elder <elder@riscstar.com>, Jeff Layton <jlayton@kernel.org>,
ceph-devel@vger.kernel.org
Subject: Re: [bug report] ceph: decode interval_sets for delegated inos
Date: Wed, 4 Dec 2024 20:05:43 +0300 [thread overview]
Message-ID: <bb34b6aa-730a-418d-bb25-20ad003779e6@stanley.mountain> (raw)
In-Reply-To: <CAO8a2SgNuGyvH+jcCbaVO0p1fRfOd7_Kuo9MuUDCnDwxNt1SoA@mail.gmail.com>
On Wed, Dec 04, 2024 at 03:12:31PM +0200, Alex Markuze wrote:
> Dan, how are you running smatch?
> I've been looking at smatch warnings/errors and don't get this error.
> Do you have a custom smatch checker?
This is released code, but there are two possible explanations for why you
wouldn't see the warning:
1) Are you using the cross function database? Each time you rebuild the
database then it adds another layer to the call tree. EDIT: But
actually in this case, it doesn't matter because Smatch hardcodes
ceph_decode_64() as returning user data so the database isn't
required.
2) This bug only affects 32bit .configs and I suspect you're building for
64bit kernels.
regards,
dan carpenter
prev parent reply other threads:[~2024-12-04 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 8:19 [bug report] ceph: decode interval_sets for delegated inos Dan Carpenter
2024-12-03 8:25 ` Dan Carpenter
2024-12-03 14:07 ` Jeff Layton
2024-12-03 17:06 ` Alex Elder
2024-12-03 18:29 ` Dan Carpenter
2024-12-04 12:50 ` Alex Markuze
2024-12-04 13:12 ` Alex Markuze
2024-12-04 17:05 ` 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=bb34b6aa-730a-418d-bb25-20ad003779e6@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@riscstar.com \
--cc=jlayton@kernel.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.