date:20230116

Re: [yocto] gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'

2023-01-16 Thread jovanbosic95

Is it something about compiler?

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59004): https://lists.yoctoproject.org/g/yocto/message/59004
Mute This Topic: https://lists.yoctoproject.org/mt/96325807/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'

2023-01-16 Thread jovanbosic95

Can someone help me with this problem? I want to install chromium on dunfell, 
and I am receiving this problem.

jovanbosic@administrator-ThinkPad-L470:~/Yocto/build$ bitbake 
core-image-full-cmdline
WARNING: Host distribution "ubuntu-22.04" has not been validated with this 
version of the build system; you may possibly experience unexpected failures. 
It is recommended that you use a tested distribution.
Loading cache: 100% || Time: 0:00:00
Loaded 3726 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "qemux86-64"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1.22"
TUNE_FEATURES        = "m64 core2"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp
meta-selftest
meta-skeleton        = "dunfell:6b8a307b7843af23d189d7ffcecf32c05afac850"
meta-chromium        = "master:068b693ffcf0273ec23d0ab1eeb8f4b97eb143a1"
meta-clang           = 
"dunfell-clang12:8a6558fe1cedb3eb81769a3cc2512364f1a6"
meta-filesystems
meta-gnome
meta-initramfs
meta-multimedia
meta-networking
meta-oe
meta-perl
meta-python
meta-webserver
meta-xfce            = "dunfell:7952135f650b4a754e2255f5aa03973a32344123"

Initialising tasks: 100% |###| Time: 0:00:05
Sstate summary: Wanted 21 Found 0 Missed 21 Current 2963 (0% match, 99% 
complete)
NOTE: Executing Tasks
ERROR: gn-native-106.0.5249.119-r0 do_compile: Execution of 
'/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/temp/run.do_compile.4042233'
 failed with exit code 1
ERROR: Logfile of failure stored in: 
/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/temp/log.do_compile.4042233
Log data follows:
| DEBUG: Executing shell function do_compile
| ninja: Entering directory 
`/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/chromium-106.0.5249.119/out/Release/gn_build'
| [1/195] CXX src/base/files/file_path_constants.o
| FAILED: src/base/files/file_path_constants.o
| clang++ -target x86_64-linux  -MMD -MF src/base/files/file_path_constants.o.d 
-I../../../tools/gn/src -I. 
-isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include
 -O2 -pipe 
-isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include
 -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 
-fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions 
-fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi 
-Wundef -std=c++17 -c ../../../tools/gn/src/base/files/file_path_constants.cc 
-o src/base/files/file_path_constants.o
| ../../../tools/gn/src/base/files/file_path_constants.cc:7:10: fatal error: 
'iterator' file not found
| #include 
|          ^~
| 1 error generated.
| [2/195] CXX src/base/files/file_path.o
| FAILED: src/base/files/file_path.o
| clang++ -target x86_64-linux  -MMD -MF src/base/files/file_path.o.d 
-I../../../tools/gn/src -I. 
-isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include
 -O2 -pipe 
-isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include
 -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 
-fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions 
-fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi 
-Wundef -std=c++17 -c ../../../tools/gn/src/base/files/file_path.cc -o 
src/base/files/file_path.o
| In file included from ../../../tools/gn/src/base/files/file_path.cc:5:
| ../../../tools/gn/src/base/files/file_path.h:107:10: fatal error: 'iosfwd' 
file not found
| #include 
|          ^~~~
| 1 error generated.
| [3/195] CXX src/base/files/file.o
| FAILED: src/base/files/file.o
| clang++ -target x86_64-linux  -MMD -MF src/base/files/file.o.d 
-I../../../tools/gn/src -I. 
-isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include
 -O2 -pipe 
-isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include
 -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 
-fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions 
-fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi 
-Wundef -std=c++17 -c

[yocto] M+ & H bugs with Milestone Movements WW02

2023-01-16 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW02 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  14960

valgrind ptest fails 12 tests for arm64 targets

randy.macl...@windriver.com

randy.macl...@windriver.com

4.2 M2

4.2 M3


 

  14995

do_populate_sdk: target-sdk-provides-dummy fails to provide perl for postgresql

randy.macl...@windriver.com

tim.orl...@konsulko.com

4.2 M2

4.2 M3

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59002): https://lists.yoctoproject.org/g/yocto/message/59002
Mute This Topic: https://lists.yoctoproject.org/mt/96323653/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW02!

2023-01-16 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


alexandre.bell...@bootlin.com

3


ross.bur...@arm.com

1


pa...@zhukoff.net

1


akuster...@gmail.com

1


richard.pur...@linuxfoundation.org

1


Grand Total

7

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59001): https://lists.yoctoproject.org/g/yocto/message/59001
Mute This Topic: https://lists.yoctoproject.org/mt/96323639/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 4.2

2023-01-16 Thread Stephen Jolley

All,

Below is the list as of top 34 bug owners as of the end of WW02 of who have
open medium or higher bugs and enhancements against YP 4.2.   There are 71
possible work days left until the final release candidates for YP 4.2 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

34


ross.bur...@arm.com

32


randy.macl...@windriver.com

26


bruce.ashfi...@gmail.com

25


richard.pur...@linuxfoundation.org

25


david.re...@windriver.com

23


jpewhac...@gmail.com

10


sakib.sa...@windriver.com

8


saul.w...@windriver.com

5


tim.orl...@konsulko.com

5


pi...@toganlabs.com

4


pa...@zhukoff.net

4


thomas.per...@bootlin.com

2


rybczyn...@gmail.com

2


bluelightn...@bluelightning.org

2


s...@bigsur.com

2


zheng@windriver.com

2


jon.ma...@arm.com

2


naveen.go...@windriver.com

2


alexis.loth...@bootlin.com

2


sundeep.kokko...@gmail.com

2


anton.anto...@arm.com

1


yoann.con...@smile.fr

1


yashinde...@gmail.com

1


tvgamb...@gmail.com

1


sundeep.kokko...@windriver.com

1


martin.ja...@gmail.com

1


aeh...@gmail.com

1


thr...@amazon.de

1


mathew.pro...@gmail.com

1


mhalst...@linuxfoundation.org

1


alex.kana...@gmail.com

1


hongxu@windriver.com

1


alexandre.bell...@bootlin.com

1


Grand Total

232

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59000): https://lists.yoctoproject.org/g/yocto/message/59000
Mute This Topic: https://lists.yoctoproject.org/mt/96323569/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2023-01-16 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 417
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "4.2", "4.3", "4.99" and "Future", the more pressing/urgent
issues being in "4.2" and then "4.3".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58999): https://lists.yoctoproject.org/g/yocto/message/58999
Mute This Topic: https://lists.yoctoproject.org/mt/96323544/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.22.rc1)

2023-01-16 Thread Jing Hui Tham

Hi all,
 
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.22.rc1. 
We are planning to execute following tests for this cycle:
 
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
 
Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. NUC 7
3. ADL
4. TGL NUC 11
5. Edgerouter
6. Beaglebone
 
ETA for completion this Thursday, 19/1/2023.
 
Best regards,
Jing Hui


> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Pokybuild User
> Sent: Saturday, 14 January, 2023 10:11 AM
> To: yocto@lists.yoctoproject.org
> Cc: qa-build-notificat...@lists.yoctoproject.org
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-3.1.22.rc1)
> 
> 
> A build flagged for QA (yocto-3.1.22.rc1) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.1.22.rc1
> 
> 
> Build hash information:
> 
> bitbake: e3db9c2e9eded3c5cb6040714a6054b44f6b3880
> meta-agl: ae982d798a979ee5690bee00ca90a2855bab4802
> meta-arm: d13be36099aff7ea2975a1a197564e2e801707a3
> meta-aws: c013258cecbf99528291e55005e1db360d7eb40b
> meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
> meta-intel: 6c202291925bb179d2d08b5bde80192f9b032b88
> meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
> meta-openembedded: 7952135f650b4a754e2255f5aa03973a32344123
> meta-virtualization: beea119eb529b4a11f266004aee8b548427aea39
> oecore: db81e3c7e7f1d4d9eba52ac35ac97627d0240b63
> poky: 6b8a307b7843af23d189d7ffcecf32c05afac850
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58998): https://lists.yoctoproject.org/g/yocto/message/58998
Mute This Topic: https://lists.yoctoproject.org/mt/96322177/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore

2023-01-16 Thread Martin Jansa

Hi Armin,

can you please merge this to master branch? It's in master-next for a
while, but not in master and master-next is missing some changes from
master as well, openscap upgrade and kas changes look different in master
and master-next (which has 2 more chunks):
https://git.yoctoproject.org/meta-security/commit/?id=da93339112d0a53f0008a72dcacdb55dc3bf95a8
https://git.yoctoproject.org/meta-security/commit/?h=master-next=04a0e35a79d33aadbec79272072dc105830007b7

Cheers,

On Tue, Jan 3, 2023 at 5:36 PM Martin Jansa via lists.yoctoproject.org
 wrote:

> * oe-core switched to mickedore in:
>
> https://git.openembedded.org/openembedded-core/commit/?id=57239d66b933c4313cf331d35d13ec2d0661c38f
>
> Signed-off-by: Martin Jansa 
> ---
>  conf/layer.conf  | 2 +-
>  meta-hardening/conf/layer.conf   | 2 +-
>  meta-integrity/conf/layer.conf   | 2 +-
>  meta-parsec/conf/layer.conf  | 2 +-
>  meta-security-compliance/conf/layer.conf | 2 +-
>  meta-security-isafw/conf/layer.conf  | 2 +-
>  meta-tpm/conf/layer.conf | 2 +-
>  7 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/conf/layer.conf b/conf/layer.conf
> index 470c7f6..b5a74f1 100644
> --- a/conf/layer.conf
> +++ b/conf/layer.conf
> @@ -9,7 +9,7 @@ BBFILE_COLLECTIONS += "security"
>  BBFILE_PATTERN_security = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_security = "8"
>
> -LAYERSERIES_COMPAT_security = "kirkstone langdale"
> +LAYERSERIES_COMPAT_security = "mickledore"
>
>  LAYERDEPENDS_security = "core openembedded-layer"
>
> diff --git a/meta-hardening/conf/layer.conf
> b/meta-hardening/conf/layer.conf
> index 5983161..add3cbc 100644
> --- a/meta-hardening/conf/layer.conf
> +++ b/meta-hardening/conf/layer.conf
> @@ -8,6 +8,6 @@ BBFILE_COLLECTIONS += "harden-layer"
>  BBFILE_PATTERN_harden-layer = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_harden-layer = "10"
>
> -LAYERSERIES_COMPAT_harden-layer = "kirkstone langdale"
> +LAYERSERIES_COMPAT_harden-layer = "mickledore"
>
>  LAYERDEPENDS_harden-layer = "core openembedded-layer"
> diff --git a/meta-integrity/conf/layer.conf
> b/meta-integrity/conf/layer.conf
> index 1fcf33c..b273b5b 100644
> --- a/meta-integrity/conf/layer.conf
> +++ b/meta-integrity/conf/layer.conf
> @@ -20,7 +20,7 @@ INTEGRITY_BASE := '${LAYERDIR}'
>  # interactive shell is enough.
>  OE_TERMINAL_EXPORTS += "INTEGRITY_BASE"
>
> -LAYERSERIES_COMPAT_integrity = "kirkstone langdale"
> +LAYERSERIES_COMPAT_integrity = "mickledore"
>  # ima-evm-utils depends on keyutils from meta-oe
>  LAYERDEPENDS_integrity = "core openembedded-layer"
>
> diff --git a/meta-parsec/conf/layer.conf b/meta-parsec/conf/layer.conf
> index a748d77..0a71694 100644
> --- a/meta-parsec/conf/layer.conf
> +++ b/meta-parsec/conf/layer.conf
> @@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "parsec-layer"
>  BBFILE_PATTERN_parsec-layer = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_parsec-layer = "5"
>
> -LAYERSERIES_COMPAT_parsec-layer = "kirkstone langdale"
> +LAYERSERIES_COMPAT_parsec-layer = "mickledore"
>
>  LAYERDEPENDS_parsec-layer = "core clang-layer"
>  BBLAYERS_LAYERINDEX_NAME_parsec-layer = "meta-parsec"
> diff --git a/meta-security-compliance/conf/layer.conf
> b/meta-security-compliance/conf/layer.conf
> index ec57541..f07532c 100644
> --- a/meta-security-compliance/conf/layer.conf
> +++ b/meta-security-compliance/conf/layer.conf
> @@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "scanners-layer"
>  BBFILE_PATTERN_scanners-layer = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_scanners-layer = "10"
>
> -LAYERSERIES_COMPAT_scanners-layer = "kirkstone langdale"
> +LAYERSERIES_COMPAT_scanners-layer = "mickledore"
>
>  LAYERDEPENDS_scanners-layer = "core openembedded-layer meta-python"
>
> diff --git a/meta-security-isafw/conf/layer.conf
> b/meta-security-isafw/conf/layer.conf
> index 724742d..550cced 100644
> --- a/meta-security-isafw/conf/layer.conf
> +++ b/meta-security-isafw/conf/layer.conf
> @@ -14,4 +14,4 @@ LAYERVERSION_security-isafw = "1"
>
>  LAYERDEPENDS_security-isafw = "core"
>
> -LAYERSERIES_COMPAT_security-isafw = "kirkstone langdale"
> +LAYERSERIES_COMPAT_security-isafw = "mickledore"
> diff --git a/meta-tpm/conf/layer.conf b/meta-tpm/conf/layer.conf
> index 1fd2e4c..81690ca 100644
> --- a/meta-tpm/conf/layer.conf
> +++ b/meta-tpm/conf/layer.conf
> @@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "tpm-layer"
>  BBFILE_PATTERN_tpm-layer = "^${LAYERDIR}/"
>  BBFILE_PRIORITY_tpm-layer = "10"
>
> -LAYERSERIES_COMPAT_tpm-layer = "kirkstone langdale"
> +LAYERSERIES_COMPAT_tpm-layer = "mickledore"
>
>  LAYERDEPENDS_tpm-layer = " \
>  core \
> --
> 2.39.0
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58997): https://lists.yoctoproject.org/g/yocto/message/58997
Mute This Topic: https://lists.yoctoproject.org/mt/96031444/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH] LF-3332-1: arm64: imx8: vpu: fix build errors due to API change

2023-01-16 Thread Li Wang

From: Zhou Peng 

commit 67ee385c11e1c6b3a8376b40682ba364c130215c from
https://source.codeaurora.org/external/imx/linux-imx

hantro g1/g2/h1/vc8000:
replace get_fs()/set_fs() with force_uaccess_xxx()

Signed-off-by: Zhou Peng 
Signed-off-by: Xiaolei Wang 
Signed-off-by: Li Wang 
---
 drivers/mxc/hantro/hantrodec.c| 5 ++---
 drivers/mxc/hantro_845/hantrodec_845s.c   | 5 ++---
 drivers/mxc/hantro_845_h1/hx280enc.c  | 5 ++---
 drivers/mxc/hantro_vc8000e/hx280enc_vc8000e.c | 5 ++---
 4 files changed, 8 insertions(+), 12 deletions(-)

diff --git a/drivers/mxc/hantro/hantrodec.c b/drivers/mxc/hantro/hantrodec.c
index e5bff4abec0c..065bdb576da6 100755
--- a/drivers/mxc/hantro/hantrodec.c
+++ b/drivers/mxc/hantro/hantrodec.c
@@ -1291,12 +1291,11 @@ static int put_hantro_core_desc32(struct core_desc *kp, 
struct core_desc_32 __us
 static long hantrodec_ioctl32(struct file *filp, unsigned int cmd, unsigned 
long arg)
 {
 #define HANTRO_IOCTL32(err, filp, cmd, arg) { \
-   mm_segment_t old_fs = get_fs(); \
-   set_fs(KERNEL_DS); \
+   mm_segment_t old_fs = force_uaccess_begin(); \
err = hantrodec_ioctl(filp, cmd, arg); \
if (err) \
return err; \
-   set_fs(old_fs); \
+   force_uaccess_end(old_fs); \
}
 
union {
diff --git a/drivers/mxc/hantro_845/hantrodec_845s.c 
b/drivers/mxc/hantro_845/hantrodec_845s.c
index b398a3f57715..20443e454306 100755
--- a/drivers/mxc/hantro_845/hantrodec_845s.c
+++ b/drivers/mxc/hantro_845/hantrodec_845s.c
@@ -1421,12 +1421,11 @@ static int put_hantro_core_desc32(struct core_desc *kp, 
struct core_desc_32 __us
 static long hantrodec_ioctl32(struct file *filp, unsigned int cmd, unsigned 
long arg)
 {
 #define HANTRO_IOCTL32(err, filp, cmd, arg) { \
-   mm_segment_t old_fs = get_fs(); \
-   set_fs(KERNEL_DS); \
+   mm_segment_t old_fs = force_uaccess_begin(); \
err = hantrodec_ioctl(filp, cmd, arg); \
if (err) \
return err; \
-   set_fs(old_fs); \
+   force_uaccess_end(old_fs); \
}
 
union {
diff --git a/drivers/mxc/hantro_845_h1/hx280enc.c 
b/drivers/mxc/hantro_845_h1/hx280enc.c
index 3a403e8029e0..edf2ef2fc56d 100755
--- a/drivers/mxc/hantro_845_h1/hx280enc.c
+++ b/drivers/mxc/hantro_845_h1/hx280enc.c
@@ -483,12 +483,11 @@ static long hx280enc_ioctl32(struct file *filp, unsigned 
int cmd, unsigned long
 {
 long err = 0;
 #define HX280ENC_IOCTL32(err, filp, cmd, arg) { \
-   mm_segment_t old_fs = get_fs(); \
-   set_fs(KERNEL_DS); \
+   mm_segment_t old_fs = force_uaccess_begin(); \
err = hx280enc_ioctl(filp, cmd, arg); \
if (err) \
return err; \
-   set_fs(old_fs); \
+   force_uaccess_end(old_fs); \
 }
 
 union {
diff --git a/drivers/mxc/hantro_vc8000e/hx280enc_vc8000e.c 
b/drivers/mxc/hantro_vc8000e/hx280enc_vc8000e.c
index 3a5083ed6833..bc8300307859 100755
--- a/drivers/mxc/hantro_vc8000e/hx280enc_vc8000e.c
+++ b/drivers/mxc/hantro_vc8000e/hx280enc_vc8000e.c
@@ -632,12 +632,11 @@ static long hantroenc_ioctl32(struct file *filp, unsigned 
int cmd, unsigned long
long err = 0;
 
 #define HX280ENC_IOCTL32(err, filp, cmd, arg) { \
-   mm_segment_t old_fs = get_fs(); \
-   set_fs(KERNEL_DS); \
+   mm_segment_t old_fs = force_uaccess_begin(); \
err = hantroenc_ioctl(filp, cmd, arg); \
if (err) \
return err; \
-   set_fs(old_fs); \
+   force_uaccess_end(old_fs); \
 }
 
 union {
-- 
2.39.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12105): 
https://lists.yoctoproject.org/g/linux-yocto/message/12105
Mute This Topic: https://lists.yoctoproject.org/mt/96303261/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [autobuilder][PATCH 0/2] generate regression reports against proper releases

2023-01-16 Thread Alexis Lothoré via lists . yoctoproject . org


Hi Richard,

On 13/01/2023 19:01, Richard Purdie wrote:

On Fri, 2023-01-13 at 16:06 +0100, Alexis Lothoré via
lists.yoctoproject.org wrote:

- I also have some uncommitted python unit tests on "previous version
  computation", but current scripts directory does not allow proper 
unit tests
integration. If appropriate, I could submit some minor reworks to make 
it viable

for testing and submit those tests


I'm glad you mentioned this! Yes, I think it is important we add some
tests for this. We can rework these scripts as needed as the project is
their main user at this point.
Good, I will then add some minor rework to allow introducing unit tests 
alongside

the version computation in the next revision


- This new regression checking introduced the need to clone a wider 
testresults
  history, which is (very) slow on my machine, but I do not now how 
slow it is
on autobuilder. Could it be an issue for the delivery process ? Does 
it need to

be smarter on this point ?


I think it will be slow on the autobuilder and we're going to have to
do something different to make this work well. My clone still hasn't
finished and is at 5.75GB of data now (15 mins to get the last 4.5GB)
and still going.


OK. I observed a quite similar behaviour while pulling manually the 
whole repository,
but I thought it might be linked to network issue on my side. I will add 
a smarter way

based on your suggestion (git ls-remote)

- If appropriate, new patch could follow to allow regression reports 
generation
against multiple revisions : for example we could check for a 
milestone build

against previous milestone AND previous major release


I think that is the direction we need to go so yes please!


Noted. If it is OK for you, I will keep this last point for another set 
of patches, once this

initial work is approved and merged.

Regards,

--
Alexis Lothoré, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58996): https://lists.yoctoproject.org/g/yocto/message/58996
Mute This Topic: https://lists.yoctoproject.org/mt/96247368/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'

[yocto] gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'

[yocto] M+ & H bugs with Milestone Movements WW02

[yocto] Enhancements/Bugs closed WW02!

[yocto] Current high bug count owners for Yocto Project 4.2

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.22.rc1)

Re: [yocto] [meta-security][PATCH] layer.conf: update LAYERSERIES_COMPAT for mickledore

[linux-yocto][v5.10/standard/nxp-sdk-5.10/nxp-soc & v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH] LF-3332-1: arm64: imx8: vpu: fix build errors due to API change

Re: [yocto] [autobuilder][PATCH 0/2] generate regression reports against proper releases

10 matches

Site Navigation

Mail list logo

Footer information