From: "Balaji Pothunoori (QUIC)" <quic_bpothuno@quicinc.com>
To: "dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
"Balaji Pothunoori (QUIC)" <quic_bpothuno@quicinc.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: RE: [PATCH] dhcpcd: fix for unexpected syscall 135 for 10.1.0 version
Date: Wed, 5 Mar 2025 12:08:09 +0000 [thread overview]
Message-ID: <88cc44853dc94eb3b5b7a0c9abfa4ff3@quicinc.com> (raw)
In-Reply-To: <kxtt4okxjormycbnwxffxqadztn2mgzthuu6btjlkzqsdhihhc@deieyeztitxj>
> -----Original Message-----
> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Sent: Wednesday, March 5, 2025 2:17 PM
> To: Balaji Pothunoori (QUIC) <quic_bpothuno@quicinc.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [PATCH] dhcpcd: fix for unexpected syscall 135 for 10.1.0 version
>
> On Wed, Mar 05, 2025 at 12:11:01PM +0530, Balaji Pothunoori wrote:
> > Current dhcpcd (version 10.1.0) service crashes on the WiFi (wlan0)
> > interface with the following error:
>
> There are newer releases, which already have this patch. Any reason for not
> upgrading? For example there was an AUH message from March 1st.
Few patches are applied as OE Specific in https://git.openembedded.org/openembedded-core/tree/meta/recipes-connectivity/dhcpcd/files
Hence, I can't perform end to end testing for upgrade, So proceeded with patch BACKPORT for 10.1.0 version.
>
> >
> > "ps_seccomp_violation: unexpected syscall 135"
> >
> > This update pulls in fix #421 for dhcpcd 10.1.0 to address this issue.
> >
> > Signed-off-by: Balaji Pothunoori <quic_bpothuno@quicinc.com>
> > ---
> > .../dhcpcd/dhcpcd_10.1.0.bb | 1 +
> > ...llow-the-__NR_rt_sigprocmask-syscall.patch | 30
> > +++++++++++++++++++
> > 2 files changed, 31 insertions(+)
> > create mode 100644
> > meta/recipes-connectivity/dhcpcd/files/0001-linux-Allow-the-__NR_rt_si
> > gprocmask-syscall.patch
> >
> > diff --git a/meta/recipes-connectivity/dhcpcd/dhcpcd_10.1.0.bb
> > b/meta/recipes-connectivity/dhcpcd/dhcpcd_10.1.0.bb
> > index 3f806bb18783..99b72852bf34 100644
> > --- a/meta/recipes-connectivity/dhcpcd/dhcpcd_10.1.0.bb
> > +++ b/meta/recipes-connectivity/dhcpcd/dhcpcd_10.1.0.bb
> > @@ -15,6 +15,7 @@ SRC_URI =
> "git://github.com/NetworkConfiguration/dhcpcd;protocol=https;branch=ma
> > file://dhcpcd.service \
> > file://dhcpcd@.service \
> >
> > file://0001-dhcpcd.8-Fix-conflict-error-when-enable-multilib.patch \
> > +
> > + file://0001-linux-Allow-the-__NR_rt_sigprocmask-syscall.patch \
> > "
> >
> > SRCREV = "57c3506a5622e199cf0e3fc1ef26a71cdedc9521"
> > diff --git
> > a/meta/recipes-connectivity/dhcpcd/files/0001-linux-Allow-the-__NR_rt_
> > sigprocmask-syscall.patch
> > b/meta/recipes-connectivity/dhcpcd/files/0001-linux-Allow-the-__NR_rt_
> > sigprocmask-syscall.patch
> > new file mode 100644
> > index 000000000000..7058330165f3
> > --- /dev/null
> > +++ b/meta/recipes-connectivity/dhcpcd/files/0001-linux-Allow-the-__NR
> > +++ _rt_sigprocmask-syscall.patch
> > @@ -0,0 +1,30 @@
> > +From e9e40400003db2e4f12dba85acabbaf2212a520f Mon Sep 17
> 00:00:00
> > +2001
> > +From: Scott Shambarger <devel@shambarger.net>
> > +Date: Sat, 7 Dec 2024 16:37:28 +0000
> > +Subject: [PATCH] linux: Allow the __NR_rt_sigprocmask syscall
> > +
> > +Fixes recent glibc changes to getrandom() used by arc4random().
> > +Fixes #421.
> > +
> > +Upstream-Status: Backport
> > +See details in
> > +https://github.com/NetworkConfiguration/dhcpcd/issues/421
>
> This doesn't follow the established standard. I doubt that it will not trigger QA
> error.
Validated the patch using " patchtest --patch <patch_name>"
>
> --
> With best wishes
> Dmitry
Regards,
Balaji.
next prev parent reply other threads:[~2025-03-05 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 6:41 [PATCH] dhcpcd: fix for unexpected syscall 135 for 10.1.0 version Balaji Pothunoori
2025-03-05 8:46 ` Dmitry Baryshkov
2025-03-05 12:08 ` Balaji Pothunoori (QUIC) [this message]
2025-03-05 22:14 ` Dmitry Baryshkov
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=88cc44853dc94eb3b5b7a0c9abfa4ff3@quicinc.com \
--to=quic_bpothuno@quicinc.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=openembedded-core@lists.openembedded.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.