4.14.147-stable review
Subsystems (7)
Greg Kroah-Hartman
maintainerPATCH 178/185 hwrng: core - dont wait on add_early_randomness()
In reply to Greg Kroah-HartmanFrom: Laurent Vivier <[email protected]>
commit 78887832e76541f77169a24ac238fccb51059b63 upstream.
add_early_randomness() is called by hwrng_register() when the hardware is added. If this hardware and its module are present at boot, and if there is no data available the boot hangs until data are available and can't be interrupted.
For instance, in the case of virtio-rng, in some cases the host can be not able to provide enough entropy for all the guests.
We can have two easy ways to reproduce the problem but they rely on misconfiguration of the hypervisor or the egd daemon:
- if virtio-rng device is configured to connect to the egd daemon of the host but when the virtio-rng driver asks for data the daemon is not connected,
- if virtio-rng device is configured to connect to the egd daemon of the host but the egd daemon doesn't provide data.
The guest kernel will hang at boot until the virtio-rng driver provides enough data.
To avoid that, call rng_get_data() in non-blocking mode (wait=0) from add_early_randomness().
--- drivers/char/hw_random/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/char/hw_random/core.c +1 -1
@@ -67,7 +67,7 @@ static void add_early_randomness(structsize_t size =min_t (size_t,16 ,rng_buffer_size ());mutex_lock (&reading_mutex); - bytes_read =rng_get_data (rng, rng_buffer, size,1 ); + bytes_read =rng_get_data (rng, rng_buffer, size,0 );mutex_unlock (&reading_mutex);if (bytes_read >0 )add_device_randomness (rng_buffer, bytes_read);
Greg Kroah-Hartman
maintainerPATCH 179/185 i2c: riic: Clear NACK in tend isr
In reply to Greg Kroah-HartmanFrom: Chris Brandt <[email protected]>
commit a71e2ac1f32097fbb2beab098687a7a95c84543e upstream.
The NACKF flag should be cleared in INTRIICNAKI interrupt processing as description in HW manual.
This issue shows up quickly when PREEMPT_RT is applied and a device is probed that is not plugged in (like a touchscreen controller). The result is endless interrupts that halt system boot.
--- drivers/i2c/busses/i2c-riic.c | 1 + 1 file changed, 1 insertion(+)
drivers/i2c/busses/i2c-riic.c +1 -0
@@ -212,6 +212,7 @@ static irqreturn_t riic_tend_isr(int irqif (readb (riic->base +RIIC_ICSR2 ) &ICSR2_NACKF ) {/* We got a NACKIE */ readb (riic->base +RIIC_ICDRR );/* dummy read */ +riic_clear_set_bit (riic,ICSR2_NACKF ,0 ,RIIC_ICSR2 ); riic->err = -ENXIO ; }else if (riic->bytes_left) {return IRQ_NONE ;
Greg Kroah-Hartman
maintainerPATCH 180/185 CIFS: fix max ea value size
In reply to Greg Kroah-HartmanFrom: Murphy Zhou <[email protected]>
commit 63d37fb4ce5ae7bf1e58f906d1bf25f036fe79b2 upstream.
It should not be larger then the slab max buf size. If user specifies a larger size, it passes this check and goes straightly to SMB2_set_info_init performing an insecure memcpy.
--- fs/cifs/xattr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/cifs/xattr.c +1 -1
@@ -31,7 +31,7 @@#include "cifs_fs_sb.h" #include "cifs_unicode.h" -#define MAX_EA_VALUE_SIZE 65535 +#define MAX_EA_VALUE_SIZE CIFSMaxBufSize#define CIFS_XATTR_CIFS_ACL "system.cifs_acl"#define CIFS_XATTR_ATTRIB "cifs.dosattrib"/* full name: user.cifs.dosattrib */ #define CIFS_XATTR_CREATETIME "cifs.creationtime"/* user.cifs.creationtime */
Greg Kroah-Hartman
maintainerPATCH 181/185 CIFS: Fix oplock handling for SMB 2.1+ protocols
In reply to Greg Kroah-HartmanFrom: Pavel Shilovsky <[email protected]>
commit a016e2794fc3a245a91946038dd8f34d65e53cc3 upstream.
There may be situations when a server negotiates SMB 2.1 protocol version or higher but responds to a CREATE request with an oplock rather than a lease.
Currently the client doesn't handle such a case correctly:
when another CREATE comes in the server sends an oplock break to the initial CREATE and the client doesn't send an ack back due to a wrong caching level being set (READ instead of RWH). Missing an oplock break ack makes the server wait until the break times out which dramatically increases the latency of the second CREATE.
Fix this by properly detecting oplocks when using SMB 2.1 protocol version and higher.
--- fs/cifs/smb2ops.c | 5 +++++ 1 file changed, 5 insertions(+)
fs/cifs/smb2ops.c +5 -0
@@ -1975,6 +1975,11 @@ smb21_set_oplock_level(struct cifsInodeIif (oplock ==SMB2_OPLOCK_LEVEL_NOCHANGE )return ; +/* Check if the server granted an oplock rather than a lease */ +if (oplock &SMB2_OPLOCK_LEVEL_EXCLUSIVE ) +return smb2_set_oplock_level (cinode, oplock, epoch, + purge_cache); +if (oplock &SMB2_LEASE_READ_CACHING_HE ) { new_oplock |=CIFS_CACHE_READ_FLG ;strcat (message,"R" );
Greg Kroah-Hartman
maintainerPATCH 182/185 md/raid0: avoid RAID0 data corruption due to layout confusion.
In reply to Greg Kroah-HartmanFrom: NeilBrown <[email protected]>
[ Upstream commit c84a1372df929033cb1a0441fb57bd3932f39ac9 ]
If the drives in a RAID0 are not all the same size, the array is divided into zones.
The first zone covers all drives, to the size of the smallest. The second zone covers all drives larger than the smallest, up to the size of the second smallest - etc.
A change in Linux 3.14 unintentionally changed the layout for the second and subsequent zones. All the correct data is still stored, but each chunk may be assigned to a different device than in pre-3.14 kernels. This can lead to data corruption.
It is not possible to determine what layout to use - it depends which kernel the data was written by.
So we add a module parameter to allow the old (0) or new (1) layout to be specified, and refused to assemble an affected array if that parameter is not set.
--- drivers/md/raid0.c | 33 ++++++++++++++++++++++++++++++++- drivers/md/raid0.h | 14 ++++++++++++++ 2 files changed, 46 insertions(+), 1 deletion(-)
drivers/md/raid0.c +32 -1
@@ -26,6 +26,9 @@#include "raid0.h" #include "raid5.h" +static int default_layout =0 ; +module_param (default_layout, int,0644 ); +#define UNSUPPORTED_MDDEV_FLAGS \ ((1L << MD_HAS_JOURNAL) | \ (1L << MD_JOURNAL_CLEAN) | \
@@ -146,6 +149,19 @@ static int create_strip_zones(struct mddev *mddev, struct r0conf **private_conf) }pr_debug ("md/raid0:%s: FINAL %d zones\n" ,mdname (mddev), conf->nr_strip_zones); + +if (conf->nr_strip_zones ==1 ) { + conf->layout =RAID0_ORIG_LAYOUT ; + }else if (default_layout ==RAID0_ORIG_LAYOUT || + default_layout ==RAID0_ALT_MULTIZONE_LAYOUT ) { + conf->layout = default_layout; + }else { +pr_err ("md/raid0:%s: cannot assemble multi-zone RAID0 with default_layout setting\n" , +mdname (mddev)); +pr_err ("md/raid0: please set raid.default_layout to 1 or 2\n" ); + err = -ENOTSUPP ; + goto abort; + }/* * now since we have the hard sector sizes, we can make sure * chunk size is a multiple of that sector size
@@ -552,10 +568,12 @@ static void raid0_handle_discard(struct mddev *mddev, struct bio *bio)static bool raid0_make_request (struct mddev *mddev,struct bio *bio) { +struct r0conf *conf = mddev->private;struct strip_zone *zone;struct md_rdev *tmp_dev;sector_t bio_sector;sector_t sector; +sector_t orig_sector;unsigned chunk_sects;unsigned sectors;
@@ -588,8 +606,21 @@ static bool raid0_make_request(struct mddev *mddev, struct bio *bio) bio = split; } + orig_sector = sector; zone =find_zone (mddev->private, §or); - tmp_dev =map_sector (mddev, zone, sector, §or); +switch (conf->layout) { +case RAID0_ORIG_LAYOUT : + tmp_dev =map_sector (mddev, zone, orig_sector, §or); +break ; +case RAID0_ALT_MULTIZONE_LAYOUT : + tmp_dev =map_sector (mddev, zone, sector, §or); +break ; +default : +WARN ("md/raid0:%s: Invalid layout\n" ,mdname (mddev)); +bio_io_error (bio); +return true; + } +bio_set_dev (bio, tmp_dev->bdev); bio->bi_iter.bi_sector = sector + zone->dev_start + tmp_dev->data_offset;
drivers/md/raid0.h +14 -0
@@ -8,11 +8,25 @@ struct strip_zone { int nb_dev; /* # of devices attached to the zone */ }; +/* Linux 3.14 (20d0189b101) made an unintended change to +* the RAID0 layout for multi-zone arrays (where devices aren't all +* the same size. +* RAID0_ORIG_LAYOUT restores the original layout +* RAID0_ALT_MULTIZONE_LAYOUT uses the altered layout +* The layouts are identical when there is only one zone (all +* devices the same size). +*/ + +enum r0layout { +RAID0_ORIG_LAYOUT =1 , +RAID0_ALT_MULTIZONE_LAYOUT =2 , +};struct r0conf {struct strip_zone *strip_zone;struct md_rdev **devlist;/* lists of rdevs, pointed to * by strip_zone->dev */ int nr_strip_zones; +enum r0layout layout; };#endif
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 183/185 mm/compaction.c: clear total_{migrate,free}_scanned before scanning a new zone
In reply to Greg Kroah-HartmanFrom: Yafang Shao <[email protected]>
[ Upstream commit a94b525241c0fff3598809131d7cfcfe1d572d8c ]
total_{migrate,free}_scanned will be added to COMPACTMIGRATE_SCANNED and COMPACTFREE_SCANNED in compact_zone(). We should clear them before scanning a new zone. In the proc triggered compaction, we forgot clearing them.
--- mm/compaction.c | 35 +++++++++++++---------------------- 1 file changed, 13 insertions(+), 22 deletions(-)
mm/compaction.c +13 -22
@@ -1517,6 +1517,17 @@ static enum compact_result compact_zone(struct zone *zone, struct compact_controunsigned long end_pfn =zone_end_pfn (zone);const bool sync = cc->mode !=MIGRATE_ASYNC ; +/* +* These counters track activities during zone compaction. Initialize +* them before compacting a new zone. +*/ + cc->total_migrate_scanned =0 ; + cc->total_free_scanned =0 ; + cc->nr_migratepages =0 ; + cc->nr_freepages =0 ; +INIT_LIST_HEAD (&cc->freepages); +INIT_LIST_HEAD (&cc->migratepages); + cc->migratetype =gfpflags_to_migratetype (cc->gfp_mask); ret =compaction_suitable (zone, cc->order, cc->alloc_flags, cc->classzone_idx);
@@ -1680,10 +1691,6 @@ static enum compact_result compact_zone_order(struct zone *zone, int order, {enum compact_result ret;struct compact_control cc = { - .nr_freepages =0 , - .nr_migratepages =0 , - .total_migrate_scanned =0 , - .total_free_scanned =0 , .order = order, .gfp_mask = gfp_mask, .zone = zone,
@@ -1696,8 +1703,6 @@ static enum compact_result compact_zone_order(struct zone *zone, int order, .ignore_skip_hint = (prio == MIN_COMPACT_PRIORITY), .ignore_block_suitable = (prio == MIN_COMPACT_PRIORITY) }; -INIT_LIST_HEAD (&cc.freepages); -INIT_LIST_HEAD (&cc.migratepages); ret =compact_zone (zone, &cc);
@@ -1796,8 +1801,6 @@ static void compact_node(int nid)struct zone *zone;struct compact_control cc = { .order =-1 , - .total_migrate_scanned =0 , - .total_free_scanned =0 , .mode =MIGRATE_SYNC , .ignore_skip_hint = true, .whole_zone = true,
@@ -1811,11 +1814,7 @@ static void compact_node(int nid)if (!populated_zone (zone))continue ; - cc.nr_freepages =0 ; - cc.nr_migratepages =0 ; cc.zone = zone; -INIT_LIST_HEAD (&cc.freepages); -INIT_LIST_HEAD (&cc.migratepages);compact_zone (zone, &cc);
@@ -1924,8 +1923,6 @@ static void kcompactd_do_work(pg_data_t *pgdat)struct zone *zone;struct compact_control cc = { .order = pgdat->kcompactd_max_order, - .total_migrate_scanned =0 , - .total_free_scanned =0 , .classzone_idx = pgdat->kcompactd_classzone_idx, .mode =MIGRATE_SYNC_LIGHT , .ignore_skip_hint = true,
@@ -1950,16 +1947,10 @@ static void kcompactd_do_work(pg_data_t *pgdat) COMPACT_CONTINUE)continue ; - cc.nr_freepages =0 ; - cc.nr_migratepages =0 ; - cc.total_migrate_scanned =0 ; - cc.total_free_scanned =0 ; - cc.zone = zone; -INIT_LIST_HEAD (&cc.freepages); -INIT_LIST_HEAD (&cc.migratepages); -if (kthread_should_stop ())return ; + + cc.zone = zone; status =compact_zone (zone, &cc);if (status ==COMPACT_SUCCESS ) {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 184/185 btrfs: qgroup: Drop quota_root and fs_info parameters from update_qgroup_status_item
In reply to Greg Kroah-HartmanFrom: Lu Fengqi <[email protected]>
[ Upstream commit 2e980acdd829742966c6a7e565ef3382c0717295 ]
They can be fetched from the transaction handle.
--- fs/btrfs/qgroup.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
fs/btrfs/qgroup.c +6 -6
@@ -722,10 +722,10 @@ static int update_qgroup_info_item(struct btrfs_trans_handle *trans,return ret; } -static int update_qgroup_status_item (struct btrfs_trans_handle *trans, -struct btrfs_fs_info *fs_info, -struct btrfs_root *root) +static int update_qgroup_status_item (struct btrfs_trans_handle *trans) { +struct btrfs_fs_info *fs_info = trans->fs_info; +struct btrfs_root *quota_root = fs_info->quota_root;struct btrfs_path *path;struct btrfs_key key;struct extent_buffer *l;
@@ -741,7 +741,7 @@ static int update_qgroup_status_item(struct btrfs_trans_handle *trans,if (!path)return -ENOMEM ; - ret =btrfs_search_slot (trans, root, &key, path,0 ,1 ); + ret =btrfs_search_slot (trans, quota_root, &key, path,0 ,1 );if (ret >0 ) ret = -ENOENT ;
@@ -2110,7 +2110,7 @@ int btrfs_run_qgroups(struct btrfs_trans_handle *trans, fs_info->qgroup_flags &= ~BTRFS_QGROUP_STATUS_FLAG_ON ;spin_unlock (&fs_info->qgroup_lock); - ret =update_qgroup_status_item (trans, fs_info, quota_root); + ret =update_qgroup_status_item (trans);if (ret) fs_info->qgroup_flags |=BTRFS_QGROUP_STATUS_FLAG_INCONSISTENT ;
@@ -2668,7 +2668,7 @@ static void btrfs_qgroup_rescan_worker(struct btrfs_work *work) err); goto done; } - ret =update_qgroup_status_item (trans, fs_info, fs_info->quota_root); + ret =update_qgroup_status_item (trans);if (ret <0 ) { err = ret;btrfs_err (fs_info,"fail to update qgroup status: %d" , err);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 185/185 Btrfs: fix race setting up and completing qgroup rescan workers
In reply to Greg Kroah-HartmanFrom: Filipe Manana <[email protected]>
[ Upstream commit 13fc1d271a2e3ab8a02071e711add01fab9271f6 ]
There is a race between setting up a qgroup rescan worker and completing a qgroup rescan worker that can lead to callers of the qgroup rescan wait ioctl to either not wait for the rescan worker to complete or to hang forever due to missing wake ups. The following diagram shows a sequence of steps that illustrates the race.
CPU 1 CPU 2 CPU 3
btrfs_ioctl_quota_rescan()
btrfs_qgroup_rescan()
qgroup_rescan_init()
mutex_lock(&fs_info->qgroup_rescan_lock)
spin_lock(&fs_info->qgroup_lock)
fs_info->qgroup_flags |=
BTRFS_QGROUP_STATUS_FLAG_RESCAN
init_completion(
&fs_info->qgroup_rescan_completion)
fs_info->qgroup_rescan_running = true
mutex_unlock(&fs_info->qgroup_rescan_lock)
spin_unlock(&fs_info->qgroup_lock)
btrfs_init_work()
--> starts the worker
btrfs_qgroup_rescan_worker()
mutex_lock(&fs_info->qgroup_rescan_lock)
fs_info->qgroup_flags &=
~BTRFS_QGROUP_STATUS_FLAG_RESCAN
mutex_unlock(&fs_info->qgroup_rescan_lock)
starts transaction, updates qgroup status
item, etc
btrfs_ioctl_quota_rescan()
btrfs_qgroup_rescan()
qgroup_rescan_init()
mutex_lock(&fs_info->qgroup_rescan_lock)
spin_lock(&fs_info->qgroup_lock)
fs_info->qgroup_flags |=
BTRFS_QGROUP_STATUS_FLAG_RESCAN
init_completion(
&fs_info->qgroup_rescan_completion)
fs_info->qgroup_rescan_running = true
mutex_unlock(&fs_info->qgroup_rescan_lock)
spin_unlock(&fs_info->qgroup_lock)
btrfs_init_work()
--> starts another worker
mutex_lock(&fs_info->qgroup_rescan_lock)
fs_info->qgroup_rescan_running = false
mutex_unlock(&fs_info->qgroup_rescan_lock)
complete_all(&fs_info->qgroup_rescan_completion)Before the rescan worker started by the task at CPU 3 completes, if another task calls btrfs_ioctl_quota_rescan(), it will get -EINPROGRESS because the flag BTRFS_QGROUP_STATUS_FLAG_RESCAN is set at fs_info->qgroup_flags, which is expected and correct behaviour.
However if other task calls btrfs_ioctl_quota_rescan_wait() before the rescan worker started by the task at CPU 3 completes, it will return immediately without waiting for the new rescan worker to complete, because fs_info->qgroup_rescan_running is set to false by CPU 2.
This race is making test case btrfs/171 (from fstests) to fail often:
btrfs/171 9s ... - output mismatch (see /home/fdmanana/git/hub/xfstests/results//btrfs/171.out.bad)
# --- tests/btrfs/171.out 2018-09-16 21:30:48.505104287 +0100 # +++ /home/fdmanana/git/hub/xfstests/results//btrfs/171.out.bad 2019-09-19 02:01:36.938486039 +0100 # @@ -1,2 +1,3 @@
# QA output created by 171
# +ERROR: quota rescan failed: Operation now in progress
# Silence is golden
# ...
# (Run 'diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/171.out /home/fdmanana/git/hub/xfstests/results//btrfs/171.out.bad' to see the entire diff)
That is because the test calls the btrfs-progs commands "qgroup quota rescan -w", "qgroup assign" and "qgroup remove" in a sequence that makes calls to the rescan start ioctl fail with -EINPROGRESS (note the "btrfs" commands 'qgroup assign' and 'qgroup remove' often call the rescan start ioctl after calling the qgroup assign ioctl, btrfs_ioctl_qgroup_assign()), since previous waits didn't actually wait for a rescan worker to complete.
Another problem the race can cause is missing wake ups for waiters, since the call to complete_all() happens outside a critical section and after clearing the flag BTRFS_QGROUP_STATUS_FLAG_RESCAN. In the sequence diagram above, if we have a waiter for the first rescan task (executed by CPU 2), then fs_info->qgroup_rescan_completion.wait is not empty, and if after the rescan worker clears BTRFS_QGROUP_STATUS_FLAG_RESCAN and before it calls complete_all() against fs_info->qgroup_rescan_completion, the task at CPU 3 calls init_completion() against fs_info->qgroup_rescan_completion which re-initilizes its wait queue to an empty queue, therefore causing the rescan worker at CPU 2 to call complete_all() against an empty queue, never waking up the task waiting for that rescan worker.
Fix this by clearing BTRFS_QGROUP_STATUS_FLAG_RESCAN and setting fs_info->qgroup_rescan_running to false in the same critical section, delimited by the mutex fs_info->qgroup_rescan_lock, as well as doing the call to complete_all() in that same critical section. This gives the protection needed to avoid rescan wait ioctl callers not waiting for a running rescan worker and the lost wake ups problem, since setting that rescan flag and boolean as well as initializing the wait queue is done already in a critical section delimited by that mutex (at qgroup_rescan_init()).
--- fs/btrfs/qgroup.c | 33 +++++++++++++++++++-------------- 1 file changed, 19 insertions(+), 14 deletions(-)
fs/btrfs/qgroup.c +19 -14
@@ -2645,9 +2645,6 @@ out:btrfs_free_path (path);mutex_lock (&fs_info->qgroup_rescan_lock); -if (!btrfs_fs_closing (fs_info)) - fs_info->qgroup_flags &= ~BTRFS_QGROUP_STATUS_FLAG_RESCAN ; -if (err >0 && fs_info->qgroup_flags &BTRFS_QGROUP_STATUS_FLAG_INCONSISTENT ) { fs_info->qgroup_flags &= ~BTRFS_QGROUP_STATUS_FLAG_INCONSISTENT ;
@@ -2663,16 +2660,30 @@ out: trans =btrfs_start_transaction (fs_info->quota_root,1 );if (IS_ERR (trans)) { err =PTR_ERR (trans); + trans =NULL ;btrfs_err (fs_info,"fail to start transaction for status update: %d" , err); - goto done; } - ret =update_qgroup_status_item (trans); -if (ret <0 ) { - err = ret; -btrfs_err (fs_info,"fail to update qgroup status: %d" , err); + +mutex_lock (&fs_info->qgroup_rescan_lock); +if (!btrfs_fs_closing (fs_info)) + fs_info->qgroup_flags &= ~BTRFS_QGROUP_STATUS_FLAG_RESCAN ; +if (trans) { + ret =update_qgroup_status_item (trans); +if (ret <0 ) { + err = ret; +btrfs_err (fs_info,"fail to update qgroup status: %d" , + err); + } } + fs_info->qgroup_rescan_running = false; +complete_all (&fs_info->qgroup_rescan_completion); +mutex_unlock (&fs_info->qgroup_rescan_lock); + +if (!trans) +return ; +btrfs_end_transaction (trans);if (btrfs_fs_closing (fs_info)) {
@@ -2683,12 +2694,6 @@ out: }else {btrfs_err (fs_info,"qgroup scan failed with %d" , err); } - -done: -mutex_lock (&fs_info->qgroup_rescan_lock); - fs_info->qgroup_rescan_running = false; -mutex_unlock (&fs_info->qgroup_rescan_lock); -complete_all (&fs_info->qgroup_rescan_completion); }/*
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.147 release. There are 185 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.147-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.14.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Jon Hunter
maintainerQuoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.147 release. There are 185 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.147-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.14.y
and the diffstat can be found below.thanks,
greg k-h
All tests are passing for Tegra ...
Test results for stable-v4.14:
8 builds: 8 pass, 0 fail
16 boots: 16 pass, 0 fail
24 tests: 24 pass, 0 failLinux version: 4.14.147-rc1-gb99061374089
Boards tested: tegra124-jetson-tk1, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a0
Cheers
Jon
Signature · 1 line
nvpublic
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.147 release. There are 185 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. Anything received after that time might be too late.
There's a regression listed below that happened while running 'modprobe vivid' on db410c. We've investigated it and are unable to reliably reproduce it. It happens less than 1% of the time, so it is very unlikely to be a regression. The detailed log can be found at
https://lkft.validation.linaro.org/scheduler/job/950199#L1545 and we will continue to investigate and try to narrow down the problem so that we can report it coherently.
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Summary
------------------------------------------------------------------------
kernel: 4.14.147-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.14.y
git commit: b99061374089a66c2dd55bbea3299a602a4f0891
git describe: v4.14.146-186-gb99061374089
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.14-oe/build/v4.14.146-186-gb99061374089
Regressions (compared to build v4.14.146-18-gf0e4f7af6713)
------------------------------------------------------------------------
dragonboard-410c - arm64:
v4l2-compliance:
* modprobe-vivid
No fixes (compared to build v4.14.146-18-gf0e4f7af6713)
Ran 22696 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c - arm64
- hi6220-hikey - arm64
- i386
- juno-r2 - arm64
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15 - arm
- x86_64
Test Suites
-----------
* build
* install-android-platform-tools-r2600
* kselftest
* libhugetlbfs
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-cpuhotplug-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-timers-tests
* perf
* spectre-meltdown-checker-test
* v4l2-compliance
* ltp-fs-tests
* ltp-syscalls-tests
* network-basic-tests
* ltp-open-posix-tests
* kvm-unit-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
* ssuite
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Quoted 9 lines · Dan Rue
Quoted 7 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.147 release. There are 185 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. Anything received after that time might be too late.
Quoted 9 lines
There's a regression listed below that happened while running 'modprobe vivid' on db410c. We've investigated it and are unable to reliably reproduce it. It happens less than 1% of the time, so it is very unlikely to be a regression. The detailed log can be found at
https://lkft.validation.linaro.org/scheduler/job/950199#L1545 and we will continue to investigate and try to narrow down the problem so that we can report it coherently.
Adding Hans and linux-media to the thread.
Hans! I thought you might be interested in looking at this vivid panic.
thanks,
-- Shuah
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.147 release. There are 185 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 05 Oct 2019 03:37:47 PM UTC. Anything received after that time might be too late.
Build results:
total: 172 pass: 172 fail: 0 Qemu test results: total: 372 pass: 372 fail: 0
Guenter