[PATCH 3.2 005/153] netfilter: ebtables: fix erroneous reject of last rule

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 932909d9b28d27e807ff8eecb68c7748f6701628 upstream. The last rule in the blob has next_entry offset that is same as total size. This made "ebtables32 -A OUTPUT -d

Re: [PATCH v14 0/2] Kryo CPU scaling driver

Just like Viresh said, this is fixed in the v15. On May 30, 2018 12:15:35 PM GMT+03:00, Viresh Kumar wrote: >On 30-05-18, 10:08, Rafael J. Wysocki wrote: >> On Fri, May 25, 2018 at 2:07 PM, Ilia Lin >wrote: >> > [v14] >> > * Addressed comment from Sudeep about DT compatible >> > * Added

[PATCH 3.2 043/153] crypto: cryptd - pass through absence of ->setkey()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 841a3ff329713f796a63356fef6e2f72e4a3f6a3 upstream. When the cryptd template is used to wrap an unkeyed hash algorithm, don't install a ->setkey() method to the cryptd

Re: Applied "regulator: bd71837: BD71837 PMIC regulator driver" to the regulator tree

Hello All, On Wed, May 30, 2018 at 12:02:56PM +0100, Mark Brown wrote: > The patch > >regulator: bd71837: BD71837 PMIC regulator driver > > has been applied to the regulator tree at > >https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git Does this mean this single

[PATCH 3.2 042/153] crypto: hash - introduce crypto_hash_alg_has_setkey()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit cd6ed77ad5d223dc6299fb58f62e0f5267f7e2ba upstream. Templates that use an shash spawn can use crypto_shash_alg_has_setkey() to determine whether the underlying algorithm

[PATCH 3.2 045/153] crypto: hash - prevent using keyed hashes without setting key

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 9fa68f620041be04720d0cbfb1bd3ddfc6310b24 upstream. Currently, almost none of the keyed hash algorithms check whether a key has been set before proceeding. Some algorithms

[PATCH 3.2 038/153] scsi: aacraid: remove redundant setting of variable c

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit 91814744646351a470f256fbcb853fb5a7229a9f upstream. A previous commit no longer stores the contents of c, so we now have a situation where c is being updated but the

[PATCH 3.2 039/153] ext4: save error to disk in __ext4_grp_locked_error()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Zhouyi Zhou commit 06f29cc81f0350261f59643a505010531130eea0 upstream. In the function __ext4_grp_locked_error(), __save_error_info() is called to save error info in super block block, but

[PATCH 3.2 016/153] ALSA: seq: More protection for concurrent write and ioctl races

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 7bd80091567789f1c0cb70eb4737aac8bcd2b6b9 upstream. This patch is an attempt for further hardening against races between the concurrent write and ioctls. The previous fix

[PATCH 3.2 034/153] scsi: aacraid: Fix udev inquiry race condition

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Raghava Aditya Renukunta commit f4e8708d3104437fd7716e957f38c265b0c509ef upstream. When udev requests for a devices inquiry string, it might create multiple threads causing a race condition

[PATCH 3.2 030/153] USB: serial: io_edgeport: fix possible sleep-in-atomic

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Jia-Ju Bai commit c7b8f77872c73f69a16528a9eb87afefcccdc18b upstream. According to drivers/usb/serial/io_edgeport.c, the driver may sleep under a spinlock. The function call path is:

[PATCH 3.2 033/153] l2tp: fix missing print session offset info

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Hangbin Liu commit 820da5357572715c6235ba3b3daa2d5b43a1198f upstream. Report offset parameter in L2TP_CMD_SESSION_GET command if it has been configured by userspace Fixes: 309795f4bec

[PATCH 3.2 044/153] crypto: hash - annotate algorithms taking optional key

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit a208fa8f33031b9e0aba44c7d1b7e68eb0cbd29e upstream. We need to consistently enforce that keyed hashes cannot be used without setting the key. To do this we need a reliable

[PATCH 3.2 147/153] bonding: process the err returned by dev_set_allmulti properly in bond_enslave

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Xin Long commit 9f5a90c107741b864398f4ac0014711a8c1d8474 upstream. When dev_set_promiscuity(1) succeeds but dev_set_allmulti(1) fails, dev_set_promiscuity(-1) should be done before going to

[PATCH 3.2 083/153] usb: dwc3: gadget: Set maxpacket size for ep0 IN

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Thinh Nguyen commit 6180026341e852a250e1f97ebdcf71684a3c81b9 upstream. There are 2 control endpoint structures for DWC3. However, the driver only updates the OUT direction control endpoint

Re: Linux 4.17-rc7

Hi Pavel, On 30 May 2018 at 12:17, Pavel Machek wrote: >> The bulk of it is really pretty trivial one-liners, and nothing looks >> particularly scary. Let's see how next week looks, but if nothing really >> happens I suspect we can make do without an rc8. >> >> Shortlog appended as usual. Go out

[PATCH 3.2 077/153] powerpc/numa: Invalidate numa_cpu_lookup_table on cpu remove

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Nathan Fontenot commit 1d9a090783bef19fe8cdec878620d22f05191316 upstream. When DLPAR removing a CPU, the unmapping of the cpu from a node in unmap_cpu_from_node() should also invalidate the

[PATCH 3.2 071/153] Btrfs: fix extent state leak from tree log

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Liu Bo commit 55237a5f2431a72435e3ed39e4306e973c0446b7 upstream. It's possible that btrfs_sync_log() bails out after one of the two btrfs_write_marked_extents() which convert extent state's

[PATCH 3.2 075/153] MIPS: TXx9: use IS_BUILTIN() for CONFIG_LEDS_CLASS

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Matt Redfearn commit 0cde5b44a30f1daaef1c34e08191239dc63271c4 upstream. When commit b27311e1cace ("MIPS: TXx9: Add RBTX4939 board support") added board support for the RBTX4939, it added a

Re: [PATCH] mm: Change return type to vm_fault_t

On Wed, May 30, 2018 at 09:10:47AM +0530, Souptick Joarder wrote: > On Tue, May 29, 2018 at 11:04 PM, Matthew Wilcox wrote: > > I see: > > > > mm/gup.c:817:15: warning: invalid assignment: |= > > mm/gup.c:817:15:left side has type int > > mm/gup.c:817:15:right side has type restricted

[PATCH 3.2 078/153] netlink: ensure to loop over all netns in genlmsg_multicast_allns()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Nicolas Dichtel commit cb9f7a9a5c96a773bbc9c70660dc600cfff82f82 upstream. Nowadays, nlmsg_multicast() returns only 0 or -ESRCH but this was not the case when commit 134e63756d5f was pushed.

[PATCH 3.2 079/153] netlink: avoid a double skb free in genlmsg_mcast()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Nicolas Dichtel commit 02a2385f37a7c6594c9d89b64c4a1451276f08eb upstream. nlmsg_multicast() consumes always the skb, thus the original skb must be freed only when this function is called with

[PATCH 3.2 080/153] 9p/trans_virtio: discard zero-length reply

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Greg Kurz commit 26d99834f89e76514076d9cd06f61e56e6a509b8 upstream. When a 9p request is successfully flushed, the server is expected to just mark it as used without sending a 9p reply (ie,

[PATCH 3.2 026/153] perf/hwbp: Simplify the perf-hwbp code, fix documentation

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit f67b15037a7a50c57f72e69a6d59941ad90a0f0f upstream. Annoyingly, modify_user_hw_breakpoint() unnecessarily complicates the modification of a breakpoint - simplify it and

[PATCH v2 1/2] drm/blend: Add per-plane pixel blend mode property

Pixel blend modes represent the alpha blending equation selection, describing how the pixels from the current plane are composited with the background. Add a pixel_blend_mode to drm_plane_state and a blend_mode_property to drm_plane, and related support functions. Defines three blend modes in

Re: [PATCH 6/6] mfd: da9063: Add DA9063L support

On 05/29/2018 09:46 AM, Lee Jones wrote: > On Thu, 24 May 2018, Marek Vasut wrote: >> On 05/24/2018 02:32 PM, Steve Twiss wrote: >>> On 24 May 2018 @ 12:49 Steve Twiss wrote: > > [...] > >>> static const struct regmap_irq da9063l_irqs[] = { >>> /* DA9063 event A register */ >>>

[PATCH 3.2 050/153] hrtimer: Ensure POSIX compliance (relative CLOCK_REALTIME hrtimers)

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Anna-Maria Gleixner commit 48d0c9becc7f3c66874c100c126459a9da0fdced upstream. The POSIX specification defines that relative CLOCK_REALTIME timers are not affected by clock modifications.

[PATCH 3.2 107/153] batman-adv: fix packet checksum in receive path

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Matthias Schiffer commit abd6360591d3f8259f41c34e31ac4826dfe621b8 upstream. eth_type_trans() internally calls skb_pull(), which does not adjust the skb checksum; skb_postpull_rcsum() is

[PATCH 3.2 111/153] tty: make n_tty_read() always abort if hangup is in progress

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 28b0f8a6962a24ed21737578f3b1b07424635c9e upstream. A tty is hung up by __tty_hangup() setting file->f_op to hung_up_tty_fops, which is skipped on ttys whose write operation

[PATCH 3.2 099/153] libata: Apply NOLPM quirk to Crucial MX100 512GB SSDs

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 9c7be59fc519af9081c46c48f06f2b8fadf55ad8 upstream. Various people have reported the Crucial MX100 512GB model not working with LPM set to min_power. I've now received a

[PATCH 3.2 114/153] e1000e: Fix check_for_link return value with autoneg off

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Benjamin Poirier commit 4e7dc08e57c95673d2edaba8983c3de4dd1f65f5 upstream. When autoneg is off, the .check_for_link callback functions clear the get_link_status flag and systematically return

[PATCH 3.2 125/153] netfilter: bridge: ebt_among: add missing match size checks

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit c4585a2823edf4d1326da44d1524ecbfda26bb37 upstream. ebt_among is special, it has a dynamic match size and is exempt from the central size checks. Therefore it must

[PATCH 3.2 112/153] serial: sh-sci: prevent lockup on full TTY buffers

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Ulrich Hecht commit 7842055bfce4bf0170d0f61df8b2add8399697be upstream. When the TTY buffers fill up to the configured maximum, a system lockup occurs: [ 598.820128] INFO: rcu_preempt

[PATCH 3.2 102/153] libata: disable LPM for Crucial BX100 SSD 500GB drive

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit b17e5729a630d8326a48ec34ef02e6b4464a6aef upstream. After Laptop Mode Tools starts to use min_power for LPM, a user found out Crucial BX100 SSD can't get mounted. Crucial

Re: [PATCH] staging: lustre: libcfs: add parens around macros args

On Tue, May 22, 2018 at 04:34:39PM +0300, Ivan Bornyakov wrote: > One may call 'CFS_FAIL_TIMEOUT(id, secs + 5);' and get unexpected result > after macro substitution, viz., 'secs + 5' will turn into > 'secs + 5 * 1000' > We actually do that in ptl_send_rpc() as well so this is a real bug. It's

[PATCH] ARM: debug: Add Iproc UART3 debug addresses

From: Clément Peron Broadcom Iproc SoCs typically use the UART3 for debug/console, provide a known good location for that. Signed-off-by: Clément Peron --- arch/arm/Kconfig.debug | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/arch/arm/Kconfig.debug

Re: [PATCH 3/3] ARM: imx: remove i.MX6SLL support in i.MX6SL cpu idle driver

Hi Anson, On Wed, May 30, 2018 at 4:12 AM, Anson Huang wrote: > i.MX6SLL supports ARM power off in cpu idle, better to reuse > i.MX6SX cpu idle driver instead of i.MX6SL which does NOT > support ARM power off. > > Signed-off-by: Anson Huang > --- > arch/arm/mach-imx/cpuidle-imx6sl.c | 7

Re: [PATCH] ARM: debug: Add Iproc UART3 debug addresses

Hi Clément, On Wed, May 30, 2018 at 02:29:22PM +0200, Clément Péron wrote: > From: Clément Peron > > Broadcom Iproc SoCs typically use the UART3 for > debug/console, provide a known good location for that. > > Signed-off-by: Clément Peron > --- > arch/arm/Kconfig.debug | 12 +++- > 1

Re: [PATCH v2 1/6] soc: qcom: rpmpd: Add a powerdomain driver to model corners

[...] >>> + >>> +static DEFINE_MUTEX(rpmpd_lock); >>> + >>> +/* msm8996 RPM powerdomains */ >>> +DEFINE_RPMPD_CORN_SMPA(msm8996, vddcx, vddcx_ao, 1); >>> +DEFINE_RPMPD_CORN_SMPA(msm8996, vddmx, vddmx_ao, 2); >>> +DEFINE_RPMPD_CORN_LDOA(msm8996, vddsscx, 26); >>> + >>>

[PATCH v2 1/8] gnss: add GNSS receiver subsystem

Add a new subsystem for GNSS (e.g. GPS) receivers. While GNSS receivers are typically accessed using a UART interface they often also support other I/O interfaces such as I2C, SPI and USB, while yet other devices use iomem or even some form of remote-processor messaging (rpmsg). The new GNSS

[PATCH v2 7/8] gnss: add driver for sirfstar-based receivers

Add driver for serial-connected SiRFstar-based GNSS receivers. These devices typically boot into hibernate mode from which they can be woken using a pulse on the ON_OFF input pin. Once active, a pulse on the same ON_OFF pin is used to put the device back into hibernate mode. The current state can

Re: [PATCH] tpm: separate cmd_ready/go_idle from runtime_pm

On Wed, May 23, 2018 at 01:48:17PM +, Winkler, Tomas wrote: > > > On Tue, May 22, 2018 at 09:27:46AM +, Winkler, Tomas wrote: > > > > > > > > On Wed, May 16, 2018 at 10:46:00PM +0300, Tomas Winkler wrote: > > > > > New wrappers are added tpm_cmd_ready() and tpm_go_idle() > > wrappers > >

Re: [PATCH v5 04/10] sched/dl: add dl_rq utilization tracking

On 25-May 15:12, Vincent Guittot wrote: > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > index fb18bcc..967e873 100644 > --- a/kernel/sched/fair.c > +++ b/kernel/sched/fair.c > @@ -7290,11 +7290,14 @@ static inline bool cfs_rq_has_blocked(struct cfs_rq > *cfs_rq) > return false; >

Re: [PATCH 1/1] device core: Add flag to autoremove device link on supplier unbind

On 5/30/2018 11:57 AM, Vivek Gautam wrote: When using the device links without the consumers or suppliers maintaining pointers to these links, a flag can help in autoremoving the links on supplier driver unbind. We remove these links only when the supplier's link to its consumers has gone in

Re: [PATCH V3] cpufreq: reinitialize new policy min/max when writing scaling_(max|min)_freq

On Wed, May 30, 2018 at 9:56 AM, Kevin Wangtao wrote: > consider such situation, current user_policy.min is 100, > current user_policy.max is 120, in cpufreq_set_policy, > other driver may update policy.min to 120, policy.max to > 130. After that, If we input "echo 130 >

[PATCH 3.2 058/153] CDC-ACM: apply quirk for card reader

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit df1cc78a52491f71d8170d513d0f6f114faa1bda upstream. This devices drops random bytes from messages if you talk to it too fast. Signed-off-by: Oliver Neukum Signed-off-by:

[PATCH 3.2 062/153] cifs: Fix missing put_xid in cifs_file_strict_mmap

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Matthew Wilcox commit f04a703c3d613845ae3141bfaf223489de8ab3eb upstream. If cifs_zap_mapping() returned an error, we would return without putting the xid that we got earlier. Restructure

[PATCH 3.2 059/153] scsi: fas216: fix sense buffer initialization

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 96d5eaa9bb74d299508d811d865c2c41b38b0301 upstream. While testing with the ARM specific memset() macro removed, I ran into a compiler warning that shows an old bug:

[PATCH 3.2 054/153] drm/ttm: Don't add swapped BOs to swap-LRU list

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Felix Kuehling commit fd5002d6a3c602664b07668a24df4ef7a43bf078 upstream. A BO that's already swapped would be added back to the swap-LRU list for example if its validation failed under high

[PATCH 3.2 051/153] USB: cdc-acm: Do not log urb submission errors on disconnect

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit f0386c083c2ce85284dc0b419d7b89c8e567c09f upstream. When disconnected sometimes the cdc-acm driver logs errors like these: [20278.039417] cdc_acm 2-2:2.1: urb 9 failed

[PATCH 3.2 065/153] media: cxusb, dib0700: ignore XC2028_I2C_FLUSH

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 9893b905e743ded332575ca04486bd586c0772f7 upstream. The XC2028_I2C_FLUSH only needs to be implemented on a few devices. Others can safely ignore it. That prevents

[PATCH 3.2 144/153] tty: vt: fix up tabstops properly

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit f1869a890cdedb92a3fab969db5d0fd982850273 upstream. Tabs on a console with long lines do not wrap properly, so correctly account for the line length when computing the

[PATCH 3.2 048/153] console/dummy: leave .con_font_get set to NULL

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Nicolas Pitre commit 724ba8b30b044aa0d94b1cd374fc15806cdd6f18 upstream. When this method is set, the caller expects struct console_font fields to be properly initialized when it returns.

[PATCH 3.2 049/153] ASoC: au1x: Fix timeout tests in au1xac97c_ac97_read()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 123af9043e93cb6f235207d260d50f832cdb5439 upstream. The loop timeout doesn't work because it's a post op and ends with "tmo" set to -1. I changed it from a post-op to a

[PATCH 3.2 052/153] dm thin: fix documentation relative to low water mark threshold

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: mulhern commit 9b28a1102efc75d81298198166ead87d643a29ce upstream. Fixes: 1. The use of "exceeds" when the opposite of exceeds, falls below, was meant. 2. Properly speaking, a table can not

Re: [PATCH v2 0/6] mfd/regulator/clk: bd71837: ROHM BD71837 PMIC driver

On Tue, 29 May 2018, Matti Vaittinen wrote: > Hello, > > On Tue, May 29, 2018 at 08:39:58AM +0100, Lee Jones wrote: > > On Mon, 28 May 2018, Matti Vaittinen wrote: > > > > > Patch series adding support for ROHM BD71837 PMIC. > > FYI, this patch-set is going to be difficult to manage since it

[PATCH 3.2 061/153] HID: roccat: prevent an out of bounds read in kovaplus_profile_activated()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 7ad81482cad67cbe1ec808490d1ddfc420c42008 upstream. We get the "new_profile_index" value from the mouse device when we're handling raw events. Smatch taints it as

[PATCH 3.2 025/153] perf/hwpb: Invoke __perf_event_disable() if interrupts are already disabled

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: "K.Prasad" commit 500ad2d8b01390c98bc6dce068bccfa9534b8212 upstream. While debugging a warning message on PowerPC while using hardware breakpoints, it was discovered that when

[PATCH 3.2 066/153] scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Tyrel Datwyler commit c39813652700f3df552b6557530f1e5f782dbe2f upstream. The fcp_rsp_info structure as defined in the FC spec has an initial 3 bytes reserved field. The ibmvfc driver

Re: [PATCH 1/2] staging: wilc1000: fix some endianness sparse warnings

On Tue, May 29, 2018 at 09:11:43PM +0200, Thibaut Robert wrote: > diff --git a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c > b/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c > index e248702ee519..745bf5ca2622 100644 > --- a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c > +++

[PATCH 3.2 067/153] netfilter: ipt_CLUSTERIP: fix out-of-bounds accesses in clusterip_tg_check()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit 1a38956cce5eabd7b74f94bab70265e4df83165e upstream. Commit 136e92bbec0a switched local_nodes from an array to a bitmask but did not add proper bounds checks. As the result

[PATCH 3.2 069/153] mm: pin address_space before dereferencing it while isolating an LRU page

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit 69d763fc6d3aee787a3e8c8c35092b4f4960fa5d upstream. Minchan Kim asked the following question -- what locks protects address_space destroying when race happens between inode

Re: Linux 4.17-rc7

Hi! > So this week wasn't as calm as the previous weeks have been, but despite > that I suspect this is the last rc. > > This week we had the whole "spectre v4" thing, and yes, the fallout from > that shows up as part of the patch and commit log. But it's not actually > dominant: the patch is

[PATCH 3.2 020/153] x86/MCE: Serialize sysfs changes

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Seunghun Han commit b3b7c4795ccab5be71f080774c45bbbcc75c2aaf upstream. The check_interval file in /sys/devices/system/machinecheck/machinecheck directory is a global timer value for MCE

Re: [PATCH 6/6] mfd: da9063: Add DA9063L support

On 05/24/2018 07:30 PM, Steve Twiss wrote: > On 24 May 2018 15:51 Marek Vasut wrote: > > Hi Marek, > >> To: Steve Twiss ; linux-kernel@vger.kernel.org >> Cc: Marek Vasut ; Geert Uytterhoeven >> ; Lee Jones ; Mark Brown >> ; Wolfram Sang ; >> linux-renesas-...@vger.kernel.org >> Subject: Re:

[PATCH 3.2 040/153] ext4: correct documentation for grpid mount option

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Ernesto A. Fernández commit 9f0372488cc9243018a812e8cfbf27de650b187b upstream. The grpid option is currently described as being the same as nogrpid. Signed-off-by: Ernesto A. Fernández

[PATCH 3.2 035/153] pktcdvd: Fix pkt_setup_dev() error path

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 5a0ec388ef0f6e33841aeb810d7fa23f049ec4cd upstream. Commit 523e1d399ce0 ("block: make gendisk hold a reference to its queue") modified add_disk() and disk_release() but

[PATCH 3.2 036/153] signal/sh: Ensure si_signo is initialized in do_divide_error

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" commit 0e88bb002a9b2ee8cc3cc9478ce2dc126f849696 upstream. Set si_signo. Cc: Yoshinori Sato Cc: Rich Felker Cc: Paul Mundt Cc: linux...@vger.kernel.org Fixes:

[PATCH 3.2 029/153] ASoC: nuc900: Fix a loop timeout test

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 65a12b3aafed5fc59f4ce41b22b752b1729e6701 upstream. We should be finishing the loop with timeout set to zero but because this is a post-op we finish with timeout == -1.

[PATCH 3.2 027/153] media: cpia2: Fix a couple off by one bugs

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit d5ac225c7d64c9c3ef821239edc035634e594ec9 upstream. The cam->buffers[] array has cam->num_frames elements so the > needs to be changed to >= to avoid going beyond the end

[PATCH 3.2 022/153] x86/traps: Enable DEBUG_STACK after cpu_init() for TRAP_DB/BP

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Wang Nan commit b4d8327024637cb2a1f7910dcb5d0ad7a096f473 upstream. Before this patch early_trap_init() installs DEBUG_STACK for X86_TRAP_BP and X86_TRAP_DB. However, DEBUG_STACK doesn't work

[PATCH 3.2 047/153] mn10300/misalignment: Use SIGSEGV SEGV_MAPERR to report a failed user copy

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" commit 6ac1dc736b323011a55ecd1fc5897c24c4f77cbd upstream. Setting si_code to 0 is the same a setting si_code to SI_USER which is definitely not correct. With si_code set

[PATCH 3.2 092/153] netfilter: nat: cope with negative port range

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni commit db57ccf0f2f4624b4c4758379f8165277504fbd7 upstream. syzbot reported a division by 0 bug in the netfilter nat code: divide error: [#1] SMP KASAN Dumping ftrace buffer:

[PATCH 3.2 084/153] bridge: check brport attr show in brport_show

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Xin Long commit 1b12580af1d0677c3c3a19e35bfe5d59b03f737f upstream. Now br_sysfs_if file flush doesn't have attr show. To read it will cause kernel panic after users chmod u+r this file.

[PATCH 3.2 087/153] xfrm_user: uncoditionally validate esn replay attribute struct

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit d97ca5d714a5334aecadadf696875da40f1fbf3e upstream. The sanity test added in ecd7918745234 can be bypassed, validation only occurs if XFRM_STATE_ESN flag is set, but

[PATCH 3.2 120/153] USB: usbmon: remove assignment from IS_ERR argument

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Julia Lawall commit 46c236dc7d1212d7417e6fb0317f91c44c719322 upstream. The semantic patch that makes this change is as follows: (http://coccinelle.lip6.fr/) // @@ expression e1,e2;

[PATCH 3.2 096/153] Add delay-init quirk for Corsair K70 RGB keyboards

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Jack Stocker commit 7a1646d922577b5b48c0d222e03831141664bb59 upstream. Following on from this patch: https://lkml.org/lkml/2017/11/3/516, Corsair K70 RGB keyboards also require the DELAY_INIT

[PATCH 3.2 119/153] x86/MCE: Save microcode revision in machine check records

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Tony Luck commit fa94d0c6e0f3431523f5701084d799c77c7d4a4f upstream. Updating microcode used to be relatively rare. Now that it has become more common we should save the microcode version in a

[PATCH 3.2 104/153] regulatory: add NUL to request alpha2

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 657308f73e674e86b60509a430a46e569bf02846 upstream. Similar to the ancient commit a5fe8e7695dc ("regulatory: add NUL to alpha2"), add another byte to alpha2 in the request

[PATCH 3.2 115/153] usb: quirks: add control message delay for 1b1c:1b20

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Danilo Krummrich commit cb88a0588717ba6c756cb5972d75766b273a6817 upstream. Corsair Strafe RGB keyboard does not respond to usb control messages sometimes and hence generates timeouts. Commit

[PATCH 3.2 118/153] RDMA/ucma: Check that user doesn't overflow QP state

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit a5880b84430316e3e1c1f5d23aa32ec6000cc717 upstream. The QP state is limited and declared in enum ib_qp_state, but ucma user was able to supply any possible (u32) value.

[PATCH 3.2 122/153] xhci: Fix front USB ports on ASUS PRIME B350M-A

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 191edc5e2e515aab1075a3f0ef23599e80be5f59 upstream. When a USB device gets plugged on ASUS PRIME B350M-A's front ports, the xHC stops working: [ 549.114587] xhci_hcd

[PATCH 3.2 123/153] ALSA: seq: Fix possible UAF in snd_seq_check_queue()

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit d0f833065221cbfcbadf19fd4102bcfa9330006a upstream. Although we've covered the races between concurrent write() and ioctl() in the previous patch series, there is still a

Re: [PATCH V2] platform/x86: intel_pmc_core: Add CNP SLPS0 debug registers

On Wed, May 30, 2018 at 03:53:12AM -0700, David E. Box wrote: Hi Dave, > Hi Rajneesh, > > On Mon, 2018-05-28 at 12:30 +0530, Rajneesh Bhardwaj wrote: > > On Thu, May 24, 2018 at 06:10:56PM -0700, David E. Box wrote: > > > > Thanks for sending this, Dave. Few comments below. > > > > > Adds

[PATCH 3.2 117/153] RDMA/ucma: Limit possible option size

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky commit 6a21dfc0d0db7b7e0acedce67ca533a6eb19283c upstream. Users of ucma are supposed to provide size of option level, in most paths it is supposed to be equal to u8 or u16,

[PATCH 3.2 003/153] ocfs2: subsystem.su_mutex is required while accessing the item->ci_parent

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: alex chen commit 853bc26a7ea39e354b9f8889ae7ad1492ffa28d2 upstream. The subsystem.su_mutex is required while accessing the item->ci_parent, otherwise, NULL pointer dereference to the

[PATCH 3.2 004/153] netfilter: ebtables: CONFIG_COMPAT: don't trust userland offsets

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit b71812168571fa55e44cdd0254471331b9c4c4c6 upstream. We need to make sure the offsets are not out of range of the total size. Also check that they are in ascending

[PATCH 3.2 009/153] ext4: fix bitmap position validation

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Lukas Czerner commit 22be37acce25d66ecf6403fc8f44df9c5ded2372 upstream. Currently in ext4_valid_block_bitmap() we expect the bitmap to be positioned anywhere between 0 and s_blocksize

[PATCH 3.2 008/153] ext4: add validity checks for bitmap block numbers

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit 7dac4a1726a9c64a517d595c40e95e2d0d135f6f upstream. An privileged attacker can cause a crash by mounting a crafted ext4 image which triggers a out-of-bounds read in the

[PATCH 3.2 018/153] hugetlbfs: check for pgoff value overflow

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Mike Kravetz commit 63489f8e821144000e0bdca7e65a8d1cc23a7ee7 upstream. A vma with vm_pgoff large enough to overflow a loff_t type when converted to a byte offset can be passed via the

[PATCH 3.2 006/153] ext4: fail ext4_iget for root directory if unallocated

3.2.102-rc1 review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit 8e4b5eae5decd9dfe5a4ee369c22028f90ab4c44 upstream. If the root directory has an i_links_count of zero, then when the file system is mounted, then when ext4_fill_super()

Re: [PATCH v5 04/10] sched/dl: add dl_rq utilization tracking

On 30 May 2018 at 12:50, Patrick Bellasi wrote: > On 25-May 15:12, Vincent Guittot wrote: >> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c >> index fb18bcc..967e873 100644 >> --- a/kernel/sched/fair.c >> +++ b/kernel/sched/fair.c >> @@ -7290,11 +7290,14 @@ static inline bool

Re: [PATCH 0/2] mm->owner to mm->memcg fixes

On Wed 23-05-18 14:46:43, Eric W. Biederman wrote: [...] > As two processes sharing an mm is useless and highly unlikely there is > no need to handle this case well, it just needs to be handled well > enough to prevent an indefinite loop. So when css_tryget_online fails > just treat the mm as

[PATCH v4 1/5] ARM: imx: remove inexistant EPIT timer init

From: Clément Peron i.MX EPIT timer has been removed but not the init function declaration. Signed-off-by: Clément Peron Reviewed-by: Fabio Estevam --- arch/arm/mach-imx/common.h | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm/mach-imx/common.h b/arch/arm/mach-imx/common.h index

Re: [PATCH 0/2] mm->owner to mm->memcg fixes

On Thu 24-05-18 14:16:35, Andrew Morton wrote: > On Thu, 24 May 2018 13:10:02 +0200 Michal Hocko wrote: > > > I would really prefer and appreciate a repost with all the fixes folded > > in. > > [1/2] Thanks Andrew and sorry it took so long! This seems to be missing the fix for the issue I've

[PATCH v2 02/10] drm/exynos: move pm_runtime_get_sync() to exynos_dsi_init()

In order to allow bridge drivers to use DSI transfers in their pre_enable callbacks, pm_runtime_get_sync() should be performed before exynos_dsi_enable(). DSIM_STATE_ENABLED flag now should not guard from calling dsi_host_transfer() before enabling. Signed-off-by: Maciej Purski ---

Re: [PATCH] IB/mad: Use ID allocator routines to allocate agent number

On 05/30/2018 10:02 AM, jackm wrote: On Tue, 29 May 2018 10:40:32 -0600 Jason Gunthorpe wrote: On Tue, May 29, 2018 at 06:16:14PM +0200, Håkon Bugge wrote: On 29 May 2018, at 17:49, Jason Gunthorpe wrote: On Tue, May 29, 2018 at 09:38:08AM +0200, Hans Westgaard Ry wrote: The agent

[PATCH v2] zswap: re-check zswap_is_full after do zswap_shrink

The '/sys/../zswap/stored_pages:' keep raising in zswap test with "zswap.max_pool_percent=0" parameter. But theoretically, it should not compress or store pages any more since there is no space in compressed pool. Reproduce steps: 1. Boot kernel with "zswap.enabled=1" 2. Set the

Re: [PATCH v4 0/6] mfd/regulator/clk: bd71837: ROHM BD71837 PMIC driver

On Wed, May 30, 2018 at 12:05:12PM +0300, Matti Vaittinen wrote: > Other 4 can be used on PWM or PFM switching mode. When PWM is used > voltages can be changed without disabling regulator. On PFM this should > not be done. These latter 4 regulators can be forced to PWM mode via > control bit in

Re: [PATCH v1] i2c: tegra: Remove suspend-resume

On Tuesday 29 May 2018 11:36 PM, Wolfram Sang wrote: Our I2C driver is based on the interrupt. So we have converted the suspend/resume to suspend_noirq and reseume_noirq so that we will not allow the transfer when system interrupt disabled in downstream.

<    2   3   4   5   6   7   8   9   10   11   >