Re: [PATCH v4] refs/reftable: fix uninitialized memory access of `max_index`

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Patrick Steinhardt <ps@xxxxxx> writes:

> On Mon, Jan 27, 2025 at 10:44:08AM +0100, Patrick Steinhardt wrote:
>> Karthik is out of office this week, so I'm taking over this series for
>> him to ensure that it lands soonish. The only change compared to v3 is
>> an adapted commit message based on my own feedback.
>
> Ugh, sorry, forgot to set the In-reply-to header. This was meant as a
> reply to [1].
>
> Patrick
>
> [1]: <CAOLa=ZR=Hz+LU0n-uC2dpk8_sLqAyaxO0NswJH8bP_kEdDdbUQ@xxxxxxxxxxxxxx>

Thanks, that was very helpful.  This turns the v3 that was a
replacement for a patch that was already in 'next' into an
incremental form, and replaces the kn/reflog-migration-fix-fix topic
which was my tentative attempt.

Will queue.




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux