Linux Test Project
 help / color / mirror / Atom feed
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: Thu, 11 Jan 2024 09:25:49 +0100	[thread overview]
Message-ID: <20240111082549.GA1856272@pevik> (raw)
In-Reply-To: <ZZ9aR/SEWl57q6aR@xpf.sh.intel.com>

> Hi Petr,

> On 2024-01-10 at 18:59:31 +0100, Petr Vorel wrote:
> > 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.

> Yes, it needs to load dns_resolver module to test it.
> Or set kconfig CONFIG_DNS_RESOLVER=y.

Well, that would not work for kernels in linux distros.
Therefore I'll send a patch to add modprobe functionality.

> Due to the bundary issue fixed patch as follows, I will send another patch to
> set to 6 bytes coming data for add_key syscall for passed boundary checking:
> https://lore.kernel.org/all/1784441.1704907412@warthog.procyon.org.uk/

Thank you!

FYI we're planning LTP release in the end of month, it'd be great if you send
patch soon so that fix is included.

Kind regards,
Petr

> BR,
> Thanks!


> > Kind regards,
> > Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-01-11  8:26 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
2024-01-11  3:02     ` Pengfei Xu
2024-01-11  8:25       ` Petr Vorel [this message]
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=20240111082549.GA1856272@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