From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
gregkh@linuxfoundation.org, badari.pulavarty@intel.com,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/damon/dbgfs: avoid duplicate context directory creation
Date: Fri, 19 Aug 2022 23:05:01 +0000 [thread overview]
Message-ID: <20220819230501.16830-1-sj@kernel.org> (raw)
In-Reply-To: <20220819154451.9f424d9d563969d9cc6437f7@linux-foundation.org>
On Fri, 19 Aug 2022 15:44:51 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 19 Aug 2022 21:16:31 +0000 SeongJae Park <sj@kernel.org> wrote:
>
> > > It would be simpler (and less racy) to check the debugfs_create_dir()
> > > return value for IS_ERR()?
> >
> > I was merely following Greg's previous advice for ignoring the return value[1]
> > of the function, but I might misunderstanding his intention, so CC-ing Greg.
> > Greg, may I ask your opinion?
> >
> > [1] https://lore.kernel.org/linux-mm/YB1kZaD%2F7omxXztF@kroah.com/
>
> Thing is, the correct functioning of the debugfs interfaces is utterly
> critical to damon. And that's apart from these memory leak and
> oops-we-killed-damon issues.
>
> So damon simply cannot ignore the state of its debugfs interfaces and
> keep going along - because if something goes wrong at the debugfs
> layer, damon is dead and useless and the machine needs a reboot.
>
> Perhaps this means that damon should not be using debugfs for its
> interfaces at all. Or it means that the debugfs interfaces are
> misdesigned. I go with the latter, which, alas, also affirms the
> former.
I'd save my word about the latter, but agreed on the former. Fortunately we
already have an alternative (DAMON sysfs interface), and the debugfs interface
deprecation plan was announced for a while ago. Not sure if the deprecation
will be well as hoped, though.
>
> From a quick scan it appears that a significant minority (20%?) of
> drivers are checking the debugfs_create_dir() return value.
Maybe partly owing to Greg's previous efforts for removing the checks[1,2]?
Anyway, based on the previous discussions, I'd expect Greg might prefer not
checking the return code.
Anyway, waiting for his opinion.
[1] https://lore.kernel.org/all/20190122152151.16139-14-gregkh@linuxfoundation.org/
[2] https://lore.kernel.org/lkml/20190122152151.16139-7-gregkh@linuxfoundation.org/
Thanks,
SJ
next prev parent reply other threads:[~2022-08-19 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 17:19 [PATCH v2] mm/damon/dbgfs: avoid duplicate context directory creation SeongJae Park
2022-08-19 21:08 ` Andrew Morton
2022-08-19 21:16 ` SeongJae Park
2022-08-19 22:44 ` Andrew Morton
2022-08-19 23:05 ` SeongJae Park [this message]
2022-08-20 17:32 ` Greg KH
2022-08-21 17:52 ` SeongJae Park
2022-08-20 2:29 ` Bagas Sanjaya
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=20220819230501.16830-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=badari.pulavarty@intel.com \
--cc=damon@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.