From: Catalin Marinas <catalin.marinas@arm.com>
To: "André Almeida" <andrealmeid@collabora.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, akpm@linux-foundation.org
Subject: Re: [PATCH v2 1/2] mm: kmemleak: change error at _write when kmemleak is disabled
Date: Thu, 13 Jun 2019 13:22:43 +0100 [thread overview]
Message-ID: <20190613122243.GQ28951@C02TF0J2HF1T.local> (raw)
In-Reply-To: <20190612155231.19448-1-andrealmeid@collabora.com>
On Wed, Jun 12, 2019 at 12:52:30PM -0300, André Almeida wrote:
> According to POSIX, EBUSY means that the "device or resource is busy",
> and this can lead to people thinking that the file
> `/sys/kernel/debug/kmemleak/` is somehow locked or being used by other
> process. Change this error code to a more appropriate one.
>
> Signed-off-by: André Almeida <andrealmeid@collabora.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
prev parent reply other threads:[~2019-06-13 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 15:52 André Almeida
2019-06-12 15:52 ` [PATCH v2 2/2] docs: kmemleak: add more documentation details André Almeida
2019-06-13 12:23 ` Catalin Marinas
2019-06-13 12:22 ` Catalin Marinas [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=20190613122243.GQ28951@C02TF0J2HF1T.local \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@collabora.com \
--cc=kernel@collabora.com \
--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