From: Stefano Brivio <sbrivio@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Pablo Neira Ayuso <pablo@netfilter.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] lib: Fix bitmap_cut() for overlaps, add test
Date: Sun, 14 Jun 2020 19:40:52 +0200 [thread overview]
Message-ID: <cover.1592155364.git.sbrivio@redhat.com> (raw)
Patch 1/2 addresses the issue Yury reported with partially overlapping
src and dst in bitmap_cut(), and 2/2 adds a test that covers basic
functionality as well as this case.
v2: In 2/2, use macro to verify result, drop bogus Co-Authored-by:
tag, both suggested by Andy Shevchenko, and avoid stack overflow
Stefano Brivio (2):
bitmap: Fix bitmap_cut() for partial overlapping case
bitmap: Add test for bitmap_cut()
lib/bitmap.c | 4 ++--
lib/test_bitmap.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 60 insertions(+), 2 deletions(-)
--
2.27.0
next reply other threads:[~2020-06-14 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 17:40 Stefano Brivio [this message]
2020-06-14 17:40 ` [PATCH 1/2] bitmap: Fix bitmap_cut() for partial overlapping case Stefano Brivio
2020-06-15 9:42 ` Andy Shevchenko
2020-06-14 17:40 ` [PATCH 2/2] bitmap: Add test for bitmap_cut() Stefano Brivio
2020-06-15 9:41 ` Andy Shevchenko
2020-06-15 9:46 ` Andy Shevchenko
2020-06-15 11:08 ` Stefano Brivio
2020-06-15 11:43 ` Andy Shevchenko
2020-06-15 13:16 ` Stefano Brivio
2020-06-15 12:04 ` Alexander Gordeev
-- strict thread matches above, loose matches on Subject: below --
2020-06-08 9:13 [PATCH 0/2] lib: Fix bitmap_cut() for overlaps, add test Stefano Brivio
2020-06-08 10:13 ` Andy 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=cover.1592155364.git.sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pablo@netfilter.org \
--cc=yury.norov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome