Re: [linux-yocto][linux-yocto v5.4/standard/xlnx-soc][PATCH 1/1] sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

Hi Michal, On 2020/3/18 下午12:40, quanyang.wang wrote: Hi Michal, On 2020/3/17 下午5:24, Michal Simek wrote: Hi, I have tested the latest Xilinx kernel based on v5.4 at github.com/Xilinx/linux-xlnx and I built it by toolchain you pointed me to and I can't see any issue. I find that the

Re: [linux-yocto][linux-yocto v5.4/standard/xlnx-soc][PATCH 1/1] sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

Hi Michal, On 2020/3/17 下午5:24, Michal Simek wrote: Hi, I have tested the latest Xilinx kernel based on v5.4 at github.com/Xilinx/linux-xlnx and I built it by toolchain you pointed me to and I can't see any issue. I find that the reason why this issue only exists in SDK v4.19 but not in SDK

[yocto] [meta-security][PATCH 3/7] chkrootkit: add rootkit recipe

Signed-off-by: Armin Kuster --- recipes-scanners/rootkits/chkrootkit_0.53.bb | 48 1 file changed, 48 insertions(+) create mode 100644 recipes-scanners/rootkits/chkrootkit_0.53.bb diff --git a/recipes-scanners/rootkits/chkrootkit_0.53.bb

[yocto] [meta-security][PATCH 4/7] clamav: move to recipes-scanners

Signed-off-by: Armin Kuster --- {recipes-security => recipes-scanners}/clamav/clamav_0.101.5.bb | 0 .../clamav/files/clamav-freshclam.service | 0 .../clamav/files/clamav-milter.conf.sample| 0 .../clamav/files/clamav.service

[yocto] [meta-security][PATCH 1/7] lynis: add missing rdepends

add findutils Signed-off-by: Armin Kuster --- meta-security-compliance/recipes-auditors/lynis/lynis_2.7.5.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-security-compliance/recipes-auditors/lynis/lynis_2.7.5.bb

[yocto] [meta-security][PATCH 6/7] checksecurity: move to recipes-scanners

Signed-off-by: Armin Kuster --- .../checksecurity/checksecurity_2.0.15.bb | 0 .../files/check-setuid-use-more-portable-find-args.patch | 0 .../checksecurity/files/setuid-log-folder.patch | 0 3 files changed, 0 insertions(+), 0 deletions(-)

[yocto] [meta-security][PATCH 2/7] fail2ban: change hardcoded sysklogd to VIRTUAL-RUNTIME_base-utils-syslog

Signed-off-by: Armin Kuster --- recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb b/recipes-security/fail2ban/python3-fail2ban_0.10.4.0.bb index 8673c10..e737f50

[yocto] [meta-security][PATCH 5/7] checksec: move to recipe-scanners

Signed-off-by: Armin Kuster --- {recipes-security => recipes-scanners}/checksec/checksec_2.1.0.bb | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename {recipes-security => recipes-scanners}/checksec/checksec_2.1.0.bb (100%) diff --git a/recipes-security/checksec/checksec_2.1.0.bb

[PATCH 2/2] [linux-yocto] [linux-yocto v4.19/standard/base] ath9k_htc: CVE-2019-19073

Security Advisory References https://github.com/torvalds/linux/commit/853acf7caf10b828102d92d05b5c101666a6142b ath9k_htc: release allocated buffer if timed out In htc_config_pipe_credits, htc_setup_complete, and htc_connect_service if time out happens, the allocated buffer needs to be released.

[PATCH 1/2] [linux-yocto] [linux-yocto v4.19/standard/base] tracing: CVE-2019-19072

Security Advisory References https://github.com/torvalds/linux/commit/96c5c6e6a5b6db592acae039fed54b5c8844cd35 tracing: Have error path in predicate_parse() free its allocated memory In predicate_parse, there is an error path that is not going to out_free instead it returns directly which leads

Re: [yocto] How to PROVIDE boost-python

Also as Quentin suggested it might be needed to remove the "-mt" suffix, but I see it in the do_install() method of the "boost" recipe for revision 1.64. Kind regards, Laurent. On Tue, Mar 17, 2020 at 11:17 PM Laurent Gauthier via Lists.Yoctoproject.Org wrote: > > Hi again Emily, > > You have

Re: [yocto] How to PROVIDE boost-python

Hi again Emily, You have put your finger on the core issue there. The name of the boost python library which is linked in your "opc-ua-server-gfex" recipe is "boost_python-mt" where it seems that it should be "boost_python3-mt". I guess you should have a look at the CMakeLists.txt of the

Re: [yocto] How to PROVIDE boost-python

Hi Emily, On Tue, Mar 17, 2020 at 12:06:48PM -0500, Emily wrote: > Hi Quentin - > > That's what I tried originally! DEPENDS on boost and not boost-python gives I should have read more carefully, sorry. > me the following error when trying to build my original recipe: > >

Re: [yocto] [poky] Thud community support

On 3/13/20 11:03 AM, akuster via Lists.Yoctoproject.Org wrote: > The Poky thud branch is now under 'Community support' and is seeking a > maintainer to continue supporting the following repos for the thud release: > > bitbake, core, meta-yocto and yocto-docs. > > > There will be no more point

[yocto] [meta-raspberrypi] How Build Image Supports X11 and 7" Touch Display

I'm trying to build am image that supports X11 and will use the official 7" touch screen from the Raspberry Pi organization for the raspberrypi2. To test I've built both core-image-x11 and core-image sato with no changes to either recipe and am getting the same behavior from both. What

Re: [yocto] Excluding kernel configuration fragment

On Tue, Mar 17, 2020 at 2:41 PM Fred Baksik wrote: > > What is the best way of excluding a kernel configuration fragment? > > I am trying to disable sound support in the kernel. I can create a fragment > for this but then this conflicts with the other existing fragments. > For example when

[yocto] Excluding kernel configuration fragment

What is the best way of excluding a kernel configuration fragment? I am trying to disable sound support in the kernel.  I can create a fragment for this but then this conflicts with the other existing fragments. For example when using meta-intel and removing sound support then you will receive

Re: [yocto] How to PROVIDE boost-python

Hi Laurent - Thanks for the suggestion. It looks like there are a few packages that provide libboost_python3: find tmp/work/*/*/*/packages-split -name libboost_python\* tmp/work/aarch64-poky-linux/boost/1.64.0-r0/packages-split/boost-dev/usr/lib/libboost_python3.so

Re: [yocto] How to PROVIDE boost-python

Hi Emily, To find the solution to your issue in a rational and deterministic way we need to start from the error message. What I understand is that while build recipe "opc-ua-server-gfex" you get an error message that says in short "ld: cannot find -lboost_python-mt". Therefore you need to

Re: [yocto] How to PROVIDE boost-python

Hi Quentin - That's what I tried originally! DEPENDS on boost and not boost-python gives me the following error when trying to build my original recipe: /local/d6/easmith5/rocko_bitbake/poky/build/tmp/work/aarch64 -poky-linux/opc-ua-server-gfex/1.0+gitAUTOINC+921c563309

[V2][linux-yocto][linux-yocto v5.4/standard/xlnx-soc][PATCH 0/1] sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

From: Quanyang Wang V1 ---> V2: 1. modify commit description since the gcc with -O2 is not the root cause. 2. fix some format defects. Quanyang Wang (1): sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

Re: [linux-yocto][linux-yocto v5.4/standard/xlnx-soc][PATCH 1/1] sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

Hi, I am doing some checking but it will be available soon. M On 17. 03. 20 16:38, wqyoung wrote: > Hi Michal, > > Is the xilinx kernel 5.4 finished? I check the git tree > https://github.com/Xilinx/linux-xlnx.git and  there is no > xlnx_rebase_v5.4 branch. > > Thanks, > > Quanyang > > On

Re: [yocto] How to PROVIDE boost-python

Hi Emily, On Tue, Mar 17, 2020 at 10:44:10AM -0500, Emily wrote: > Hi all - > > I'm trying to build an opca recipe ( > https://github.com/kratsg/meta-l1calo/blob/add/opcServer/recipes-core/opc-ua/opc-ua-server-gfex_git.bb) > and it's giving me a build error like: > > | >

[yocto] How to PROVIDE boost-python

Hi all - I'm trying to build an opca recipe ( https://github.com/kratsg/meta-l1calo/blob/add/opcServer/recipes-core/opc-ua/opc-ua-server-gfex_git.bb) and it's giving me a build error like: |

Re: [linux-yocto][linux-yocto v5.4/standard/xlnx-soc][PATCH 1/1] sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

Hi Michal, Is the xilinx kernel 5.4 finished? I check the git tree https://github.com/Xilinx/linux-xlnx.git and  there is no xlnx_rebase_v5.4 branch. Thanks, Quanyang On 2020/3/17 下午11:25, Michal Simek wrote: Hi, tbh I think that it will be good to start to think how to switch 5.4 to be

Re: [linux-yocto][linux-yocto v5.4/standard/xlnx-soc][PATCH 1/1] sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

Hi, tbh I think that it will be good to start to think how to switch 5.4 to be based on xilinx rebase kernel and this code will be changed anyway. Thanks, Michal On 17. 03. 20 15:56, Quanyang Wang wrote: > Hi Michal, > > It's strange that this issue only exists with SDK 4.19 patches for >

[yocto] Yocto Project Status WW11'20

Current Dev Position: YP 3.1 M4 - Stabilization Next Deadline: YP 3.1 M4 build date 3/30/2020 Next Team Meetings: * Bug Triage meeting Thursday Mar. 19th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Apr. 7th at

Re: [linux-yocto][linux-yocto v5.4/standard/xlnx-soc][PATCH 1/1] sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

Hi Michal, It's strange that this issue only exists with SDK 4.19 patches for sdhci-of-arasan.c and gcc 9.2. Once the code is changed, this issue disappears. It means that the over optimization of gcc 9.2 is not the root cause. Since this issue breaks down the mmc controller in linux-yocto 5.4

Re: [linux-yocto] [PATCH] linux-yocto v4.19/standard/base] media: CVE-2019-19054

merged. Bruce On Tue, Mar 17, 2020 at 3:01 AM Wang Mingyu wrote: > > Security Advisory > > Reference to upstream patch: > https://github.com/torvalds/linux/commit/a7b2df76b42bdd026e3106cf2ba97db41345a177 > > media: rc: prevent memory leak in cx23888_ir_probe > > In cx23888_ir_probe if

Re: [linux-yocto] [PATCH] linux-yocto v4.19/standard/base] gpu: CVE-2019-19067

merged Bruce On Tue, Mar 17, 2020 at 3:01 AM Wang Mingyu wrote: > > Security Advisory > > Backport from v5.4 > Reference to upstream patch: > https://github.com/torvalds/linux/commit/57be09c6e8747bf48704136d9e3f92bfb93f5725 > > drm/amdgpu: fix multiple memory leaks in acp_hw_init > > In

Re: [linux-yocto]: [yocto-kernel-cache master]: bcm-2xxx-rpi: enable CONFIG_CLK_RASPBERRYPI for bcm-2xxx-rpi BSP in kernel-cache

On Tue, Mar 17, 2020 at 3:12 AM wrote: > > From: Limeng > > Hi Bruce, > > I am working on updating kernel patches for BSP bcm-2xxx-rpi platform, and > found out > there is a new clock drvier clk-raspberrypi.c that is created in latest > kernel v5.6. > So, enable kernel config

Re: [linux-yocto][yocto-kernel-cache yocto-5.4 master][PATCH] bsp/intel-x86: remove invalid config item CRYPTO_AES_X86_64

On Tue, Mar 17, 2020 at 4:06 AM wrote: > > From: Yanfei Xu > > Item CONFIG_CRYPTO_AES_X86_64 has been dropped from v5.4 kernel, > therefore, we drop it too. > My audit should have caught this, I've enhanced the scripts to pick it up in the future. > Reference: >

Re: [linux-yocto] [kernel-cache][PATCH 2/3] features/intel-pinctrl: remove CONFIG_GPIO_LYNXPOINT

On Tue, Mar 17, 2020 at 4:26 AM Xu, Yanfei wrote: > > Hi Bruce, > > I find PINCTRL_LYNXPOINT is actually removed from v5.6 kernel. And v5.4 kernel > is still using GPIO_LYNXPOINT. > Indeed. I confirmed this myself. It was showing in my invalid Kconfig audit log, so I've enhanced the reporting

Re: [linux-yocto][linux-yocto v5.4/standard/xlnx-soc][PATCH 1/1] sdhci: arasan: use an array of integers for *_itap/otap_delays instead of macro *_ITAP/OTAP_DELAYS

Hi, I have tested the latest Xilinx kernel based on v5.4 at github.com/Xilinx/linux-xlnx and I built it by toolchain you pointed me to and I can't see any issue. Driver has changed a little bit based on mainline discussion but handling these values is the same. $ dmesg | grep gcc [0.00]

Re: [linux-yocto] [kernel-cache][PATCH 2/3] features/intel-pinctrl: remove CONFIG_GPIO_LYNXPOINT

Hi Bruce, I find PINCTRL_LYNXPOINT is actually removed from v5.6 kernel. And v5.4 kernel is still using GPIO_LYNXPOINT. Would you please revert it on v5.4 kernel-cache? Reference: https://github.com/torvalds/linux/commit/eb83479e18999e34b3b800f54aa31137f7f41c33 Thanks, Yanfei On 1/21/20

[linux-yocto][yocto-kernel-cache yocto-5.4 master][PATCH] bsp/intel-x86: remove invalid config item CRYPTO_AES_X86_64

From: Yanfei Xu Item CONFIG_CRYPTO_AES_X86_64 has been dropped from v5.4 kernel, therefore, we drop it too. Reference: https://github.com/torvalds/linux/commit/1d2c3279311e4f03fcf164e1366f2fda9f4bfccf Signed-off-by: Yanfei Xu --- bsp/intel-x86/intel-x86-64.cfg | 1 - 1 file changed, 1

[linux-yocto] [PATCH] bcm-2xxx-rpi: enable CONFIG_CLK_RASPBERRYPI for bcm-2xxx-rpi BSP in kernel-cache

From: Limeng In latest kernel v5.6, new clock drvier clk-raspberrypi.c is created. So, enable kernel config CONFIG_CLK_RASPBERRYPI in kernel-cache Signed-off-by: Meng Li --- bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg | 3 +++ 1 file changed, 3 insertions(+) diff --git

[linux-yocto]: [yocto-kernel-cache master]: bcm-2xxx-rpi: enable CONFIG_CLK_RASPBERRYPI for bcm-2xxx-rpi BSP in kernel-cache

From: Limeng Hi Bruce, I am working on updating kernel patches for BSP bcm-2xxx-rpi platform, and found out there is a new clock drvier clk-raspberrypi.c that is created in latest kernel v5.6. So, enable kernel config CONFIG_CLK_RASPBERRYPI in kernel-cache So, could you please merge this

[linux-yocto] [PATCH] linux-yocto v4.19/standard/base] gpu: CVE-2019-19067

Security Advisory Backport from v5.4 Reference to upstream patch: https://github.com/torvalds/linux/commit/57be09c6e8747bf48704136d9e3f92bfb93f5725 drm/amdgpu: fix multiple memory leaks in acp_hw_init In acp_hw_init there are some allocations that needs to be released in case of failure: 1-

[linux-yocto] [PATCH] linux-yocto v4.19/standard/base] media: CVE-2019-19054

Security Advisory Reference to upstream patch: https://github.com/torvalds/linux/commit/a7b2df76b42bdd026e3106cf2ba97db41345a177 media: rc: prevent memory leak in cx23888_ir_probe In cx23888_ir_probe if kfifo_alloc fails the allocated memory for state should be released. Signed-off-by: Navid