From: Borislav Petkov <bp@alien8.de>
To: Jan Glauber <Jan.Glauber@cavium.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Sergey Temerkhanov <s.temerkhanov@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: EDAC, thunderx: memory leak in thunderx_l2c_threaded_isr()
Date: Mon, 15 Oct 2018 15:01:25 +0200 [thread overview]
Message-ID: <20181015130125.GC11434@zn.tnic> (raw)
Hi,
On Mon, Oct 15, 2018 at 12:47:24PM +0000, Jan Glauber wrote:
> the allocations happen only in the threaded function handlers, not in
> hard IRQ context, is that still an issue?
Nah, I take that back. I'm being told you can do almost everything in
threaded handler context! :-)
Thx.
next reply other threads:[~2018-10-15 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 13:01 Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-15 12:47 EDAC, thunderx: memory leak in thunderx_l2c_threaded_isr() Jan Glauber
2018-10-13 12:28 Borislav Petkov
2018-10-13 10:28 Dan Carpenter
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=20181015130125.GC11434@zn.tnic \
--to=bp@alien8.de \
--cc=Jan.Glauber@cavium.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=s.temerkhanov@gmail.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;
as well as URLs for NNTP newsgroup(s).