All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Ricardo Branco" <rbranco@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] userfaultfd: Minor fixes
Date: Thu, 26 Mar 2026 12:38:35 +0000	[thread overview]
Message-ID: <69c528cc.5d0a0220.15fc5b.6425@mx.google.com> (raw)
In-Reply-To: <33458536-f2e1-4ab8-a7b7-5882481dfa9b@suse.de>

Hi Ricardo,

> 
> On 3/26/26 9:38 AM, Andrea Cervesato wrote:
> > Hi ricardo,
> >
> >> +	if (page) {
> >> +		SAFE_MUNMAP(page, page_size);
> >> +		SAFE_MUNMAP(copy_page, page_size);
> >> +		page = NULL;
> >> +	}
> > This is gonna TBROK when copy_page is NULL. The same apply to all other
> > tests which are affected by the same bug.
> 
> Fixed in v3.
> 
> BTW, we have a minor difference in tests:
> 
> $ diff userfaultfd03.c userfaultfd06.c
> 
> <         tst_brk(TBROK | TERRNO, "Received unexpected UFFD_EVENT %d", 
> msg.event);
> ---
>  >         tst_brk(TFAIL, "Received unexpected UFFD_EVENT %d", msg.event);
> 
> I think we should have TFAIL, WDYT?

It depends on the subject of our test and both tests are actually testing
other features than the specific uffd_msg attributes when an event is
recevied. For this reason I would keep TBROK in both of them.

I see that also userfaultfd05 has the same issue. I don't remember the full
conversation before merging the patches, but if none mentioned a reason in
there, the tests will need to be adapted.

Regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com

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

      parent reply	other threads:[~2026-03-26 12:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 15:47 [LTP] [PATCH v2] userfaultfd: Minor fixes Ricardo Branco
2026-03-26  8:38 ` Andrea Cervesato via ltp
2026-03-26 11:37   ` Ricardo Branco
2026-03-26 12:32     ` Petr Vorel
2026-03-26 12:43       ` Andrea Cervesato via ltp
2026-03-26 13:12         ` Petr Vorel
2026-03-26 12:38     ` Andrea Cervesato via ltp [this message]

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=69c528cc.5d0a0220.15fc5b.6425@mx.google.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.com \
    --cc=rbranco@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.