From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>, Shuah Khan <shuah@kernel.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix slab-out-of-bounds Write in dbgfs_rm_context_write
Date: Thu, 3 Nov 2022 16:14:03 +0000 [thread overview]
Message-ID: <20221103161403.115053-1-sj@kernel.org> (raw)
In-Reply-To: <20221031182554.7882-1-sj@kernel.org>
Hi Andrew,
May I ask you to merge this fix in your tree if you have no concern for this?
I think it deserves stable@.
Thanks,
SJ
On Mon, 31 Oct 2022 18:25:52 +0000 SeongJae Park <sj@kernel.org> wrote:
> This patchset is for fixing (patch 1) the syzbot-reported
> slab-out-of-bounds write in dbgfs_rm_context_write[1], and adding a
> selftest for the bug (patch 2).
>
> [1] https://lore.kernel.org/damon/000000000000ede3ac05ec4abf8e@google.com/
>
> SeongJae Park (2):
> mm/damon/dbgfs: check if rm_contexts input is for a real context
> selftests/damon: test non-context inputs to rm_contexts file
>
> mm/damon/dbgfs.c | 7 +++++++
> tools/testing/selftests/damon/Makefile | 1 +
> .../damon/debugfs_rm_non_contexts.sh | 19 +++++++++++++++++++
> 3 files changed, 27 insertions(+)
> create mode 100755 tools/testing/selftests/damon/debugfs_rm_non_contexts.sh
>
> --
> 2.25.1
prev parent reply other threads:[~2022-11-03 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 18:25 [PATCH 0/2] Fix slab-out-of-bounds Write in dbgfs_rm_context_write SeongJae Park
2022-10-31 18:25 ` [PATCH 1/2] mm/damon/dbgfs: check if rm_contexts input is for a real context SeongJae Park
2022-10-31 18:25 ` [PATCH 2/2] selftests/damon: test non-context inputs to rm_contexts file SeongJae Park
2022-11-03 16:14 ` SeongJae Park [this message]
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=20221103161403.115053-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).