From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org
Cc: Marco Elver <elver@google.com>, Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH v2 0/2] kcsan: debugs: Refactor allocation code
Date: Thu, 21 Nov 2024 16:17:11 +0200 [thread overview]
Message-ID: <Zz9A59XQdiHJ8oLp@smile.fi.intel.com> (raw)
In-Reply-To: <20241121141412.107370-1-andriy.shevchenko@linux.intel.com>
On Thu, Nov 21, 2024 at 04:12:50PM +0200, Andy Shevchenko wrote:
> Refactor allocation code to be more robust against overflows
> and shorted in terms of LoCs.
>
> In v2:
> - collected tags (Marco)
> - added patch 2
Okay, it seems I have to check the Linux Next for the current state of
affairs...
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-11-21 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 14:12 [PATCH v2 0/2] kcsan: debugs: Refactor allocation code Andy Shevchenko
2024-11-21 14:12 ` [PATCH v2 1/2] kcsan: debugfs: Use krealloc_array() to replace krealloc() Andy Shevchenko
2024-11-21 14:12 ` [PATCH v2 2/2] kcsan: debugfs: Use krealloc_array() for initial allocation as well Andy Shevchenko
2024-11-21 14:17 ` Andy Shevchenko [this message]
2024-11-21 14:19 ` [PATCH v2 0/2] kcsan: debugs: Refactor allocation code Marco Elver
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=Zz9A59XQdiHJ8oLp@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@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