From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nathan@kernel.org" <nathan@kernel.org>,
"justinstitt@google.com" <justinstitt@google.com>,
"idryomov@gmail.com" <idryomov@gmail.com>,
Xiubo Li <xiubli@redhat.com>,
"nick.desaulniers+lkml@gmail.com"
<nick.desaulniers+lkml@gmail.com>,
"morbo@google.com" <morbo@google.com>
Subject: Re: [PATCH v1 1/1] libceph: Amend checking to fix `make W=1` build breakage
Date: Mon, 10 Nov 2025 21:36:02 +0200 [thread overview]
Message-ID: <aRI-ohUyQLxIY1vu@smile.fi.intel.com> (raw)
In-Reply-To: <8d1983c9d4c84a6c78b72ba23aa196e849b465a1.camel@ibm.com>
On Mon, Nov 10, 2025 at 07:28:36PM +0000, Viacheslav Dubeyko wrote:
> On Mon, 2025-11-10 at 15:46 +0100, Andy Shevchenko wrote:
...
> > ceph_decode_32_safe(p, end, len, e_inval);
> > if (len == 0 && incremental)
> > return NULL; /* new_pg_temp: [] to remove */
> > - if (len > (SIZE_MAX - sizeof(*pg)) / sizeof(u32))
> > + if ((size_t)len > (SIZE_MAX - sizeof(*pg)) / sizeof(u32))
> > return ERR_PTR(-EINVAL);
> >
> > ceph_decode_need(p, end, len * sizeof(u32), e_inval);
> I am guessing... What if we change the declaration of len on size_t, then could
> it be more clear solution here? For example, let's consider this for both cases:
>
> size_t len, i;
>
> Could it eliminate the issue and to make the Clang happy? Or could it introduce
> another warnings/issues?
Probably, but the code is pierced with the sizeof(u32) and alike, moreover
size_t is architecture-dependent type, while the set of macros in decode.h
seems to operate on the fixed-width type. That said, I prefer my way of fixing
this. But if you find another, better one, I am all ears!
*Also note, I'm not familiar with the guts of the ceph, so maybe your solution
is the best, but I want more people to confirm this.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-10 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 14:46 [PATCH v1 1/1] libceph: Amend checking to fix `make W=1` build breakage Andy Shevchenko
2025-11-10 19:28 ` Viacheslav Dubeyko
2025-11-10 19:36 ` andriy.shevchenko [this message]
2025-11-10 20:39 ` Viacheslav Dubeyko
2025-11-24 15:09 ` andriy.shevchenko
2025-11-24 17:45 ` Viacheslav Dubeyko
2025-11-24 18:44 ` andriy.shevchenko
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=aRI-ohUyQLxIY1vu@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Slava.Dubeyko@ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=xiubli@redhat.com \
/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.