public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Pengfei Xu <pengfei.xu@intel.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Heng Su <heng.su@intel.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1 1/1] keyctl05: improve the dns_res_payload for boundary testing
Date: Thu, 11 Jan 2024 20:24:42 +0800	[thread overview]
Message-ID: <ZZ/eCt9jeCNYMMff@xpf.sh.intel.com> (raw)
In-Reply-To: <20240111100949.GA1895489@pevik>

Hi Petr,

On 2024-01-11 at 11:09:49 +0100, Petr Vorel wrote:
> Hi Xu,
> 
> > Because the following patch will fix the add_key syscall incoming data boundary
> > size issue, 6 bytes incoming data should pass:
> > https://lore.kernel.org/all/1784441.1704907412@warthog.procyon.org.uk/
> >  -> https://lore.kernel.org/all/1850031.1704921100@warthog.procyon.org.uk/
> > In order to test above boundary incoming data size, change the dns_res_payload
> > size.
> 
> I'm sorry, I was faster and just fixed \ myself.
> Rebasing is trivial, but there was missing commit (already merged and other
> things). Thus I have sent v2 under your name (which I actually forget to mark
> as v2 :().
> 
> https://lore.kernel.org/ltp/20240111100636.1897637-1-pvorel@suse.cz/
> https://patchwork.ozlabs.org/project/ltp/patch/20240111100636.1897637-1-pvorel@suse.cz/
> 
> Can you please have a look on it?

Yes, it's better to add the linux-git acc657692aed and it looks good.
Thanks for your improvment!

Best Regards,
Thanks!

> 
> Kind regards,
> Petr
> 
> > Signed-off-by: Pengfei Xu <pengfei.xu@intel.com>
> > ---
> >  testcases/kernel/syscalls/keyctl/keyctl05.c | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> > diff --git a/testcases/kernel/syscalls/keyctl/keyctl05.c b/testcases/kernel/syscalls/keyctl/keyctl05.c
> > index 90cf1ef06..50e78853c 100644
> > --- a/testcases/kernel/syscalls/keyctl/keyctl05.c
> > +++ b/testcases/kernel/syscalls/keyctl/keyctl05.c
> > @@ -199,11 +199,11 @@ static void do_test(unsigned int i)
> >  	 * We need to pass check in dns_resolver_preparse(),
> >  	 * give it dummy server list request.
> >  	 * From v6.7-rc8 commit 1997b3cb4217b09e49659b634c94da47f0340409:
> > -	 * the incoming data for add_key syscall should be larger than 6 bytes,
> > -	 * because struct dns_server_list_v1_header without body is 6 bytes.
> > +	 * the incoming data for add_key syscall should be not less than 6
> > +	 * bytes, because struct dns_server_list_v1_header is 6 bytes.
> > +	 * The minimum payload will be tested here for boundary testing.
> >  	 */
> > -	static char dns_res_payload[] = { 0x00, 0x00, 0x01, 0xff, 0x00, \
> > -					  0x00, 0x00 };
> > +	static char dns_res_payload[] = { 0x00, 0x00, 0x01, 0xff, 0x00, 0x00 };
> 
> >  	switch (i) {
> >  	case 0:

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

  reply	other threads:[~2024-01-11 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1704949719.git.pengfei.xu@intel.com>
2024-01-11  5:09 ` [LTP] [PATCH v1 1/1] keyctl05: improve the dns_res_payload for boundary testing Pengfei Xu
2024-01-11  8:51   ` Petr Vorel
2024-01-11  9:12     ` Pengfei Xu
2024-01-11 10:09   ` Petr Vorel
2024-01-11 12:24     ` Pengfei Xu [this message]
2024-01-22 18:22       ` Petr Vorel
2024-01-23  1:23         ` 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=ZZ/eCt9jeCNYMMff@xpf.sh.intel.com \
    --to=pengfei.xu@intel.com \
    --cc=heng.su@intel.com \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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