From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>, "Takashi Iwai" <tiwai@suse.de>
Cc: "Peter Huewe" <peterhuewe@gmx.de>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
<linux-integrity@vger.kernel.org>,
"Andy Liang" <andy.liang@hpe.com>, <jenifer.golmitz@hpe.com>
Subject: Re: [PATCH] tpm/eventlog: Use kvmalloc() for event log buffer
Date: Thu, 07 Nov 2024 22:44:17 +0200 [thread overview]
Message-ID: <D5G8MT5N7M3M.3PW6KDINE6GEF@kernel.org> (raw)
In-Reply-To: <D5G8DXQ15SFC.SDV9NC2LH1CF@kernel.org>
On Thu Nov 7, 2024 at 10:32 PM EET, Jarkko Sakkinen wrote:
> >
> > This patch replaces the devm_kmalloc() call with kvmalloc() to allow
> > larger sizes. Since there is no devm variant for kvmalloc(), now it's
> > managed manually via devres_alloc() and devres_add().
> >
> > Reported-and-tested-by: Andy Liang <andy.liang@hpe.com>
> > Cc: jenifer.golmitz@hpe.com
> > Link: https://bugzilla.suse.com/show_bug.cgi?id=1232421
>
> "You are not authorized to access bug #1232421. To see this bug, you must
> first log in to an account with the appropriate permissions."
>
> Please remove this link as it gives no information without login
> access, *or* make it available w/o acocunt, *or* repost a bug to the
> kernel bugzilla.
>
> I've been cursing SUSE accounts for over a year now. Never been able
> to successfully get either to the bugzilla or forums (still I get
> some weekly spam about the forums). And no, no interest to recall
> or figure out this problem.
Just a personal recommendation but I'd create a bug to kernel bugzilla
and link that to the SUSE bug, and call it a day ;-) It would be the
least friction approach.
BR, Jarkko
next prev parent reply other threads:[~2024-11-07 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 11:18 [PATCH] tpm/eventlog: Use kvmalloc() for event log buffer Takashi Iwai
2024-11-07 12:17 ` Paul Menzel
2024-11-07 12:38 ` Takashi Iwai
2024-11-07 19:06 ` Stefan Berger
2024-11-07 19:31 ` Stefan Berger
2024-11-08 8:24 ` Takashi Iwai
2024-11-08 8:48 ` Liang, Andy (Linux Ecosystem Engineering)
2024-11-08 9:28 ` Takashi Iwai
2024-11-11 8:43 ` Liang, Andy (Linux Ecosystem Engineering)
2024-11-12 17:56 ` Jarkko Sakkinen
2024-11-13 3:00 ` Liang, Andy (Linux Ecosystem Engineering)
2024-11-07 20:42 ` Jarkko Sakkinen
2024-11-08 8:22 ` Takashi Iwai
2024-11-07 20:32 ` Jarkko Sakkinen
2024-11-07 20:44 ` Jarkko Sakkinen [this message]
2024-11-08 8:21 ` Takashi Iwai
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=D5G8MT5N7M3M.3PW6KDINE6GEF@kernel.org \
--to=jarkko@kernel.org \
--cc=andy.liang@hpe.com \
--cc=jenifer.golmitz@hpe.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tiwai@suse.de \
/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.