[OE-core] [PATCH 02/19] systemd: Fix time_t size assumptions

Khem Raj raj.khem at gmail.com
Mon Jan 6 16:48:00 UTC 2020


On Mon, Jan 6, 2020 at 3:25 AM Ross Burton <ross.burton at intel.com> wrote:
>
> On 29/12/2019 18:43, Khem Raj wrote:
> > Signed-off-by: Khem Raj <raj.khem at gmail.com>
> > ---
> >   ...ead-of-TIME_T_MAX-for-timerfd_settim.patch | 31 +++++++++++++++++++
> >   meta/recipes-core/systemd/systemd_243.2.bb    |  1 +
> >   2 files changed, 32 insertions(+)
> >   create mode 100644 meta/recipes-core/systemd/systemd/0022-Use-INT_MAX-instead-of-TIME_T_MAX-for-timerfd_settim.patch
> >
> > diff --git a/meta/recipes-core/systemd/systemd/0022-Use-INT_MAX-instead-of-TIME_T_MAX-for-timerfd_settim.patch b/meta/recipes-core/systemd/systemd/0022-Use-INT_MAX-instead-of-TIME_T_MAX-for-timerfd_settim.patch
> > new file mode 100644
> > index 0000000000..76a1c7364d
> > --- /dev/null
> > +++ b/meta/recipes-core/systemd/systemd/0022-Use-INT_MAX-instead-of-TIME_T_MAX-for-timerfd_settim.patch
> > @@ -0,0 +1,31 @@
> > +From 6bcf562bd1e541c7aa46923d9a14201c7f785261 Mon Sep 17 00:00:00 2001
> > +From: Khem Raj <raj.khem at gmail.com>
> > +Date: Mon, 16 Dec 2019 12:49:07 -0800
> > +Subject: [PATCH] Use INT_MAX instead of TIME_T_MAX for timerfd_settime timeout
> > +
> > +kernel prior to 64bit time_t support might not entertain such large
> > +timeout therefore reduce it to INT_MAX which would set timer expiration
> > +event after 68 years of uptime, should be good for all practical
> > +purposes
> > +
> > +Signed-off-by: Khem Raj <raj.khem at gmail.com>
>
> Missing Upstream-Status.  Have you send or discussed this upstream?
>

I had it on list of things to open pulls for haven't done yet. Thanks
for reminding me.

> Ross
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


More information about the Openembedded-core mailing list