mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavitra Jha <jhapavitra98@gmail.com>
To: Slava.Dubeyko@ibm.com
Cc: idryomov@gmail.com, amarkuze@redhat.com,
	ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] ceph: fix bare ceph_decode_8 OOB in decode_lockers()
Date: Thu, 28 May 2026 14:17:41 -0400	[thread overview]
Message-ID: <20260528181741.880777-1-jhapavitra98@gmail.com> (raw)
In-Reply-To: <581a303fac01d2854bc32cf2afff928990026aa0.camel@ibm.com>

Hi Slava,

Sorry for the confusion here.

The original patch fixing:

*num_lockers = ceph_decode_32(p);

and the later fix for:

*type = ceph_decode_8(p);

were intended as two separate incremental fixes, 

not as replacement versions of the same patch.

I mistakenly labeled the second one as "[PATCH v2]" and also 

sent it as a separate thread, which made the relationship unclear.

I'll resend this properly as a clean patch series.

Thanks,
Pavitra

  reply	other threads:[~2026-05-28 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23  8:59 [PATCH] ceph: fix multiple unsafe decodes in decode_locker() Pavitra Jha
2026-05-26 19:18 ` Viacheslav Dubeyko
2026-05-28 13:01   ` [PATCH v2] " Pavitra Jha
2026-05-28 18:14     ` Viacheslav Dubeyko
2026-05-28 18:17       ` Pavitra Jha [this message]
2026-06-02  5:02       ` [PATCH v3] " Pavitra Jha
2026-05-26 19:04 [PATCH] ceph: fix OOB read in decode_lockers() via missing bounds check Viacheslav Dubeyko
2026-05-28 13:25 ` [PATCH v2] ceph: fix bare ceph_decode_8 OOB in decode_lockers() Pavitra Jha
2026-05-28 18:06   ` Viacheslav Dubeyko
2026-05-30 17:46   ` Dan Carpenter

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=20260528181741.880777-1-jhapavitra98@gmail.com \
    --to=jhapavitra98@gmail.com \
    --cc=Slava.Dubeyko@ibm.com \
    --cc=amarkuze@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome