From: Vlastimil Babka <vbabka@suse.cz>
To: Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Marco Elver <elver@google.com>, Jonathan Corbet <corbet@lwn.net>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Roman Gushchin <guro@fb.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 1/3] mm/slub: Clarify verification reporting
Date: Tue, 13 Oct 2020 18:13:33 +0200 [thread overview]
Message-ID: <cfdb11d7-fb8e-e578-c939-f7f5fb69a6bd@suse.cz> (raw)
In-Reply-To: <20201009195411.4018141-2-keescook@chromium.org>
On 10/9/20 9:54 PM, Kees Cook wrote:
> Instead of repeating "Redzone" and "Poison", clarify which sides of
> those zones got tripped. Additionally fix column alignment in the
> trailer.
>
> Before:
>
> BUG test (Tainted: G B ): Redzone overwritten
> ...
> Redzone (____ptrval____): bb bb bb bb bb bb bb bb ........
> Object (____ptrval____): f6 f4 a5 40 1d e8 ...@..
> Redzone (____ptrval____): 1a aa ..
> Padding (____ptrval____): 00 00 00 00 00 00 00 00 ........
>
> After:
>
> BUG test (Tainted: G B ): Right Redzone overwritten
> ...
> Redzone (____ptrval____): bb bb bb bb bb bb bb bb ........
> Object (____ptrval____): f6 f4 a5 40 1d e8 ...@..
> Redzone (____ptrval____): 1a aa ..
> Padding (____ptrval____): 00 00 00 00 00 00 00 00 ........
>
> Fixes: d86bd1bece6f ("mm/slub: support left redzone")
> Fixes: ffc79d288000 ("slub: use print_hex_dump")
> Fixes: 2492268472e7 ("SLUB: change error reporting format to follow lockdep loosely")
Not sure about those Fixes: tag as this is mainly an enhancement. I'd only use
those for real bug fixes.
> Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
next prev parent reply other threads:[~2020-10-13 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 19:54 [PATCH v2 0/3] Actually fix freelist pointer vs redzoning Kees Cook
2020-10-09 19:54 ` [PATCH v2 1/3] mm/slub: Clarify verification reporting Kees Cook
2020-10-13 16:13 ` Vlastimil Babka [this message]
2020-10-09 19:54 ` [PATCH v2 2/3] mm/slub: Fix redzoning for small allocations Kees Cook
2020-10-12 8:01 ` Christopher Lameter
2020-10-12 20:43 ` Kees Cook
2020-10-09 19:54 ` [PATCH v2 3/3] mm/slub: Actually fix freelist pointer vs redzoning Kees Cook
2020-10-13 16:44 ` Vlastimil Babka
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=cfdb11d7-fb8e-e578-c939-f7f5fb69a6bd@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=elver@google.com \
--cc=guro@fb.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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