|
Bugzilla – Full Text Bug Listing |
Created attachment 728060 [details]
0002-mvebu-Use-dev_pm_opp_set_sharing_cpus-to-mark-OPP-ta.patch
Created attachment 728061 [details]
0003-cpufreq-tegra124-No-need-of-setting-platform-data.patch
Created attachment 728062 [details]
0004-extcon-adc-jack-Remove-the-usage-of-extcon_set_state.patch
Created attachment 728063 [details]
0005-extcon-arizona-Remove-the-usage-of-extcon_update_sta.patch
Created attachment 728064 [details]
0006-input-misc-max77693-Use-pwm_get_args-where-appropria.patch
Created attachment 728065 [details]
0007-ACPI-bus-add-stub-acpi_evaluate_dsm-to-linux-acpi.h.patch
Created attachment 728066 [details]
0008-ACPI-bus-add-stub-acpi_dev_found-to-linux-acpi.h.patch
Created attachment 728067 [details]
0009-power-axp288_charger-Replace-deprecatd-API-of-extcon.patch
Created attachment 728068 [details]
0010-pwm-rcar-Make-use-of-pwm_is_enabled.patch
Created attachment 728069 [details]
0011-pwm-Use-pwm_get-set_xxx-helpers-where-appropriate.patch
Created attachment 728070 [details]
0012-dmaengine-core-Move-and-merge-the-code-paths-using-p.patch
Created attachment 728071 [details]
0013-dmaengine-core-Introduce-new-universal-API-to-reques.patch
Created attachment 728072 [details]
0014-dmaengine-Add-transfer-termination-synchronization-s.patch
Created attachment 728073 [details]
0015-dmaengine-enable-DMA_CTRL_REUSE.patch
Created attachment 728074 [details]
0016-dmaengine-core-expose-max-burst-capability-to-client.patch
Created attachment 728075 [details]
0017-spi-expose-master-transfer-size-limitation.patch
Created attachment 728076 [details]
0018-ARM-gic-v3-Work-around-definition-of-gic_write_bpr1.patch
Created attachment 728077 [details]
0019-drm-define-drm_compat_ioctl-NULL-on-CONFIG_COMPAT-n-.patch
Hm, this is worse than I thought. Basically it's too late to take too intrusive patches that change kABI heavily. That is, it's no big problem to take patches changing arch/arm/* in general, but not for the common code. Please try to reduce the changes as much as possible. If it's inevitably necessary, we can take some changes but with kABI workaround or similar hack might be required in addition. Thanks. 0001-ARM-EXYNOS-Remove-calls-to-of_genpd_get_from_provide.patch is armv7-specific
0002-mvebu-Use-dev_pm_opp_set_sharing_cpus-to-mark-OPP-ta.patch is armv7-specific
0003-cpufreq-tegra124-No-need-of-setting-platform-data.patch is armv7-specific (tegra124 is cortex-a15 based platform)
0004-extcon-adc-jack-Remove-the-usage-of-extcon_set_state.patch
0005-extcon-arizona-Remove-the-usage-of-extcon_update_sta.patch
are required to fix errors like this:
/home/matwey/lab/linux/drivers/extcon/extcon-adc-jack.c: In function 'adc_jack_handler':
/home/matwey/lab/linux/drivers/extcon/extcon-adc-jack.c:81:2: error: too few arguments to function 'extcon_set_state'
extcon_set_state(data->edev, state);
and that:
/home/matwey/lab/linux/drivers/extcon/extcon-arizona.c: In function 'arizona_jackdet':
/home/matwey/lab/linux/drivers/extcon/extcon-arizona.c:1152:9: error: implicit declaration of function 'extcon_update_state' [-Werror=implicit-function-declaration]
ret = extcon_update_state(info->edev, 0xffffffff, 0);
which come from API change introduced by patch rk3399-0010-extcon-Add-the-synchronization-extcon-APIs-to-suppor.patch which is already in SUSE kernel. And as soon as nobody had checked extcon compilation when rk3399-0010-extcon-Add-the-synchronization-extcon-APIs-to-suppor.patch was applied, they are also armv7-specific.
0006-input-misc-max77693-Use-pwm_get_args-where-appropria.patch
is required to fix errors like those:
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c: In function 'max77693_haptic_set_duty_cycle':
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c:73:30: error: 'struct pwm_device' has no member named 'period'
int delta = (haptic->pwm_dev->period + haptic->pwm_duty) / 2;
^~
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c:76:60: error: 'struct pwm_device' has no member named 'period'
error = pwm_config(haptic->pwm_dev, delta, haptic->pwm_dev->period);
^~
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c: In function 'max77693_haptic_play_effect':
/home/matwey/lab/linux/drivers/input/misc/max77693-haptic.c:248:41: error: 'struct pwm_device' has no member named 'period'
period_mag_multi = (u64)haptic->pwm_dev->period * haptic->magnitude;
which are due to API change introduced by rk3399-pwm-0008-pwm-Introduce-the-pwm_state-concept.patch (in upstream kernel 0006-input-misc-max77693-Use-pwm_get_args-where-appropria.patch is before than rk3399-pwm-0008-pwm-Introduce-the-pwm_state-concept.patch). Since nobody found that, I suppose this is also armv7-specific.
0007-ACPI-bus-add-stub-acpi_evaluate_dsm-to-linux-acpi.h.patch
0008-ACPI-bus-add-stub-acpi_dev_found-to-linux-acpi.h.patch
These are required to fix:
/home/matwey/lab/linux/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c: In function 'hns_dsaf_get_cfg':
/home/matwey/lab/linux/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c:64:7: error: implicit declaration of function 'acpi_dev_found' [-Werror=implicit-function-declaration]
if (acpi_dev_found(hns_dsaf_acpi_match[0].id))
So, actually it is SUSE kernel patch net-hns-dsaf-adds-support-of-acpi.patch which breaks hisilicon compilation for armv7l.
I think there could be three options 1) accepting ACPI-* patches 2) fixing net-hns-dsaf-adds-support-of-acpi.patch, net-hns-net-hns-enet-adds-support-of-acpi.patch, net-hns-Add-ACPI-support-to-check-SFP-present.patch and net-hns-implement-the-miscellaneous-operation-by-asl.patch in order no to use acpi_dev_found() and acpi_evaluate_dsm() functions at armv7l 3) disable NET_VENDOR_HISILICON_HNS in config and not to build this code.
What would you prefer?
To be continued...
(In reply to Matwey Kornilov from comment #20) > 0001-ARM-EXYNOS-Remove-calls-to-of_genpd_get_from_provide.patch is > 0002-mvebu-Use-dev_pm_opp_set_sharing_cpus-to-mark-OPP-ta.patch is > 0003-cpufreq-tegra124-No-need-of-setting-platform-data.patch is They are fine. > 0004-extcon-adc-jack-Remove-the-usage-of-extcon_set_state.patch > 0005-extcon-arizona-Remove-the-usage-of-extcon_update_sta.patch OK, these aren't used for x86, so it's no big problem about kABI change for now. > 0006-input-misc-max77693-Use-pwm_get_args-where-appropria.patch Ditto. > 0007-ACPI-bus-add-stub-acpi_evaluate_dsm-to-linux-acpi.h.patch > 0008-ACPI-bus-add-stub-acpi_dev_found-to-linux-acpi.h.patch > > These are required to fix: > > /home/matwey/lab/linux/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c: > In function 'hns_dsaf_get_cfg': > /home/matwey/lab/linux/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c:64: > 7: error: implicit declaration of function 'acpi_dev_found' > [-Werror=implicit-function-declaration] > if (acpi_dev_found(hns_dsaf_acpi_match[0].id)) > > So, actually it is SUSE kernel patch net-hns-dsaf-adds-support-of-acpi.patch > which breaks hisilicon compilation for armv7l. > I think there could be three options 1) accepting ACPI-* patches 2) fixing > net-hns-dsaf-adds-support-of-acpi.patch, > net-hns-net-hns-enet-adds-support-of-acpi.patch, > net-hns-Add-ACPI-support-to-check-SFP-present.patch and > net-hns-implement-the-miscellaneous-operation-by-asl.patch in order no to > use acpi_dev_found() and acpi_evaluate_dsm() functions at armv7l 3) disable > NET_VENDOR_HISILICON_HNS in config and not to build this code. > What would you prefer? I put Benjamin to Cc. But I guess these two are fine from the kABI POV, too, as they just add dummy static inline functions. So far, so good. I'll try to apply these ones. Let's check the rest. 0009-power-axp288_charger-Replace-deprecatd-API-of-extcon.patch
is needed to fix the following driver:
/home/matwey/lab/linux/drivers/power/axp288_charger.c: In function 'axp288_charger_extcon_evt_worker':
/home/matwey/lab/linux/drivers/power/axp288_charger.c:589:6: error: implicit declaration of function 'extcon_get_cable_state' [-Werror=implicit-function-declaration]
if (extcon_get_cable_state(edev, AXP288_EXTCON_SLOW_CHARGER) > 0) {
^~~~~~~~~~~~~~~~~~~~~~
extcon_get_cable_state() function is dropped by rk3399-0009-extcon-Rename-the-extcon_set-get_state-to-maintain-t.patch and I think it is also affects only armv7l arch. drivers/power/axp288_charger.c seems to not be used for other arhcs.
0010-pwm-rcar-Make-use-of-pwm_is_enabled.patch:
is needed to fix:
/home/matwey/lab/linux/drivers/pwm/pwm-rcar.c: In function 'rcar_pwm_config':
/home/matwey/lab/linux/drivers/pwm/pwm-rcar.c:160:16: error: 'PWMF_ENABLED' undeclared (first use in this function)
if (!test_bit(PWMF_ENABLED, &pwm->flags) && !duty_ns)
It is rk3399-pwm-0009-pwm-Move-the-enabled-disabled-info-into-pwm_state.patch who stole PWMF_ENABLED macro definition.
Aarch64 team could found it by itself since pwm-rcar is required for Renesas R8A7795-based 64-bit boards (but CONFIG_PWM_RCAR is not enabled in arch64 default config).
Since pwm-rcar is useless for armv7l I think there is also option to drop CONFIG_PWM_RCAR from armv7l config. What would you prefer?
0011-pwm-Use-pwm_get-set_xxx-helpers-where-appropriate.patch:
is needed to fix:
/home/matwey/lab/linux/drivers/pwm/pwm-sun4i.c: In function 'sun4i_pwm_probe':
/home/matwey/lab/linux/drivers/pwm/pwm-sun4i.c:357:21: error: 'struct pwm_device' has no member named 'polarity'
pwm->chip.pwms[i].polarity = PWM_POLARITY_INVERSED;
There again API change backported by rk3399-pwm-0008-pwm-Introduce-the-pwm_state-concept.patch again. (See 0006-input-misc-max77693-Use-pwm_get_args-where-appropria.patch which suffers the same.)
The patch affects only armv7l-related PWM drivers.
*-dmaengine-*.patch and 0017-spi-expose-master-transfer-size-limitation.patch:
These are required to fix multiple compilation errors introduced by rk3399-*-spi-rockchip-*.patch
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c: In function 'rockchip_spi_handle_err':
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c:327:4: error: implicit declaration of function 'dmaengine_terminate_async' [-Werror=implicit-function-declaration]
dmaengine_terminate_async(rs->dma_rx.ch);
^~~~~~~~~~~~~~~~~~~~~~~~~
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c: In function 'rockchip_spi_prepare_dma':
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c:457:19: error: 'struct dma_slave_caps' has no member named 'max_burst'
if (rs->dma_caps.max_burst > 4)
^
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c:479:19: error: 'struct dma_slave_caps' has no member named 'max_burst'
if (rs->dma_caps.max_burst > 4)
^
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c:491:5: error: implicit declaration of function 'dmaengine_terminate_sync' [-Werror=implicit-function-declaration]
dmaengine_terminate_sync(rs->dma_rx.ch);
^~~~~~~~~~~~~~~~~~~~~~~~
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c: In function 'rockchip_spi_probe':
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c:750:8: error: 'struct spi_master' has no member named 'max_transfer_size'; did you mean 'transfer_one'?
master->max_transfer_size = rockchip_spi_max_transfer_size;
^~
/home/matwey/lab/linux/drivers/spi/spi-rockchip.c:753:18: error: implicit declaration of function 'dma_request_chan' [-Werror=implicit-function-declaration]
rs->dma_tx.ch = dma_request_chan(rs->dev, "tx");
^~~~~~~~~~~~~~~~
As soon as CONFIG_SPI_ROCKCHIP is not set in aarch64 default config, I think these rk3399-*-spi-rockchip-*.patch'es have never been checked to built at all.
1) disable CONFIG_SPI_ROCKCHIP which is required not only for aarch64 boards (where it is already disabled) but by some armv7l RK3288-based (Cortex-A17 32-bit).
2) Drop rk3399-*-spi-rockchip-*.patch
0018-ARM-gic-v3-Work-around-definition-of-gic_write_bpr1.patch is armv7l specific. Required to overcome the following issue:
/tmp/ccJeHxov.s: Assembler messages:
/tmp/ccJeHxov.s:671: Error: bad or missing co-processor number -- `mcr "mrc","mcr","p15, 0, r3, c12, c12, 3",u32'
0019-drm-define-drm_compat_ioctl-NULL-on-CONFIG_COMPAT-n-.patch
required to fix the following:
Building modules, stage 2.
MODPOST 3593 modules
ERROR: "drm_compat_ioctl" [drivers/gpu/drm/hisilicon/hibmc/hibmc-drm.ko] undefined!
drm_compat_ioctl is required only for 64-bit systems. But 0001-drm-hisilicon-hibmc-Add-hisilicon-hibmc-drm-master-d.patch and 0002-drm-hisilicon-hibmc-Add-video-memory-management.patch don't take it into account. Instead of applying 0019-drm-define-drm_compat_ioctl-NULL-on-CONFIG_COMPAT-n-.patch there could be a solution to redo 0001-drm-hisilicon-hibmc-Add-hisilicon-hibmc-drm-master-d.patch and wrap drm_compat_ioctl as the following:
#ifdef CONFIG_COMPAT
.compat_ioctl = drm_compat_ioctl,
#endif
We can definitely just disable HNS for the armv7 port. That particular hardware only exists on aarch64 capable hardware. *** Bug 1043423 has been marked as a duplicate of this bug. *** What should we do with Rockchip SPI? (In reply to Matwey Kornilov from comment #22) > 0010-pwm-rcar-Make-use-of-pwm_is_enabled.patch: > > is needed to fix: > > /home/matwey/lab/linux/drivers/pwm/pwm-rcar.c: In function 'rcar_pwm_config': > /home/matwey/lab/linux/drivers/pwm/pwm-rcar.c:160:16: error: 'PWMF_ENABLED' > undeclared (first use in this function) > if (!test_bit(PWMF_ENABLED, &pwm->flags) && !duty_ns) > > It is > rk3399-pwm-0009-pwm-Move-the-enabled-disabled-info-into-pwm_state.patch who > stole PWMF_ENABLED macro definition. > Aarch64 team could found it by itself since pwm-rcar is required for Renesas > R8A7795-based 64-bit boards (but CONFIG_PWM_RCAR is not enabled in arch64 > default config). > Since pwm-rcar is useless for armv7l I think there is also option to drop > CONFIG_PWM_RCAR from armv7l config. What would you prefer? Dirk had disabled all Renesas ARMv7 drivers on master at one point, so please just disable any R-Car drivers in Leap. (-> Tumbleweed for new stuff) FWIW, patches 01-08 have been merged now. (In reply to Takashi Iwai from comment #21) [...] > > 0007-ACPI-bus-add-stub-acpi_evaluate_dsm-to-linux-acpi.h.patch > > 0008-ACPI-bus-add-stub-acpi_dev_found-to-linux-acpi.h.patch 6eb17e0df74c ACPI: bus: add stub acpi_dev_found() to linux/acpi.h (v4.8-rc1) 4ae399241adb ACPI: bus: add stub acpi_evaluate_dsm() to linux/acpi.h (v4.8-rc1) > > > > These are required to fix: > > > > /home/matwey/lab/linux/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c: > > In function 'hns_dsaf_get_cfg': > > /home/matwey/lab/linux/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c:64: > > 7: error: implicit declaration of function 'acpi_dev_found' > > [-Werror=implicit-function-declaration] > > if (acpi_dev_found(hns_dsaf_acpi_match[0].id)) > > > > So, actually it is SUSE kernel patch net-hns-dsaf-adds-support-of-acpi.patch > > which breaks hisilicon compilation for armv7l. > > I think there could be three options 1) accepting ACPI-* patches 2) fixing > > net-hns-dsaf-adds-support-of-acpi.patch, > > net-hns-net-hns-enet-adds-support-of-acpi.patch, > > net-hns-Add-ACPI-support-to-check-SFP-present.patch and > > net-hns-implement-the-miscellaneous-operation-by-asl.patch in order no to 8413b3be4d77 net: hns: dsaf adds support of acpi (v4.8-rc1) f00ef863da2b net: hns: implement the miscellaneous operation by asl (v4.8-rc1) 63434888aaf1 net: hns: net: hns: enet adds support of acpi (v4.8-rc1) b917078c1c10 net: hns: Add ACPI support to check SFP present (v4.11-rc6) > > use acpi_dev_found() and acpi_evaluate_dsm() functions at armv7l 3) disable > > NET_VENDOR_HISILICON_HNS in config and not to build this code. > > What would you prefer? > > I put Benjamin to Cc. > > But I guess these two are fine from the kABI POV, too, as they just add > dummy static inline functions. I think you're right. The two ACPI commits are part of the same series as the first three hns commits so they should all have been added at the same time. That series was merged in b1c6a3a46b8b ("Merge branch 'hns-acpi'", v4.8-rc1) Created attachment 728521 [details]
0001-ARM-add-support-for-generic-early_ioremap-early_memr.patch
0001-ARM-add-support-for-generic-early_ioremap-early_memr.patch
is required to fix the following build issue:
[ 314s] ../scripts/Makefile.build:259: recipe for target 'arch/arm/kernel/setup.o' failed
[ 314s] In file included from ../arch/arm/kernel/setup.c:41:0:
[ 314s] ../arch/arm/include/asm/efi.h:14:31: fatal error: asm/early_ioremap.h: No such file or directory
[ 314s] #include <asm/early_ioremap.h>
[ 314s] ^
[ 314s] compilation terminated.
introduced by
patches.arch/qcom-0004-ARM-wire-up-UEFI-init-and-runtime-support.patch
Hi, I've just found yet another one build issue... What is about the other half of patches? Let's try to reduce the unnecessary kconfigs at first. We can add patches later for the disabled builds, but the highest priority at this moment is to give the minimal changes to make the things working as soon as possible. Created attachment 728695 [details]
0001-armv7hl-config-Update-config-to-fix-kernel-build.patch
I've disabled all affected drivers.
But we still need the following:
0019-drm-define-drm_compat_ioctl-NULL-on-CONFIG_COMPAT-n-.patch
0001-ARM-add-support-for-generic-early_ioremap-early_memr.patch
They can not be workarounded by config.
Sorry, I was wrong. We need 0018-ARM-gic-v3-Work-around-definition-of-gic_write_bpr1.patch instead of 0019-drm-define-drm_compat_ioctl-NULL-on-CONFIG_COMPAT-n-.patch Thanks! That's a good deal. Now I applied two patches and updated the armv7hl config on openSUSE-42.3 branch. Let me know if anything is still missing. Created attachment 728770 [details]
0001-armv7hl-config-Add-missed-CONFIG_GENERIC_EARLY_IOREM.patch
Hello,
We need to apply additional changes to armv7hl config to make OBS build procedure happy:
[ 323s] #
[ 323s] # configuration written to .config
[ 323s] #
[ 323s] + /home/abuild/rpmbuild/SOURCES/check-for-config-changes .config.orig .config
[ 324s]
[ 324s] Changes after running `make oldconfig':
[ 324s] +CONFIG_GENERIC_EARLY_IOREMAP=y
[ 324s]
[ 324s] error: Bad exit status from /var/tmp/rpm-tmp.TWI0ZJ (%prep)
Ah yeah I forgot to merge the pending changes in my local repo after run_oldconfig.sh, sorry. This is an autogenerated message for OBS integration: This bug (1043231) was mentioned in https://build.opensuse.org/request/show/504823 42.2 / kernel-source The 42.3 kernel is building now, so I guess we can close this one. openSUSE-SU-2017:1633-1: An update that solves four vulnerabilities and has 35 fixes is now available. Category: security (important) Bug References: 1012060,1012382,1012422,1012829,1015452,1022595,1031796,1032339,1036638,1037840,1038085,1039348,1039900,1040855,1041242,1041431,1041810,1042286,1042356,1042421,1042517,1042535,1042536,1042886,1043014,1043231,1043236,1043371,1043467,1043598,1043935,1044015,1044125,1044532,863764,966321,966339,971975,995542 CVE References: CVE-2017-1000364,CVE-2017-1000380,CVE-2017-7346,CVE-2017-9242 Sources used: openSUSE Leap 42.2 (src): kernel-debug-4.4.72-18.12.2, kernel-default-4.4.72-18.12.2, kernel-docs-4.4.72-18.12.3, kernel-obs-build-4.4.72-18.12.2, kernel-obs-qa-4.4.72-18.12.1, kernel-source-4.4.72-18.12.1, kernel-syms-4.4.72-18.12.1, kernel-vanilla-4.4.72-18.12.2 SUSE-SU-2017:1853-1: An update that solves 15 vulnerabilities and has 162 fixes is now available. Category: security (important) Bug References: 1003581,1004003,1011044,1012060,1012382,1012422,1012452,1012829,1012910,1012985,1013561,1013887,1015342,1015452,1017461,1018885,1020412,1021424,1022266,1022595,1023287,1025461,1026570,1027101,1027512,1027974,1028217,1028310,1028340,1028883,1029607,1030057,1030070,1031040,1031142,1031147,1031470,1031500,1031512,1031555,1031717,1031796,1032141,1032339,1032345,1032400,1032581,1032803,1033117,1033281,1033336,1033340,1033885,1034048,1034419,1034635,1034670,1034671,1034762,1034902,1034995,1035024,1035866,1035887,1035920,1035922,1036214,1036638,1036752,1036763,1037177,1037186,1037384,1037483,1037669,1037840,1037871,1037969,1038033,1038043,1038085,1038142,1038143,1038297,1038458,1038544,1038842,1038843,1038846,1038847,1038848,1038879,1038981,1038982,1039214,1039348,1039354,1039700,1039864,1039882,1039883,1039885,1039900,1040069,1040125,1040182,1040279,1040351,1040364,1040395,1040425,1040463,1040567,1040609,1040855,1040929,1040941,1041087,1041160,1041168,1041242,1041431,1041810,1042286,1042356,1042421,1042517,1042535,1042536,1042863,1042886,1043014,1043231,1043236,1043347,1043371,1043467,1043488,1043598,1043912,1043935,1043990,1044015,1044082,1044120,1044125,1044532,1044767,1044772,1044854,1044880,1044912,1045154,1045235,1045286,1045307,1045467,1045568,1046105,1046434,1046589,799133,863764,922871,939801,966170,966172,966191,966321,966339,971975,988065,989311,990058,990682,993832,995542 CVE References: CVE-2017-1000365,CVE-2017-1000380,CVE-2017-7346,CVE-2017-7487,CVE-2017-7616,CVE-2017-7618,CVE-2017-8890,CVE-2017-8924,CVE-2017-8925,CVE-2017-9074,CVE-2017-9075,CVE-2017-9076,CVE-2017-9077,CVE-2017-9150,CVE-2017-9242 Sources used: SUSE Linux Enterprise Workstation Extension 12-SP2 (src): kernel-default-4.4.74-92.29.1 SUSE Linux Enterprise Software Development Kit 12-SP2 (src): kernel-docs-4.4.74-92.29.3, kernel-obs-build-4.4.74-92.29.1 SUSE Linux Enterprise Server for Raspberry Pi 12-SP2 (src): kernel-default-4.4.74-92.29.1, kernel-source-4.4.74-92.29.1, kernel-syms-4.4.74-92.29.1 SUSE Linux Enterprise Server 12-SP2 (src): kernel-default-4.4.74-92.29.1, kernel-source-4.4.74-92.29.1, kernel-syms-4.4.74-92.29.1 SUSE Linux Enterprise Live Patching 12 (src): kgraft-patch-SLE12-SP2_Update_10-1-4.1 SUSE Linux Enterprise High Availability 12-SP2 (src): kernel-default-4.4.74-92.29.1 SUSE Linux Enterprise Desktop 12-SP2 (src): kernel-default-4.4.74-92.29.1, kernel-source-4.4.74-92.29.1, kernel-syms-4.4.74-92.29.1 OpenStack Cloud Magnum Orchestration 7 (src): kernel-default-4.4.74-92.29.1 SUSE-SU-2017:1990-1: An update that solves 43 vulnerabilities and has 282 fixes is now available. Category: security (important) Bug References: 1000092,1003077,1003581,1004003,1007729,1007959,1007962,1008842,1009674,1009718,1010032,1010612,1010690,1011044,1011176,1011913,1012060,1012382,1012422,1012452,1012829,1012910,1012985,1013001,1013561,1013792,1013887,1013994,1014120,1014136,1015342,1015367,1015452,1015609,1016403,1017164,1017170,1017410,1017461,1017641,1018100,1018263,1018358,1018385,1018419,1018446,1018813,1018885,1018913,1019061,1019148,1019163,1019168,1019260,1019351,1019594,1019614,1019618,1019630,1019631,1019784,1019851,1020048,1020214,1020412,1020488,1020602,1020685,1020817,1020945,1020975,1021082,1021248,1021251,1021258,1021260,1021294,1021424,1021455,1021474,1021762,1022181,1022266,1022304,1022340,1022429,1022476,1022547,1022559,1022595,1022785,1022971,1023101,1023175,1023287,1023762,1023866,1023884,1023888,1024015,1024081,1024234,1024508,1024938,1025039,1025235,1025461,1025683,1026024,1026405,1026462,1026505,1026509,1026570,1026692,1026722,1027054,1027066,1027101,1027153,1027179,1027189,1027190,1027195,1027273,1027512,1027565,1027616,1027974,1028017,1028027,1028041,1028158,1028217,1028310,1028325,1028340,1028372,1028415,1028819,1028883,1028895,1029220,1029514,1029607,1029634,1029986,1030057,1030070,1030118,1030213,1030573,1031003,1031040,1031052,1031142,1031147,1031200,1031206,1031208,1031440,1031470,1031500,1031512,1031555,1031579,1031662,1031717,1031796,1031831,1032006,1032141,1032339,1032345,1032400,1032581,1032673,1032681,1032803,1033117,1033281,1033287,1033336,1033340,1033885,1034048,1034419,1034635,1034670,1034671,1034762,1034902,1034995,1035024,1035866,1035887,1035920,1035922,1036214,1036638,1036752,1036763,1037177,1037186,1037384,1037483,1037669,1037840,1037871,1037969,1038033,1038043,1038085,1038142,1038143,1038297,1038458,1038544,1038842,1038843,1038846,1038847,1038848,1038879,1038981,1038982,1039348,1039354,1039700,1039864,1039882,1039883,1039885,1039900,1040069,1040125,1040182,1040279,1040351,1040364,1040395,1040425,1040463,1040567,1040609,1040855,1040929,1040941,1041087,1041160,1041168,1041242,1041431,1041810,1042200,1042286,1042356,1042421,1042517,1042535,1042536,1042863,1042886,1043014,1043231,1043236,1043347,1043371,1043467,1043488,1043598,1043912,1043935,1043990,1044015,1044082,1044120,1044125,1044532,1044767,1044772,1044854,1044880,1044912,1045154,1045235,1045286,1045307,1045340,1045467,1045568,1046105,1046434,1046589,799133,863764,870618,922871,951844,966170,966172,966191,966321,966339,968697,969479,969755,970083,971975,982783,985561,986362,986365,987192,987576,988065,989056,989311,990058,990682,991273,993832,995542,995968,998106 CVE References: CVE-2016-10200,CVE-2016-2117,CVE-2016-4997,CVE-2016-4998,CVE-2016-7117,CVE-2016-9191,CVE-2017-1000364,CVE-2017-1000365,CVE-2017-1000380,CVE-2017-2583,CVE-2017-2584,CVE-2017-2596,CVE-2017-2636,CVE-2017-2671,CVE-2017-5551,CVE-2017-5576,CVE-2017-5577,CVE-2017-5897,CVE-2017-5970,CVE-2017-5986,CVE-2017-6074,CVE-2017-6214,CVE-2017-6345,CVE-2017-6346,CVE-2017-6347,CVE-2017-6353,CVE-2017-7184,CVE-2017-7187,CVE-2017-7261,CVE-2017-7294,CVE-2017-7308,CVE-2017-7346,CVE-2017-7374,CVE-2017-7487,CVE-2017-7616,CVE-2017-7618,CVE-2017-8890,CVE-2017-9074,CVE-2017-9075,CVE-2017-9076,CVE-2017-9077,CVE-2017-9150,CVE-2017-9242 Sources used: SUSE Linux Enterprise Real Time Extension 12-SP2 (src): kernel-rt-4.4.74-7.10.1, kernel-rt_debug-4.4.74-7.10.1, kernel-source-rt-4.4.74-7.10.1, kernel-syms-rt-4.4.74-7.10.1 |
Created attachment 728059 [details] 0001-ARM-EXYNOS-Remove-calls-to-of_genpd_get_from_provide.patch Hello, There is Leap 42.3 Port for armv7hl architecture. However, in order to build kernel the patches attached here should be applied. kernel-vanilla is built successfully. kernel-default patching is required to adapt armv7hl-specific parts to backported suse patches.