lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 25 Mar 2022 10:14:13 -0400
From:   Willem de Bruijn <>
To:     Vladimir Oltean <>
Cc:     Willem de Bruijn <>,, Paolo Abeni <>,
        Jakub Kicinski <>,
        "David S. Miller" <>
Subject: Re: Broken SOF_TIMESTAMPING_OPT_ID in linux-4.19.y and earlier stable branches

On Fri, Mar 25, 2022 at 10:07 AM Vladimir Oltean <> wrote:
> On Fri, Mar 25, 2022 at 09:48:41AM -0400, Willem de Bruijn wrote:
> > > Do you have any particular concerns about sending this patch to the
> > > linux-stable branches for 4.19, 4.14 and 4.9? From
> > > I see those are the only stable branches left.
> >
> > The second patch does not apply cleanly to 4.14.y and even the first
> > (one-liner) has a conflict on 4.9.y.
> >
> > It would be good to verify by running the expanded
> > tools/testing/selftests/net/txtimestamp.c against the patched kernels
> > first. That should serve as a good test whether the feature works on a
> > kernel, re: that previous point.
> >
> > If you want to test and send the 4.19.y patch, please go ahead. Or I
> > can do it, but it will take some time.
> I think I do have a setup where I can test all 3 stable kernels.
> I'll see if I can backport the SO_TIMESTAMPING fixes to them and
> validate using the kernel selftest and my app. If I'm successful,
> I'll attach the patchsets here for you to review, then send to stable if
> you're okay, would that work?

Awesome, thanks. Please don't send them as attachments to the list.
Standard text patches preferably. Off-list is fine too.

Powered by blists - more mailing lists