public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] Holidays and LTP release
Date: Tue, 12 Jan 2021 11:29:58 +0100	[thread overview]
Message-ID: <X/16JnZ4MmA6PINI@pevik> (raw)
In-Reply-To: <X/xi2iBZZFixnCQo@yuki.lan>

Hi Cyril,

> Hi!
> As I anounced last week please consider git frozen for anything but
> important fixes now.

I was thinking about speedup if-mtu-change.sh [1], but unless Alexey ack that it
might be better to wait after the release.

I planned to merge two rewrites to new API (v2 get_mempolicy [2] and v3
multicast packed flood [3]), which are ready, but as there is a git freeze it
can wait after the release.

I'd also like to add some docs to ima_tpm.sh setup when running with
ima_policy=tcb on real HW, if I figure out what's needed.

I might have look into sigwaitinfo01 problems on MUSL.
There is a patch which needs to be rebased [4] (tests and libsigwait were
rewritten to new API). But simply remove all testcases because they does not
work on MUSL is probably no-go. I guess the problem is with using (void *)1 in
in various sigwaitinfo tests in test_bad_address{,2,3}()
(libs/libltpsigwait/sigwait.c).
Maybe use tst_get_bad_addr(NULL) here?

> Also if you haven't done so yet, please test latest git head now and
> report any problems you find.
Going to.

Kind regards,
Petr

[1] https://patchwork.ozlabs.org/project/ltp/patch/20210107120247.31465-1-pvorel@suse.cz/
[2] https://patchwork.ozlabs.org/project/ltp/patch/20210106181735.1588-1-pvorel@suse.cz/
[3] https://patchwork.ozlabs.org/project/ltp/list/?series=216562&state=*
[4] https://patchwork.ozlabs.org/project/ltp/patch/20200529014448.3815022-1-raj.khem@gmail.com/

  reply	other threads:[~2021-01-12 10:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 12:18 [LTP] Holidays and LTP release Cyril Hrubis
2021-01-06 12:19 ` Cyril Hrubis
2021-01-07 11:51   ` Cyril Hrubis
2021-01-08  1:23     ` Yang Xu
2021-01-08 13:28       ` Cyril Hrubis
2021-01-11 14:38     ` Cyril Hrubis
2021-01-12 10:29       ` Petr Vorel [this message]
2021-01-13  8:57   ` =?unknown-8bit?q?K=C3=B6ry?= Maincent
2021-01-14 11:12     ` Naresh Kamboju
2021-01-14 14:14       ` Martin Doucha
2021-01-20  9:31         ` Naresh Kamboju
2021-01-20 10:26           ` Cyril Hrubis
2021-01-20 13:33             ` Cyril Hrubis
2021-01-14 14:36       ` Cyril Hrubis
2021-01-15  8:27         ` Naresh Kamboju
2021-01-15 14:00           ` Cyril Hrubis
2021-01-15 14:27             ` Cyril Hrubis
2021-01-14  9:17   ` Martin Doucha
2021-01-14 10:41     ` Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2021-01-14 15:01 gengcixi
2021-01-15 15:08 gengcixi
2021-01-19 10:43 ` Cyril Hrubis

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=X/16JnZ4MmA6PINI@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /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