From: Petr Vorel <pvorel@suse.cz>
To: Pengfei Xu <pengfei.xu@intel.com>
Cc: Heng Su <heng.su@intel.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1 1/1] keyctl05: increase dns_res_payload data due to kernel code changes
Date: Wed, 10 Jan 2024 18:59:31 +0100 [thread overview]
Message-ID: <20240110175931.GA1766165@pevik> (raw)
In-Reply-To: <f60daf00d0de49e54a5389c73c90994e7711a7d1.1704868967.git.pengfei.xu@intel.com>
Hi Xu,
Good catch, merged.
BTW any change how to trigger autoload of dns_resolver ?
# ./keyctl05
...
keyctl05.c:99: TCONF: kernel doesn't support key type 'dns_resolver'
...
# modprobe dns_resolver
# ./keyctl05
...
keyctl05.c:143: TPASS: updating 'dns_resolver' key expectedly failed with EOPNOTSUPP
...
We consider modprobe as the last result.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-01-10 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1704868967.git.pengfei.xu@intel.com>
2024-01-10 6:50 ` [LTP] [PATCH v1 1/1] keyctl05: increase dns_res_payload data due to kernel code changes Pengfei Xu
2024-01-10 17:59 ` Petr Vorel [this message]
2024-01-11 3:02 ` Pengfei Xu
2024-01-11 8:25 ` Petr Vorel
2024-01-11 8:24 ` Pengfei Xu
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=20240110175931.GA1766165@pevik \
--to=pvorel@suse.cz \
--cc=heng.su@intel.com \
--cc=ltp@lists.linux.it \
--cc=pengfei.xu@intel.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