[PATCH 4.9 21/39] kconfig: fix file name and line number of warn_ignored_character()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 77c1c0fa8b1477c5799bdad65026ea5ff676da44 ] Currently, warn_ignore_character() displays invalid file name and line number. The lexer should use current_file->name and yylineno, while

[PATCH 4.9 12/39] rxe: IB_WR_REG_MR does not capture MRs iova field

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b024dd0eba6e6d568f69d63c5e3153aba94c23e3 ] FRWR memory registration is done with a series of calls and WRs. 1. ULP invokes ib_dma_map_sg() 2. ULP invokes ib_map_mr_sg() 3. ULP posts

Re: [PATCH] misc: aspeed-lpc-ctrl: Correct return values

On 1/24/19, 12:16 AM, "Greg Kroah-Hartman" wrote: On Wed, Jan 23, 2019 at 03:06:34PM -0800, Vijay Khemka wrote: > Corrected some of return values with appropriate meanings. > > Signed-off-by: Vijay Khemka > --- > drivers/misc/aspeed-lpc-ctrl.c | 15 +++

[PATCH 4.9 17/39] media: firewire: Fix app_info parameter type in avc_ca{,_app}_info

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b2e9a4eda11fd2cb1e6714e9ad3f455c402568ff ] Clang warns: drivers/media/firewire/firedtv-avc.c:999:45: warning: implicit conversion from 'int' to 'char' changes value from 159 to -97

[PATCH 4.9 19/39] scsi: target: use consistent left-aligned ASCII INQUIRY data

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0de263577de5d5e052be5f4f93334e63cc8a7f0b ] spc5r17.pdf specifies: 4.3.1 ASCII data field requirements ASCII data fields shall contain only ASCII printable characters (i.e.,

[PATCH 4.9 10/39] arm64: perf: set suppress_bind_attrs flag to true

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 81e9fa8bab381f8b6eb04df7cdf0f71994099bd4 ] The armv8_pmuv3 driver doesn't have a remove function, and when the test 'CONFIG_DEBUG_TEST_DRIVER_REMOVE=y' is enabled, the following Call

[PATCH 4.4 088/104] clk: imx6q: reset exclusive gates on init

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f7542d817733f461258fd3a47d77da35b2d9fc81 ] The exclusive gates may be set up in the wrong way by software running before the clock driver comes up. In that case the exclusive setup

[PATCH 4.9 01/39] r8169: Add support for new Realtek Ethernet

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng [ Upstream commit 36352991835ce99e46b4441dd0eb6980f9a83e8f ] There are two new Realtek Ethernet devices which are re-branded r8168h. Add the IDs to to support them.

[PATCH 4.4 087/104] scsi: target: use consistent left-aligned ASCII INQUIRY data

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0de263577de5d5e052be5f4f93334e63cc8a7f0b ] spc5r17.pdf specifies: 4.3.1 ASCII data field requirements ASCII data fields shall contain only ASCII printable characters (i.e.,

[PATCH 4.4 081/104] arm64: perf: set suppress_bind_attrs flag to true

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 81e9fa8bab381f8b6eb04df7cdf0f71994099bd4 ] The armv8_pmuv3 driver doesn't have a remove function, and when the test 'CONFIG_DEBUG_TEST_DRIVER_REMOVE=y' is enabled, the following Call

[PATCH 4.4 102/104] mm, proc: be more verbose about unstable VMA flags in /proc//smaps

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ] Patch series "THP eligibility reporting via proc". This series of three patches aims at making THP eligibility reporting much more robust

[PATCH 4.4 104/104] ipmi:ssif: Fix handling of multi-part return messages

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Corey Minyard commit 7d6380cd40f7993f75c4bde5b36f6019237e8719 upstream. The block number was not being compared right, it was off by one when checking the response. Some statistics wouldn't

[PATCH 4.4 103/104] net: speed up skb_rbtree_purge()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 7c90584c66cc4b033a3b684b0e0950f79e7b7166 upstream. As measured in my prior patch ("sch_netem: faster rb tree removal"), rbtree_postorder_for_each_entry_safe() is nice

[PATCH 4.4 100/104] ocfs2: fix panic due to unrecovered local alloc

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 532e1e54c8140188e192348c790317921cb2dc1c ] mount.ocfs2 ignore the inconsistent error that journal is clean but local alloc is unrecovered. After mount, local alloc not empty, then

[PATCH 4.4 099/104] scsi: megaraid: fix out-of-bound array accesses

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c7a082e4242fd8cd21a441071e622f87c16bdacc ] UBSAN reported those with MegaRAID SAS-3 3108, [ 77.467308] UBSAN: Undefined behaviour in

[PATCH 4.4 085/104] media: firewire: Fix app_info parameter type in avc_ca{,_app}_info

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b2e9a4eda11fd2cb1e6714e9ad3f455c402568ff ] Clang warns: drivers/media/firewire/firedtv-avc.c:999:45: warning: implicit conversion from 'int' to 'char' changes value from 159 to -97

[PATCH 4.4 095/104] dm kcopyd: Fix bug causing workqueue stalls

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d7e6b8dfc7bcb3f4f3a18313581f67486a725b52 ] When using kcopyd to run callbacks through dm_kcopyd_do_callback() or submitting copy jobs with a source size of 0, the jobs are pushed

[PATCH 4.4 094/104] perf parse-events: Fix unchecked usage of strncpy()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bd8d57fb7e25e9fcf67a9eef5fa13aabe2016e07 ] The strncpy() function may leave the destination string buffer unterminated, better use strlcpy() that we have a __weak fallback

[PATCH 4.4 096/104] dm snapshot: Fix excessive memory usage and workqueue stalls

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 721b1d98fb517ae99ab3b757021cf81db41e67be ] kcopyd has no upper limit to the number of jobs one can allocate and issue. Under certain workloads this can lead to excessive memory usage

[PATCH 4.4 097/104] ALSA: bebob: fix model-id of unit for Apogee Ensemble

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 644b2e97405b0b74845e1d3c2b4fe4c34858062b ] This commit fixes hard-coded model-id for an unit of Apogee Ensemble with a correct value. This unit uses DM1500 ASIC produced ArchWave AG

[PATCH 4.4 091/104] mmc: atmel-mci: do not assume idle after atmci_request_end

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ae460c115b7aa50c9a36cf78fced07b27962c9d0 ] On our AT91SAM9260 board we use the same sdio bus for wifi and for the sd card slot. This caused the atmel-mci to give the following splat

[PATCH 4.4 080/104] MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e4849aff1e169b86c561738daf8ff020e9de1011 ] The Broadcom SiByte BCM1250, BCM1125, and BCM1125H SOCs have an onchip DRAM controller that supports memory amounts of up to 16GiB, and due

[PATCH 4.4 038/104] media: em28xx: Fix misplaced reset of dev->v4l::field_count

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings The backport of commit afeaade90db4 "media: em28xx: make v4l2-compliance happier by starting sequence on zero" added a reset on em28xx_v4l2::field_count to em28xx_ctrl_notify(),

[PATCH 4.4 046/104] crypto: authencesn - Avoid twice completion call in decrypt path

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Harsh Jain commit a7773363624b034ab198c738661253d20a8055c2 upstream. Authencesn template in decrypt path unconditionally calls aead_request_complete after ahash_verify which leads to following

[PATCH 4.4 042/104] ipv6: fix kernel-infoleak in ipv6_local_error()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7d033c9f6a7fd3821af75620a0257db87c2b552a ] This patch makes sure the flow label in the IPv6 header forged in ipv6_local_error() is initialized. BUG: KMSAN:

[PATCH 4.4 076/104] xfs: dont fail when converting shortform attr to long form during ATTR_REPLACE

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 7b38460dc8e4eafba06c78f8e37099d3b34d473c upstream. Kanda Motohiro reported that expanding a tiny xattr into a large xattr fails on XFS because we remove the tiny xattr

[PATCH 4.4 044/104] packet: Do not leak dev refcounts on error exit

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe [ Upstream commit d972f3dce8d161e2142da0ab1ef25df00e2f21a9 ] 'dev' is non NULL when the addr_len check triggers so it must goto a label that does the dev_put otherwise dev will

[PATCH 4.4 069/104] loop: Get rid of loop_index_mutex

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 0a42e99b58a208839626465af194cfe640ef9493 upstream. Now that loop_ctl_mutex is global, just get rid of loop_index_mutex as there is no good reason to keep these two separate and

[PATCH 4.4 071/104] drm/fb-helper: Ignore the value of fb_var_screeninfo.pixclock

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Mironov commit 66a8d5bfb518f9f12d47e1d2dce1732279f9451e upstream. Strict requirement of pixclock to be zero breaks support of SDL 1.2 which contains hardcoded table of supported video

Re: [alsa-devel] [PATCH] ASoC: soc-core: Fix null pointer dereference in soc_find_component

On Thu, Jan 24, 2019 at 01:07:17PM -0600, Pierre-Louis Bossart wrote: > Thanks for the feedback, will send a formal patch with the helper and > machine driver changes after I test more with the legacy drivers. Do you > have a preference for one patch that deals with multiple machines drivers in >

[PATCH 4.4 070/104] loop: Fix double mutex_unlock(_ctl_mutex) in loop_control_ioctl()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit 628bd85947091830a8c4872adfd5ed1d515a9cf2 upstream. Commit 0a42e99b58a20883 ("loop: Get rid of loop_index_mutex") forgot to remove mutex_unlock(_ctl_mutex) from

[PATCH 4.4 041/104] arm64: Dont trap host pointer auth use to EL2

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Backport of upstream commit b3669b1e1c09890d61109a1a8ece2c5b66804714 ] To allow EL0 (and/or EL1) to use pointer authentication functionality, we must ensure that pointer authentication instructions

[PATCH 4.4 068/104] loop: Fold __loop_release into loop_release

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 967d1dc144b50ad005e5eecdfadfbcfb3996 upstream. __loop_release() has a single call site. Fold it there. This is currently not a huge win but it will make following

[PATCH 4.4 075/104] ipv6: Take rcu_read_lock in __inet6_bind for mapped addresses

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit d4a7e9bb74b5aaf07b89f6531c080b1130bdf019 ] I realized the last patch calls dev_get_by_index_rcu in a branch not holding the rcu lock. Add the calls to

[PATCH 4.4 067/104] block/loop: Use global lock for ioctl() operation.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit 310ca162d779efee8a2dc3731439680f3e9c1e86 upstream. syzbot is reporting NULL pointer dereference [1] which is caused by race condition between ioctl(loop_fd, LOOP_CLR_FD, 0)

[PATCH 4.4 061/104] sctp: allocate sctp_sockaddr_entry with kzalloc

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long commit 400b8b9a2a17918f8ce00786f596f530e7f30d50 upstream. The similar issue as fixed in Commit 4a2eb0c37b47 ("sctp: initialize sin6_flowinfo for ipv6 addrs in sctp_inet6addr_event")

[PATCH 4.4 065/104] tipc: fix uninit-value in tipc_nl_compat_name_table_dump

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit 974cb0e3e7c963ced06c4e32c5b2884173fa5e01 upstream. syzbot reported: BUG: KMSAN: uninit-value in __arch_swab32 arch/x86/include/uapi/asm/swab.h:10 [inline] BUG: KMSAN:

[PATCH 4.4 063/104] tipc: fix uninit-value in tipc_nl_compat_bearer_enable

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit 0762216c0ad2a2fccd63890648eca491f2c83d9a upstream. syzbot reported: BUG: KMSAN: uninit-value in strlen+0x3b/0xa0 lib/string.c:484 CPU: 1 PID: 6371 Comm: syz-executor652 Not

[PATCH 4.4 064/104] tipc: fix uninit-value in tipc_nl_compat_link_set

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ying Xue commit edf5ff04a45750ac8ce2435974f001dc9cfbf055 upstream. syzbot reports following splat: BUG: KMSAN: uninit-value in strlen+0x3b/0xa0 lib/string.c:486 CPU: 1 PID: 9306 Comm:

[PATCH 4.4 058/104] media: vb2: vb2_mmap: move lock up

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit cd26d1c4d1bc947b56ae404998ae2276df7b39b7 upstream. If a filehandle is dup()ped, then it is possible to close it from one fd and call mmap from the other. This creates a

[PATCH 4.4 040/104] arm64/kvm: consistently handle host HCR_EL2 flags

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Backport of upstream commit 4eaed6aa2c628101246bcabc91b203bfac1193f8 ] In KVM we define the configuration of HCR_EL2 for a VHE HOST in HCR_HOST_VHE_FLAGS, but we don't have a similar definition for

[PATCH 4.4 054/104] omap2fb: Fix stack memory disclosure

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Tsyrklevich commit a01421e4484327fe44f8e126793ed5a48a221e24 upstream. Using [1] for static analysis I found that the OMAPFB_QUERY_PLANE, OMAPFB_GET_COLOR_KEY, OMAPFB_GET_DISPLAY_INFO, and

[PATCH 4.4 052/104] mfd: tps6586x: Handle interrupts on suspend

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jonathan Hunter commit ac4ca4b9f4623ba5e1ea7a582f286567c611e027 upstream. The tps6586x driver creates an irqchip that is used by its various child devices for managing interrupts. The

[PATCH 4.4 055/104] media: vivid: fix error handling of kthread_run

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 701f49bc028edb19ffccd101997dd84f0d71e279 upstream. kthread_run returns an error pointer, but elsewhere in the code dev->kthread_vid_cap/out is checked against NULL. If

[PATCH 4.4 057/104] LSM: Check for NULL cred-security on free

4.4-stable review patch. If anyone has any objections, please let me know. -- From: James Morris commit a5795fd38ee8194451ba3f281f075301a3696ce2 upstream. From: Casey Schaufler Check that the cred security blob has been set before trying to clean it up. There is a case

[PATCH 4.4 053/104] Disable MSI also when pcie-octeon.pcie_disable on

4.4-stable review patch. If anyone has any objections, please let me know. -- From: YunQiang Su commit a214720cbf50cd8c3f76bbb9c3f5c283910e9d33 upstream. Octeon has an boot-time option to disable pcie. Since MSI depends on PCI-E, we should also disable MSI also with this

[PATCH 4.4 048/104] btrfs: wait on ordered extents on abort cleanup

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Josef Bacik commit 74d5d229b1bf60f93bff244b2dfc0eb21ec32a07 upstream. If we flip read-only before we initiate writeback on all dirty pages for ordered extents we've created then we'll have

[PATCH 4.4 050/104] scsi: sd: Fix cache_type_store()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Mironov commit 44759979a49bfd2d20d789add7fa81a21eb1a4ab upstream. Changing of caching mode via /sys/devices/.../scsi_disk/.../cache_type may fail if device responds to MODE SENSE command

[PATCH 4.4 049/104] Yama: Check for pid death before checking ancestry

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 9474f4e7cd71a633fa1ef93b7daefd44bbdfd482 upstream. It's possible that a pid has died before we take the rcu lock, in which case we can't walk the ancestry list as it may be

[PATCH 4.4 008/104] f2fs: remove an obsolete variable

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit fb58ae22067e0595d974e3d856522c1ed6d2d7bf upstream. This patch removes an obsolete variable used in add_free_nid. Signed-off-by: Jaegeuk Kim [bwh: Picked as dependency of

[PATCH 4.4 004/104] f2fs: cover more area with nat_tree_lock

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit a51311938e14c17f5a94d30baac9d7bec71f5858 upstream. There was a subtle bug on nat cache management which incurs wrong nid allocation or wrong block addresses when

[PATCH 4.4 005/104] f2fs: move sanity checking of cp into get_valid_checkpoint

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shawn Lin commit 984ec63c5a82a07ad4490ecc69bebacd23f6fa64 upstream. >From the function name of get_valid_checkpoint, it seems to return the valid cp or NULL for caller to check. If no valid

[PATCH 4.4 006/104] f2fs: fix to convert inline directory correctly

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu With below serials, we will lose parts of dirents: 1) mount f2fs with inline_dentry option 2) echo 1 > /sys/fs/f2fs/sdX/dir_level 3) mkdir dir 4) touch 180 files named [1-180] in dir

[PATCH 4.4 029/104] f2fs: Add sanity_check_inode() function

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This was done as part of commits 5d64600d4f33 "f2fs: avoid bug_on on corrupted inode" and 76d56d4ab4f2 "f2fs: fix to do sanity check with extra_attr feature" upstream, but the

[PATCH 4.4 032/104] f2fs: fix to do sanity check with block address in main area

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit c9b60788fc760d136211853f10ce73dc152d1f4a upstream. This patch add to do sanity check with below field: - cp_pack_total_block_count - blkaddr of data/node - extent info -

[PATCH 4.4 035/104] f2fs: fix invalid memory access

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit d3f07c049dab1a3f1740f476afd3d5e5b738c21c upstream. syzbot found the following crash on: HEAD commit:d9bd94c0bcaa Add linux-next specific files for 20180801 git tree:

[PATCH 4.4 026/104] f2fs: introduce and spread verify_blkaddr

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit e1da7872f6eda977bd812346bf588c35e4495a1e upstream. This patch introduces verify_blkaddr to check meta/data block address with valid range to detect bug earlier. In addition,

[PATCH 4.4 027/104] f2fs: fix to do sanity check with secs_per_zone

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit 42bf546c1fe3f3654bdf914e977acbc2b80a5be5 upstream. As Wen Xu reported in below link: https://bugzilla.kernel.org/show_bug.cgi?id=200183 - Overview Divide zero in

[PATCH 4.4 024/104] f2fs: enhance sanity_check_raw_super() to avoid potential overflow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 0cfe75c5b011994651a4ca6d74f20aa997bfc69a upstream. In order to avoid the below overflow issue, we should have checked the boundaries in superblock before reaching out to

[PATCH 4.4 025/104] f2fs: clean up with is_valid_blkaddr()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit 7b525dd01365c6764018e374d391c92466be1b7a upstream. - rename is_valid_blkaddr() to is_valid_meta_blkaddr() for readability. - introduce is_valid_blkaddr() for cleanup. No logic

[PATCH 4.4 023/104] f2fs: sanity check on sit entry

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit b2ca374f33bd33fd822eb871876e4888cf79dc97 upstream. syzbot hit the following crash on upstream commit 87ef12027b9b1dd0e0b12cf311fbcb19f9d92539 (Wed Apr 18 19:48:17 2018

[PATCH 4.4 015/104] f2fs: introduce get_checkpoint_version for cleanup

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tiezhu Yang commit fc0065adb202518e25fb929cda7d5887a456f774 upstream. There exists almost same codes when get the value of pre_version and cur_version in function validate_checkpoint, this

[PATCH 4.4 018/104] f2fs: detect wrong layout

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 2040fce83fe17763b07c97c1f691da2bb85e4135 upstream. Previous mkfs.f2fs allows small partition inappropriately, so f2fs should detect that as well. Refer this in f2fs-tools.

[PATCH 4.4 019/104] f2fs: free meta pages if sanity check for ckpt is failed

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit a2125ff7dd1ed3a2a53cdc1f8f9c9cec9cfaa7ab upstream. This fixes missing freeing meta pages in the error case. Tested-by: Eric Biggers Signed-off-by: Jaegeuk Kim

[PATCH 4.4 020/104] f2fs: fix race condition in between free nid allocator/initializer

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit 30a61ddf8117c26ac5b295e1233eaa9629a94ca3 upstream. In below concurrent case, allocated nid can be loaded into free nid cache and be allocated again. Thread A

[PATCH 4.4 021/104] f2fs: return error during fill_super

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit c39a1b348c4fe172729eff77c533dabc3c7cdaa7 upstream. Let's avoid BUG_ON during fill_super, when on-disk was totall corrupted. Reviewed-by: Chao Yu Signed-off-by: Jaegeuk Kim

[PATCH 4.4 016/104] f2fs: put directory inodes before checkpoint in roll-forward recovery

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 9e1e6df412a28cdbbd2909de5c6189eda4a3383d upstream. Before checkpoint, we'd be better drop any inodes. Signed-off-by: Jaegeuk Kim Signed-off-by: Ben Hutchings

[PATCH 4.4 014/104] f2fs: use crc and cp version to determine roll-forward recovery

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit a468f0ef516fda9c7d91bb550d458e853d76955e upstream. Previously, we used cp_version only to detect recoverable dnodes. In order to avoid same garbage cp_version, we needed to

[PATCH 4.4 013/104] f2fs: avoid unneeded loop in build_sit_entries

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit d600af236da51d9e3b90d21a23f95b820bd02e2f upstream. When building each sit entry in cache, firstly, we will load it from sit page, and then check all entries in sit journal, if

[PATCH 4.4 011/104] f2fs: fix to avoid reading out encrypted data in page cache

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit 78682f79447998369a85f12b6437fa8fdbbdca50 upstream. For encrypted inode, if user overwrites data of the inode, f2fs will read encrypted data into page cache, and then do the

[PATCH 4.4 010/104] f2fs: fix inode cache leak

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Chao Yu commit f61cce5b81f91ba336184008b24baec84afbb3dd upstream. When testing f2fs with inline_dentry option, generic/342 reports: VFS: Busy inodes after unmount of dm-0. Self-destruct in 5

[PATCH 3.18 29/52] selinux: fix GPF on invalid policy

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Smalley commit 5b0e7310a2a33c06edc7eb81ffc521af9b2c5610 upstream. levdatum->level can be NULL if we encounter an error while loading the policy during sens_read prior to initializing

[PATCH 3.18 50/52] sysfs: Disable lockdep for driver bind/unbind files

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f4b374332ec0ae9c738ff8ec9bed5cd97ff9adc ] This is the much more correct fix for my earlier attempt at: https://lkml.org/lkml/2018/12/10/118 Short recap: - There's not actually a

[PATCH 3.18 30/52] sctp: allocate sctp_sockaddr_entry with kzalloc

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long commit 400b8b9a2a17918f8ce00786f596f530e7f30d50 upstream. The similar issue as fixed in Commit 4a2eb0c37b47 ("sctp: initialize sin6_flowinfo for ipv6 addrs in sctp_inet6addr_event")

[PATCH 3.18 24/52] omap2fb: Fix stack memory disclosure

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Tsyrklevich commit a01421e4484327fe44f8e126793ed5a48a221e24 upstream. Using [1] for static analysis I found that the OMAPFB_QUERY_PLANE, OMAPFB_GET_COLOR_KEY, OMAPFB_GET_DISPLAY_INFO,

[PATCH 3.18 31/52] block/loop: Use global lock for ioctl() operation.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tetsuo Handa commit 310ca162d779efee8a2dc3731439680f3e9c1e86 upstream. syzbot is reporting NULL pointer dereference [1] which is caused by race condition between ioctl(loop_fd, LOOP_CLR_FD,

[PATCH 3.18 51/52] ocfs2: fix panic due to unrecovered local alloc

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 532e1e54c8140188e192348c790317921cb2dc1c ] mount.ocfs2 ignore the inconsistent error that journal is clean but local alloc is unrecovered. After mount, local alloc not empty, then

[PATCH 3.18 52/52] mm, proc: be more verbose about unstable VMA flags in /proc//smaps

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ] Patch series "THP eligibility reporting via proc". This series of three patches aims at making THP eligibility reporting much more robust

[PATCH 3.18 47/52] dm kcopyd: Fix bug causing workqueue stalls

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d7e6b8dfc7bcb3f4f3a18313581f67486a725b52 ] When using kcopyd to run callbacks through dm_kcopyd_do_callback() or submitting copy jobs with a source size of 0, the jobs are pushed

[PATCH 3.18 28/52] sunrpc: handle ENOMEM in rpcb_getport_async

3.18-stable review patch. If anyone has any objections, please let me know. -- From: J. Bruce Fields commit 81c88b18de1f11f70c97f28ced8d642c00bb3955 upstream. If we ignore the error we'll hit a null dereference a little later. Reported-by:

[PATCH 3.18 49/52] ALSA: bebob: fix model-id of unit for Apogee Ensemble

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 644b2e97405b0b74845e1d3c2b4fe4c34858062b ] This commit fixes hard-coded model-id for an unit of Apogee Ensemble with a correct value. This unit uses DM1500 ASIC produced ArchWave AG

[PATCH 3.18 26/52] media: vivid: set min width/height to a value > 0

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 9729d6d282a6d7ce88e64c9119cecdf79edf4e88 upstream. The capture DV timings capabilities allowed for a minimum width and height of 0. So passing a timings struct with 0

[PATCH 3.18 37/52] pstore/ram: Do not treat empty buffers as valid

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30696378f68a9e3dad6bfe55938b112e72af00c2 ] The ramoops backend currently calls persistent_ram_save_old() even if a buffer is empty. While this appears to work, it is does not seem

[PATCH 3.18 40/52] net: call sk_dst_reset when set SO_DONTROUTE

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0fbe82e628c817e292ff588cd5847fc935e025f2 ] after set SO_DONTROUTE to 1, the IP layer should not route packets if the dest IP address is not in link scope. But if the socket has

[PATCH 3.18 41/52] scsi: target: use consistent left-aligned ASCII INQUIRY data

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0de263577de5d5e052be5f4f93334e63cc8a7f0b ] spc5r17.pdf specifies: 4.3.1 ASCII data field requirements ASCII data fields shall contain only ASCII printable characters (i.e.,

[PATCH 3.18 34/52] r8169: Add support for new Realtek Ethernet

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng [ Upstream commit 36352991835ce99e46b4441dd0eb6980f9a83e8f ] There are two new Realtek Ethernet devices which are re-branded r8168h. Add the IDs to to support them.

[PATCH 3.18 36/52] jffs2: Fix use of uninitialized delayed_work, lockdep breakage

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a788c5272769ddbcdbab297cf386413eeac04463 ] jffs2_sync_fs makes the assumption that if CONFIG_JFFS2_FS_WRITEBUFFER is defined then a write buffer is available and has been

[PATCH 3.18 35/52] MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e4849aff1e169b86c561738daf8ff020e9de1011 ] The Broadcom SiByte BCM1250, BCM1125, and BCM1125H SOCs have an onchip DRAM controller that supports memory amounts of up to 16GiB, and

[PATCH 3.18 21/52] scsi: sd: Fix cache_type_store()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Mironov commit 44759979a49bfd2d20d789add7fa81a21eb1a4ab upstream. Changing of caching mode via /sys/devices/.../scsi_disk/.../cache_type may fail if device responds to MODE SENSE command

[PATCH 3.18 03/52] cifs: Fix potential OOB access of lock element array

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ross Lagerwall commit b9a74cde94957d82003fb9f7ab4777938ca851cd upstream. If maxBuf is small but non-zero, it could result in a zero sized lock element array which we would then try and access

[PATCH 3.18 23/52] Disable MSI also when pcie-octeon.pcie_disable on

3.18-stable review patch. If anyone has any objections, please let me know. -- From: YunQiang Su commit a214720cbf50cd8c3f76bbb9c3f5c283910e9d33 upstream. Octeon has an boot-time option to disable pcie. Since MSI depends on PCI-E, we should also disable MSI also with this

[PATCH 3.18 20/52] Yama: Check for pid death before checking ancestry

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit 9474f4e7cd71a633fa1ef93b7daefd44bbdfd482 upstream. It's possible that a pid has died before we take the rcu lock, in which case we can't walk the ancestry list as it may be

[PATCH 3.18 02/52] CIFS: Do not hide EINTR after sending network packets

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Shilovsky commit ee13919c2e8d1f904e035ad4b4239029a8994131 upstream. Currently we hide EINTR code returned from sock_sendmsg() and return 0 instead. This makes a caller think that we

[PATCH 3.18 00/52] 3.18.133-stable review

This is the start of the stable review cycle for the 3.18.133 release. There are 52 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 Jan 26 19:01:07 UTC 2019. Anything

[PATCH 3.18 06/52] USB: storage: add quirk for SMI SM3350

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Icenowy Zheng commit 0a99cc4b8ee83885ab9f097a3737d1ab28455ac0 upstream. The SMI SM3350 USB-UFS bridge controller cannot handle long sense request correctly and will make the chip refuse to do

[PATCH 3.18 08/52] ACPI: power: Skip duplicate power resource references in _PRx

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 7d7b467cb95bf29597b417d4990160d4ea6d69b9 upstream. Some ACPI tables contain duplicate power resource references like this: Name (_PR0, Package (0x04) // _PR0:

[PATCH 3.18 25/52] media: vivid: fix error handling of kthread_run

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 701f49bc028edb19ffccd101997dd84f0d71e279 upstream. kthread_run returns an error pointer, but elsewhere in the code dev->kthread_vid_cap/out is checked against NULL. If

[PATCH 3.18 04/52] usb: cdc-acm: send ZLP for Telit 3G Intel based modems

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniele Palmas commit 34aabf918717dd14e05051896aaecd3b16b53d95 upstream. Telit 3G Intel based modems require zero packet to be sent if out data size is equal to the endpoint max packet size.

[PATCH 3.18 12/52] tty/ldsem: Wake up readers after timed out down_write()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Safonov commit 231f8fd0cca078bd4396dd7e380db813ac5736e2 upstream. ldsem_down_read() will sleep if there is pending writer in the queue. If the writer times out, readers in the queue

[PATCH 3.18 16/52] packet: Do not leak dev refcounts on error exit

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gunthorpe [ Upstream commit d972f3dce8d161e2142da0ab1ef25df00e2f21a9 ] 'dev' is non NULL when the addr_len check triggers so it must goto a label that does the dev_put otherwise dev

<    4   5   6   7   8   9   10   11   12   13   >