From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] mm/damon/sysfs: fix unhandled return values
Date: Mon, 6 Nov 2023 23:34:05 +0000 [thread overview]
Message-ID: <20231106233408.51159-1-sj@kernel.org> (raw)
Some of DAMON sysfs interface code is not handling return values from
some functions. As a result, confusing user input handling or
NULL-dereference is possible. Check those properly.
Please note that these patches are not cleanly applicable on mm-unstable
since mm-unstable has dropped the mainline-merged patches and rebased on
v6.6, while some DAMON patches that these patches are depend on are
merged in the mainline after v6.6. I confirmed these patches can
cleanly applied on latest mainline, or mm-stable-2023-11-01-14-33.
SeongJae Park (3):
mm/damon/sysfs: check error from damon_sysfs_update_target()
mm/damon/sysfs-schemes: handle tried regions sysfs directory
allocation failure
mm/damon/sysfs-schemes: handle tried region directory allocation
failure
mm/damon/sysfs-schemes.c | 5 +++++
mm/damon/sysfs.c | 4 +++-
2 files changed, 8 insertions(+), 1 deletion(-)
base-commit: 3496e8e0a1eeabb738105c09e575495fa78914bb
--
2.34.1
next reply other threads:[~2023-11-06 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 23:34 SeongJae Park [this message]
2023-11-06 23:34 ` [PATCH 1/3] mm/damon/sysfs: check error from damon_sysfs_update_target() SeongJae Park
2023-11-06 23:34 ` [PATCH 2/3] mm/damon/sysfs-schemes: handle tried regions sysfs directory allocation failure SeongJae Park
2023-11-06 23:34 ` [PATCH 3/3] mm/damon/sysfs-schemes: handle tried region " SeongJae Park
2023-11-06 23:51 ` [PATCH 0/3] mm/damon/sysfs: fix unhandled return values SeongJae Park
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=20231106233408.51159-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-mm@kvack.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 read-only IMAP folder(s) and NNTP newsgroup(s).