All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "chensong_2000@189.cn" <chensong_2000@189.cn>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"chensong@tj.kylinos.cn" <chensong@tj.kylinos.cn>
Subject: Re: y2038 wiki/roadmap and development branch update
Date: Mon, 26 Apr 2021 09:33:04 +0000	[thread overview]
Message-ID: <da58f467a5fed5dce870c46633f79f54aa0710a2.camel@siemens.com> (raw)
In-Reply-To: <f16dfe97-865f-37ae-5979-11696f3c12bc@189.cn>

On Mon, 2021-04-26 at 17:21 +0800, chensong_2000@189.cn wrote:
> 
> 在 2021/4/23 下午11:30, Bezdeka, Florian 写道:
> > Hi Song,
> > 
> > I just moved the y2038 roadmap we once prepared in my personal
> > gitlab.com project to the official Xenomai hackerspace [1].
> > 
> > In addition there is now a florian/y2038 branch in the Xenomai
> > hackerspace [2] which holds the current state. This branch is based on
> > current wip/dovetail, so it's not a stable branch and might be rebased
> > whenever needed.
> > 
> > While updating the roadmap I just realized that we already missed two
> > affected syscalls, which (according to the current syscall table
> > ordering) would be the first two:
> >    - sc_cobalt_thread_setschedparam_ex
> >    - sc_cobalt_thread_getschedparam_ex
> 
> i looked into functions thread_setschedparam_ex/thread_getschedparam_ex, 
> didn't find anything about time64, but i will keep it in mind.

There is a struct sched_param_ex coming in as parameter which holds
struct __sched_rr_param which holds struct __user_old_timespec which is
not y2038 safe.

> 
> > 
> > I updated the roadmap accordingly and re-sorted the table. Would be
> > nice if you could double-check that again.
> 
> done, thanks
> > 

      reply	other threads:[~2021-04-26  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 15:30 y2038 wiki/roadmap and development branch update Bezdeka, Florian
2021-04-26  9:21 ` chensong_2000
2021-04-26  9:33   ` Bezdeka, Florian [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=da58f467a5fed5dce870c46633f79f54aa0710a2.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=chensong@tj.kylinos.cn \
    --cc=chensong_2000@189.cn \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.org \
    /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.