[PATCH 4.9 165/177] IB/core: Fix calculation of maximum RoCE MTU

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Parav Pandit [ Upstream commit 99260132fde7bddc6e0132ce53da94d1c9ccabcb ] The original code only took into consideration the largest header possible after the IB_BTH_BYTES. This was incorrect

Re: [v2 PATCH -tip 3/6] net: sctp: Add SCTP ACK tracking trace event

On Mon, 18 Dec 2017 17:12:15 +0900 Masami Hiramatsu wrote: > Add SCTP ACK tracking trace event to trace the changes of SCTP > association state in response to incoming packets. > It is used for debugging SCTP congestion control algorithms, > and will replace sctp_probe module. > > Note that this

Re: [PATCH V2] hyper-v: use GFP_KERNEL for hv_context.hv_numa_map

On Mon, 18 Dec 2017 17:02:52 +0800 Jia-Ju Bai wrote: > The kzalloc function is called with GFP_ATOMIC. > But according to driver call graph, it is not in atomic context, > namely no spinlock is held nor in an interrupt handler. > > This GFP_ATOMIC is unnecessary, and replace with GFP_KERNEL. >

[PATCH 4.9 162/177] pinctrl: adi2: Fix Kconfig build problem

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij [ Upstream commit 1c363531dd814dc4fe10865722bf6b0f72ce4673 ] The build robot is complaining on Blackfin: drivers/pinctrl/pinctrl-adi2.c: In function 'port_setup': >> drivers/pin

[PATCH 4.9 153/177] xfs: fix incorrect extent state in xfs_bmap_add_extent_unwritten_real

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig [ Upstream commit 5e422f5e4fd71d18bc6b851eeb3864477b3d842e ] There was one spot in xfs_bmap_add_extent_unwritten_real that didn't use the passed in new extent state but alway

[PATCH 4.9 140/177] ASoC: rsnd: rsnd_ssi_run_mods() needs to care ssi_parent_mod

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kuninori Morimoto [ Upstream commit 21781e87881f9c420871b1d1f3f29d4cd7bffb10 ] SSI parent mod might be NULL. ssi_parent_mod() needs to care about it. Otherwise, it uses negative shift. This pa

[PATCH 4.9 134/177] mm: Handle 0 flags in _calc_vm_trans() macro

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara [ Upstream commit 592e254502041f953e84d091eae2c68cba04c10b ] _calc_vm_trans() does not handle the situation when some of the passed flags are 0 (which can happen if these VM flags do

[PATCH 4.9 115/177] dmaengine: ti-dma-crossbar: Correct am335x/am43xx mux value type

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi [ Upstream commit 288e7560e4d3e259aa28f8f58a8dfe63627a1bf6 ] The used 0x1f mask is only valid for am335x family of SoC, different family using this type of crossbar might have d

[PATCH 4.9 126/177] iscsi-target: fix memory leak in lio_target_tiqn_addtpg()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: tangwenji [ Upstream commit 12d5a43b2dffb6cd28062b4e19024f7982393288 ] tpg must free when call core_tpg_register() return fail Signed-off-by: tangwenji Signed-off-by: Nicholas Bellinger Sig

[PATCH 4.9 104/177] target: fix ALUA transition timeout handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Christie [ Upstream commit d7175373f2745ed4abe5b388d5aabd06304f801e ] The implicit transition time tells initiators the min time to wait before timing out a transition. We currently sched

[PATCH 4.9 132/177] arm-ccn: perf: Prevent module unload while PMU is in use

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose [ Upstream commit c7f5828bf77dcbd61d51f4736c1d5aa35663fbb4 ] When the PMU driver is built as a module, the perf expects the pmu->module to be valid, so that the driver is prev

[PATCH 4.9 114/177] ASoC: Intel: Skylake: Fix uuid_module memory leak in failure case

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Pankaj Bharadiya [ Upstream commit f8e066521192c7debe59127d90abbe2773577e25 ] In the loop that adds the uuid_module to the uuid_list list, allocated memory is not properly freed in the error p

[PATCH 4.9 129/177] badblocks: fix wrong return value in badblocks_set if badblocks are disabled

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Liu Bo [ Upstream commit 39b4954c0a1556f8f7f1fdcf59a227117fcd8a0b ] MD's rdev_set_badblocks() expects that badblocks_set() returns 1 if badblocks are disabled, otherwise, rdev_set_badblocks()

[PATCH 4.9 131/177] xfs: truncate pagecache before writeback in xfs_setattr_size()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eryu Guan [ Upstream commit 350976ae21873b0d36584ea005076356431b8f79 ] On truncate down, if new size is not block size aligned, we zero the rest of block to avoid exposing stale data to user,

[PATCH 4.9 123/177] platform/x86: intel_punit_ipc: Fix resource ioremap warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kuppuswamy Sathyanarayanan [ Upstream commit 6cc8cbbc8868033f279b63e98b26b75eaa0006ab ] For PUNIT device, ISPDRIVER_IPC and GTDDRIVER_IPC resources are not mandatory. So when PMC IPC driver cr

[PATCH 4.9 128/177] target/file: Do not return error for UNMAP if length is zero

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiang Yi [ Upstream commit 594e25e73440863981032d76c9b1e33409ceff6e ] The function fd_execute_unmap() in target_core_file.c calles ret = file->f_op->fallocate(file, mode, pos, len); Some fil

[PATCH 4.9 127/177] target:fix condition return in core_pr_dump_initiator_port()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: tangwenji [ Upstream commit 24528f089d0a444070aa4f715ace537e8d6bf168 ] When is pr_reg->isid_present_at_reg is false,this function should return. This fixes a regression originally introduced

[PATCH 4.9 125/177] target/iscsi: Fix a race condition in iscsit_add_reject_from_cmd()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche [ Upstream commit cfe2b621bb18d86e93271febf8c6e37622da2d14 ] Avoid that cmd->se_cmd.se_tfo is read after a command has already been freed. Signed-off-by: Bart Van Assche Cc:

[PATCH 4.9 124/177] platform/x86: sony-laptop: Fix error handling in sony_nc_setup_rfkill()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Markus Elfring [ Upstream commit f6c8a317ab208aee223776327c06f23342492d54 ] Source code review for a specific software refactoring showed the need for another correction because the error code

[PATCH 4.9 083/177] afs: Prevent callback expiry timer overflow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tina Ruchandani [ Upstream commit 56e714312e7dbd6bb83b2f78d3ec19a404c7649f ] get_seconds() returns real wall-clock seconds. On 32-bit systems this value will overflow in year 2038 and beyond.

[PATCH 4.9 082/177] afs: Migrate vlocation fields to 64-bit

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tina Ruchandani [ Upstream commit 8a79790bf0b7da216627ffb85f52cfb4adbf1e4e ] get_seconds() returns real wall-clock seconds. On 32-bit systems this value will overflow in year 2038 and beyond.

[PATCH 4.9 081/177] afs: Flush outstanding writes when an fd is closed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 58fed94dfb17e89556b5705f20f90e5b2971b6a1 ] Flush outstanding writes in afs when an fd is closed. This is what NFS and CIFS do. Reported-by: Marc Dionne Signe

[PATCH 4.9 112/177] video: fbdev: au1200fb: Return an error code if a memory allocation fails

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 8cae353e6b01ac3f18097f631cdbceb5ff28c7f3 ] 'ret' is known to be 0 at this point. In case of memory allocation error in 'framebuffer_alloc()', return -ENOME

[PATCH 4.9 080/177] afs: Deal with an empty callback array

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marc Dionne [ Upstream commit bcd89270d93b7edebb5de5e5e7dca1a77a33496e ] Servers may send a callback array that is the same size as the FID array, or an empty array. If the callback count is

[PATCH 4.9 111/177] video: fbdev: au1200fb: Release some resources if a memory allocation fails

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit 451f130602619a17c8883dd0b71b11624faffd51 ] We should go through the error handling code instead of returning -ENOMEM directly. Signed-off-by: Christophe J

[PATCH 4.9 079/177] afs: Adjust mode bits processing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marc Dionne [ Upstream commit 627f46943ff90bcc32ddeb675d881c043c6fa2ae ] Mode bits for an afs file should not be enforced in the usual way. For files, the absence of user bits can restrict fi

[PATCH 4.9 078/177] afs: Populate group ID from vnode status

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marc Dionne [ Upstream commit 6186f0788b31f44affceeedc7b48eb10faea120d ] The group was hard coded to GLOBAL_ROOT_GID; use the group ID that was received from the server. Signed-off-by: Marc D

Re: [GIT PULL 0/5] perf/urgent fixes

> > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-urgent-for-mingo-4.15-20171218 > > for you to fetch changes up to 38ab834165924bf86fe7ee67bb5dbea56240b03f: > > x86/asm: Allow again usi

Re: BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit

From: Santosh Shilimkar Date: Mon, 18 Dec 2017 08:28:05 -0800 > On 12/18/2017 12:43 AM, syzbot wrote: >> Hello, >> syzkaller hit the following crash on >> 6084b576dca2e898f5c101baef151f7bfdbb606d >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master >> compiler: gcc (GCC) 7.

Re: [PATCH 1/3] dt-bindings: chosen: Add clocksource and clockevent selection

* Grygorii Strashko [171216 01:59]: > On 12/13/2017 12:53 PM, Alexandre Belloni wrote: > > +/ { > > + chosen { > > + linux,clocksource { > > + timer = <&timer0>; > > + }; > > + > > + linux,clockevent { > > + timer = <&timer1>; > >

[PATCH 4.9 109/177] fbdev: controlfb: Add missing modes to fix out of bounds access

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven [ Upstream commit ac831a379d34109451b3c41a44a20ee10ecb615f ] Dan's static analysis says: drivers/video/fbdev/controlfb.c:560 control_setup() error: buffer overflow

RE: [Intel-wired-lan] v4.15-rc2 on thinkpad x60: ethernet stopped working

Jeff was out sick last week. It might take him a bit to catch up. I'll remind him when I see him next (which I hope is soon). Todd Fujinaka Software Application Engineer Datacenter Engineering Group Intel Corporation todd.fujin...@intel.com -Original Message- From: Intel-wired-lan [mailt

[PATCH 4.9 106/177] Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dou Liyang [ Upstream commit c962cff17dfa11f4a8227ac16de2b28aea3312e4 ] Revert: dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when booting") The mapping of "cpuid <-> node

[PATCH 4.9 077/177] afs: Fix missing put_page()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 29c8bbbd6e21daa0997d1c3ee886b897ee7ad652 ] In afs_writepages_region(), inside the loop where we find dirty pages to deal with, one of the if-statements is missi

Re: jsm_tty: Deletion of a null pointer check in two functions?

> So, what do you prefer? Send it yourself, I became concerned that “my patch” would not get picked up because of Greg's communication settings (for my initial messages when they do not get resent by other contributors). > or want me to send it with your sign-off too? (since was your idea). I w

[PATCH] [media] dvb-frontends: remove self assignments

These were leftover from: commit 469ffe083665 ("[media] tda18271c2dd: Remove the CHK_ERROR macro") and commit 58d5eaec9f87 ("[media] drxd: Don't use a macro for CHK_ERROR ...") that programmatically removed the CHK_ERROR macro, which left behind a few self assignments that Clang warns about. These

[PATCH 4.9 102/177] btrfs: add missing memset while reading compressed inline extents

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Zygo Blaxell [ Upstream commit e1699d2d7bf6e6cce3e1baff19f9dd4595a58664 ] This is a story about 4 distinct (and very old) btrfs bugs. Commit c8b978188c ("Btrfs: Add zlib compression support")

[PATCH 4.9 100/177] efi/esrt: Cleanup bad memory map log messages

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Drake [ Upstream commit 822f5845f710e57d7e2df1fd1ee00d6e19d334fe ] The Intel Compute Stick STCK1A8LFC and Weibu F3C platforms both log 2 error messages during boot: efi: requested m

[PATCH 4.9 098/177] tty: fix data race in tty_ldisc_ref_wait()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov [ Upstream commit a4a3e061149f09c075f108b6f1cf04d9739a6bc2 ] tty_ldisc_ref_wait() checks tty->ldisc under tty->ldisc_sem. But if ldisc==NULL it releases them sem and reloads tty-

Re: BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit

On 12/18/2017 9:12 AM, David Miller wrote: From: Santosh Shilimkar Date: Mon, 18 Dec 2017 08:28:05 -0800 On 12/18/2017 12:43 AM, syzbot wrote: Hello, syzkaller hit the following crash on 6084b576dca2e898f5c101baef151f7bfdbb606d git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

[PATCH 4.9 094/177] net/mlx4_core: Avoid delays during VF driver device shutdown

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit 4cbe4dac82e423ecc9a0ba46af24a860853259f4 ] Some Hypervisors detach VFs from VMs by instantly causing an FLR event to be generated for a VF. In the mlx4 case

[PATCH 4.9 096/177] rxrpc: Ignore BUSY packets on old calls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 4d4a6ac73e7466c2085c307fac41f74ce4568a45 ] If we receive a BUSY packet for a call we think we've just completed, the packet is handed off to the connection proc

[PATCH 4.9 097/177] tty: dont panic on OOM in tty_set_ldisc()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov [ Upstream commit 5362544bebe85071188dd9e479b5a5040841c895 ] If tty_ldisc_open() fails in tty_set_ldisc(), it tries to go back to the old discipline or N_TTY. But that can fail a

[PATCH 4.9 076/177] drm/radeon: reinstate oland workaround for sclk

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher [ Upstream commit 66822d815ae61ecb2d9dba9031517e8a8476969d ] Higher sclks seem to be unstable on some boards. bug: https://bugs.freedesktop.org/show_bug.cgi?id=100222 Signed-off

[PATCH 4.9 093/177] nvmet-rdma: Fix a possible uninitialized variable dereference

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sagi Grimberg [ Upstream commit b25634e2a051bef4b2524b11adddfbfa6448f6cd ] When handling a new recv command, we grab a new rsp resource and check for the queue state being live. In case the qu

[PATCH RFC 1/7] KVM: x86: rename HV_X64_MSR_APIC_ASSIST_PAGE to HV_X64_MSR_VP_ASSIST_PAGE

From: Ladi Prosek The assist page has been used only for the paravirtual EOI so far, hence the "APIC" in the MSR name. Renaming to match the Hyper-V TLFS where it's called "Virtual VP Assist MSR". Signed-off-by: Ladi Prosek Signed-off-by: Vitaly Kuznetsov --- arch/x86/include/uapi/asm/hyperv.

[PATCH RFC 0/7] KVM: nVMX: enlightened VMCS initial implementation

The original author of these patches does no longer work at Red Hat, I agreed to take this over and send upstream. Here is his original description: "Makes KVM implement the enlightened VMCS feature per Hyper-V TLFS 5.0b. I've measured about %5 improvement in cost of a nested VM exit (Hyper-V enab

[PATCH RFC 4/7] KVM: hyperv: define VP assist page structure and add helpers

From: Ladi Prosek Structure layout is specified in Hyper-V TLFS 5.0b. The state related to the VP assist page is still managed by the LAPIC code in the pv_eoi field. Signed-off-by: Ladi Prosek Signed-off-by: Vitaly Kuznetsov --- arch/x86/include/uapi/asm/hyperv.h | 10 ++ arch/x86/kv

[PATCH RFC 7/7] KVM: nVMX: implement enlightened VMPTRLD

From: Ladi Prosek Per Hyper-V TLFS 5.0b: "The L1 hypervisor may choose to use enlightened VMCSs by writing 1 to the corresponding field in the VP assist page (see section 7.8.7). Another field in the VP assist page controls the currently active enlightened VMCS. Each enlightened VMCS is exactly

[PATCH RFC 6/7] KVM: nVMX: add enlightened VMCS state

From: Ladi Prosek Adds two bool fields and implements copy_enlightened_to_vmcs12() and copy_enlightened_to_vmcs12(). Unlike shadow VMCS, enlightened VMCS is para-virtual and active only if the nested guest explicitly enables it. The pattern repeating itself a few times throughout this patch:

[PATCH RFC 3/7] KVM: nVMX: add I/O exit ECX, ESI, EDI, EIP vmcs12 fields

From: Ladi Prosek These non-synthetic VMCS fields were not supported by KVM thus far. The layout is according to Hyper-V TLFS 5.0b, the physical encoding according to the Intel SDM. Signed-off-by: Ladi Prosek Signed-off-by: Vitaly Kuznetsov --- arch/x86/include/asm/vmx.h | 4 arch/x86/kv

[PATCH RFC 5/7] KVM: nVMX: add KVM_CAP_HYPERV_ENLIGHTENED_VMCS capability

From: Ladi Prosek Enlightened VMCS is opt-in. The current version does not contain all fields supported by nested VMX so we must not advertise the corresponding VMX features if enlightened VMCS is enabled. Userspace is given the enlightened VMCS version supported by KVM as part of enabling KVM_C

[tip:perf/urgent] tools arch s390: Do not include header files from the kernel sources

Commit-ID: 10b9baa701d5023897f70a4acb3bf0235da3dc4f Gitweb: https://git.kernel.org/tip/10b9baa701d5023897f70a4acb3bf0235da3dc4f Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 28 Nov 2017 11:08:41 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 18 Dec 2017 11:56:13 -0300 t

Re: [BUG] Build error for 4.15-rc3 kernel caused by patch "kbuild: Add a cache for generated variables"

On 12/18/17 7:50 AM, Masahiro Yamada wrote: 2017-12-18 23:56 GMT+09:00 Masahiro Yamada : 2017-12-17 7:35 GMT+09:00 Yang Shi : Hi folks, I just upgraded gcc to 6.4 on my centos 7 machine by Arnd's suggestion. But, I ran into the below compile error with 4.15-rc3 kernel: In file included from

Re: NFS: 82ms wakeup latency 4.14-rc4

On Mon, 2017-12-18 at 18:00 +0100, Mike Galbraith wrote: > On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote: > > > > Like I say, I don't really understand the issues here, so it's more a > > question than an objection (I don't know any reason a > > cond_resched() would be bad there.)

[PATCH RFC 2/7] KVM: nVMX: modify vmcs12 fields to match Hyper-V enlightened VMCS

From: Ladi Prosek Reorders existing fields and adds fields specific to Hyper-V. The layout now matches Hyper-V TLFS 5.0b 16.11.2 Enlightened VMCS. Fields used by KVM but missing from Hyper-V are placed in the second half of the VMCS page to minimize the chances they will clash with future enligh

Re: [BUG] Build error for 4.15-rc3 kernel caused by patch "kbuild: Add a cache for generated variables"

Hi, On Mon, Dec 18, 2017 at 7:50 AM, Masahiro Yamada wrote: > 2017-12-18 23:56 GMT+09:00 Masahiro Yamada : >> 2017-12-17 7:35 GMT+09:00 Yang Shi : >>> Hi folks, >>> >>> I just upgraded gcc to 6.4 on my centos 7 machine by Arnd's suggestion. But, >>> I ran into the below compile error with 4.15-rc

[PATCH 4.9 092/177] nvmet: confirm sq percpu has scheduled and switched to atomic

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sagi Grimberg [ Upstream commit d11ea004a458b982e19b188c386e25a9b66ec446 ] percpu_ref_kill is not enough to prevent subsequent percpu_ref_tryget_live from failing. Hence call perfcpu_ref_kill_

[PATCH 4.9 090/177] afs: Fix abort on signal while waiting for call completion

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 954cd6dc02a65065aecb7150962c0870c5b0e322 ] Fix the way in which a call that's in progress and being waited for is aborted in the case that EINTR is detected. W

[tip:perf/urgent] perf tools: Use shell function for perl cflags retrieval

Commit-ID: 5cfee7a357f60675cae32b494bb2096d7203efd3 Gitweb: https://git.kernel.org/tip/5cfee7a357f60675cae32b494bb2096d7203efd3 Author: Jiri Olsa AuthorDate: Wed, 8 Nov 2017 11:27:37 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 18 Dec 2017 11:54:08 -0300 perf tools: Use s

[tip:perf/urgent] perf tools: Fix up build in hardened environments

Commit-ID: 61fb26a6a23c0f1a07a0f8a11b54bafb1ac2398b Gitweb: https://git.kernel.org/tip/61fb26a6a23c0f1a07a0f8a11b54bafb1ac2398b Author: Jiri Olsa AuthorDate: Mon, 4 Dec 2017 12:23:08 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 18 Dec 2017 11:54:08 -0300 perf tools: Fix u

Re: [PATCH 4.9 124/177] platform/x86: sony-laptop: Fix error handling in sony_nc_setup_rfkill()

On Mon, 2017-12-18 at 16:49 +0100, Greg Kroah-Hartman wrote: > 4.9-stable review patch. If anyone has any objections, please let me know. I am _very_ suspicious of any -stable patch by Markus Elfring. Are you sure this is necessary and useful for -stable? Does this actually fix something or does

[tip:perf/urgent] perf jvmti: Generate correct debug information for inlined code

Commit-ID: ca58d7e64bdfc54f7dfe46713c1e2acc68d7522d Gitweb: https://git.kernel.org/tip/ca58d7e64bdfc54f7dfe46713c1e2acc68d7522d Author: Ben Gainey AuthorDate: Wed, 22 Nov 2017 18:25:41 -0600 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 18 Dec 2017 11:54:08 -0300 perf jvmti: Gen

Re: [PATCH v3 19/19] fs: handle inode->i_version more efficiently

On Mon, 2017-12-18 at 17:34 +0100, Jan Kara wrote: > On Mon 18-12-17 10:11:56, Jeff Layton wrote: > > static inline bool > > inode_maybe_inc_iversion(struct inode *inode, bool force) > > { > > - atomic64_t *ivp = (atomic64_t *)&inode->i_version; > > + u64 cur, old, new; > > > > - atomic6

Re: [rds-devel] BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit

> From: Santosh Shilimkar > Date: Mon, 18 Dec 2017 08:28:05 -0800 : > > Looks like another one tripping on empty transport. Mostly below > > should > > address it but we will test it if it does. that was my first thought, but it cannot be the case here: rds_sendmsg etc itself would have bombed

Re: [BUG] Build error for 4.15-rc3 kernel caused by patch "kbuild: Add a cache for generated variables"

On 12/18/17 9:17 AM, Doug Anderson wrote: Hi, On Mon, Dec 18, 2017 at 7:50 AM, Masahiro Yamada wrote: 2017-12-18 23:56 GMT+09:00 Masahiro Yamada : 2017-12-17 7:35 GMT+09:00 Yang Shi : Hi folks, I just upgraded gcc to 6.4 on my centos 7 machine by Arnd's suggestion. But, I ran into the bel

[PATCH 4.9 089/177] afs: Fix afs_kill_pages()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 7286a35e893176169b09715096a4aca557e2ccd2 ] Fix afs_kill_pages() in two ways: (1) If a writeback has been partially flushed, then if we try and kill the p

[PATCH 4.9 088/177] afs: Fix page leak in afs_write_begin()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 6d06b0d25209c80e99c1e89700f1e09694a3766b ] afs_write_begin() leaks a ref and a lock on a page if afs_fill_page() fails. Fix the leak by unlocking and releasing

Re: tps65090-charger: Delete an error message for a failed memory allocation in two functions

Hi, On Sat, Dec 16, 2017 at 09:47:34PM +0100, SF Markus Elfring wrote: > >> I am still waiting for possibilities to improve also the corresponding > >> reference documentation somehow as you know it already. > > > > If you require someone else to update the documentation to be able to > > explain

Re: NFS: 82ms wakeup latency 4.14-rc4

On Mon, 2017-12-18 at 18:00 +0100, Mike Galbraith wrote: > On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote: > > > > Like I say, I don't really understand the issues here, so it's more > > a > > question than an objection (I don't know any reason a > > cond_resched() would be bad ther

[PATCH 4.9 087/177] afs: Populate and use client modification time

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marc Dionne [ Upstream commit ab94f5d0dd6fd82e7eeca5e7c8096eaea0a0261f ] The inode timestamps should be set from the client time in the status received from the server, rather than the server

Re: [PATCH v3 16/19] fs: only set S_VERSION when updating times if necessary

On Mon, 2017-12-18 at 17:07 +0100, Jan Kara wrote: > On Mon 18-12-17 10:11:53, Jeff Layton wrote: > > From: Jeff Layton > > > > We only really need to update i_version if someone has queried for it > > since we last incremented it. By doing that, we can avoid having to > > update the inode if the

[PATCH 4.9 085/177] afs: Invalid op ID should abort with RXGEN_OPCODE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 1157f153f37a8586765034470e4f00a4a6c4ce6f ] When we are given an invalid operation ID, we should abort that with RXGEN_OPCODE rather than RX_INVALID_OPERATION.

[PATCH 4.9 035/177] net: bcmgenet: power down internal phy if open or resume fails

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Doug Berger [ Upstream commit 7627409cc4970e8c8b9de6945ad86a575290a94e ] Since the internal PHY is powered up during the open and resume functions it should be powered back down if the functio

[tip:perf/urgent] x86/asm: Allow again using asm.h when building for the 'bpf' clang target

Commit-ID: ca26cffa4e4aaeb09bb9e308f95c7835cb149248 Gitweb: https://git.kernel.org/tip/ca26cffa4e4aaeb09bb9e308f95c7835cb149248 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 4 Dec 2017 13:08:47 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 18 Dec 2017 11:56:22 -0300 x8

[PATCH 4.9 041/177] iommu/io-pgtable-arm-v7s: Check for leaf entry before dereferencing it

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Oleksandr Tyshchenko [ Upstream commit a03849e7210277fa212779b7cd9c30e1ab6194b2 ] Do a check for already installed leaf entry at the current level before dereferencing it in order to avoid wal

[PATCH 4.9 044/177] NFSD: fix nfsd_reset_versions for NFSv4.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown [ Upstream commit 800a938f0bf9130c8256116649c0cc5806bfb2fd ] If you write "-2 -3 -4" to the "versions" file, it will notice that no versions are enabled, and nfsd_reset_versions() is

[PATCH 4.9 072/177] sched/deadline: Make sure the replenishment timer fires in the next period

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Bristot de Oliveira [ Upstream commit 5ac69d37784b237707a7b15d199cdb6c6fdb6780 ] Currently, the replenishment timer is set to fire at the deadline of a task. Although that works for imp

[PATCH 4.9 071/177] sched/deadline: Add missing update_rq_clock() in dl_task_timer()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wanpeng Li [ Upstream commit dcc3b5ffe1b32771c9a22e2c916fb94c4fcf5b79 ] The following warning can be triggered by hot-unplugging the CPU on which an active SCHED_DEADLINE task is running on:

Re: NFS: 82ms wakeup latency 4.14-rc4

On Mon, 2017-12-18 at 17:24 +, Trond Myklebust wrote: > On Mon, 2017-12-18 at 18:00 +0100, Mike Galbraith wrote: > > On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote: > > > > > > Like I say, I don't really understand the issues here, so it's more > > > a > > > question than an objectio

Re: NFS: 82ms wakeup latency 4.14-rc4

On Mon, Dec 18, 2017 at 06:17:36PM +0100, Mike Galbraith wrote: > On Mon, 2017-12-18 at 18:00 +0100, Mike Galbraith wrote: > > On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote: > > > > > > Like I say, I don't really understand the issues here, so it's more a > > > question than an objectio

[PATCH 4.9 040/177] net/mlx5: Dont save PCI state when PCI error is detected

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Jurgens [ Upstream commit 5d47f6c89d568ab61712d8c40676fbb020b68752 ] When a PCI error is detected the PCI state could be corrupt, don't save it in that flow. Save the state after initia

[PATCH 4.9 073/177] sched/deadline: Throttle a constrained deadline task activated after the deadline

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Bristot de Oliveira [ Upstream commit df8eac8cafce7d086be3bd5cf5a838fa37594dfb ] During the activation, CBS checks if it can reuse the current task's runtime and period. If the deadline

[PATCH 4.9 070/177] iwlwifi: mvm: cleanup pending frames in DQA mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon [ Upstream commit 9a3fcf912ef7f5c6e18f9af6875dd13f7311f7aa ] When a station is asleep, the fw will set it as "asleep". All queues that are used only by one station will be stopped

[PATCH] Staging: Pi433: Bugfix for wrong argument for sizeof() in TX thread

sizeof(array) != sizeof(pointer to array) Fixes: "staging: pi433: reduce stack size in tx thread" Signed-off-by: Marcus Wolf --- drivers/staging/pi433/pi433_if.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging

Re: [Xen-devel] [PATCH V3 1/2] Drivers/PCI: Export pcie_has_flr() interface

On 12/18/2017 6:26 AM, Christoph Hellwig wrote: On Fri, Dec 15, 2017 at 12:18:02PM -0600, Bjorn Helgaas wrote: I think Christoph volunteered to do some restructuring, but I don't know his timeframe. If you can, I would probably wait for that because there's so much overlap here. I'll have so

[PATCH 4.9 066/177] scsi: hpsa: do not timeout reset operations

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Don Brace [ Upstream commit 2ef2884980873081a4edae92f9d88dd580c85f6e ] Resets can take longer than DEFAULT_TIMEOUT. Reviewed-by: Scott Benesh Reviewed-by: Scott Teel Reviewed-by: Tomas Henz

Re: [PATCH] MAINTAINERS: Move all MTD related branches to a single repo

On Mon, 18 Dec 2017 15:55:35 + David Woodhouse wrote: > On Mon, 2017-12-18 at 16:49 +0100, Boris Brezillon wrote: > > > > In the meantime, we should try to keep both l2-mtd and linux-mtd synced > > (that means pushing the xxx/next branches on both l2-mtd and mtd-next). > > You could make

[PATCH 4.9 064/177] scsi: hpsa: update check for logical volume status

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Don Brace [ Upstream commit 85b29008d8af6d94a0723aaa8d93cfb6e041158b ] - Add in a new case for volume offline. Resolves internal testing bug for multilun array management. - Return correc

[PATCH 4.9 065/177] scsi: hpsa: limit outstanding rescans

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Don Brace [ Upstream commit 87b9e6aa87d9411f1059aa245c0c79976bc557ac ] Avoid rescan storms. No need to queue another if one is pending. Reviewed-by: Scott Benesh Reviewed-by: Scott Teel Rev

[PATCH 4.9 063/177] ASoC: rcar: clear DE bit only in PDMACHCR when it stops

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kuninori Morimoto [ Upstream commit 62a10498afb27370ec6018e9d802b74850fd8d9a ] R-Car datasheet indicates "Clear DE in PDMACHCR" for transfer stop, but current code clears all bits in PDMACHCR.

[PATCH 4.9 060/177] drm: amd: remove broken include path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 655d9ca9ac075da1ef2a45012ba48a39f6eb1f58 ] The AMD ACP driver adds "-I../acp -I../acp/include" to the gcc command line, which makes no sense, since these are ev

[PATCH 4.9 061/177] intel_th: pci: Add Gemini Lake support

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin [ Upstream commit 340837f985c2cb87ca0868d4aa9ce42b0fab3a21 ] This adds Intel(R) Trace Hub PCI ID for Gemini Lake SOC. Signed-off-by: Alexander Shishkin Signed-off-by: Sash

[PATCH 4.9 059/177] qed: Fix interrupt flags on Rx LL2

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ram Amrani [ Upstream commit 1df2adedcce17ad4a39fba74f0e2b611f797fe10 ] Before iterating over the the LL2 Rx ring, the ring's spinlock is taken via spin_lock_irqsave(). The actual processing o

[PATCH 4.9 058/177] qed: Fix mapping leak on LL2 rx flow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Mintz, Yuval" [ Upstream commit 752ecb2da11124a948567076b60767dc8034cfa5 ] When receiving an Rx LL2 packet, qed fails to unmap the previous buffer. Fixes: 0a7fb11c23c0 ("qed: Add Light L2 su

[PATCH 4.9 037/177] net: bcmgenet: Power up the internal PHY before probing the MII

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Doug Berger [ Upstream commit 6be371b053dc86f11465cc1abce2e99bda0a0574 ] When using the internal PHY it must be powered up when the MII is probed or the PHY will not be detected. Since the PH

[PATCH 4.9 054/177] net: Resend IGMP memberships upon peer notification.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Yasevich [ Upstream commit 37c343b4f4e70e9dc328ab04903c0ec8d154c1a4 ] When we notify peers of potential changes, it's also good to update IGMP memberships. For example, during VM migrat

[PATCH 4.9 056/177] mlxsw: reg: Fix SPVMLR max record count

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Pirko [ Upstream commit e9093b1183bbac462d2caef3eac165778c0b1bf1 ] The num_rec field is 8 bit, so the maximal count number is 255. This fixes vlans learning not being enabled for wider ra

Re: tps65090-charger: Delete an error message for a failed memory allocation in two functions

>> But it seems that we are stuck with specific software aspects. >> How would you like to see remaining open issues to be resolved >> there anyhow? > > FYI: I will drop this and (without any further notice) all future > patches from you, that do no follow the documented process in > Documentation

[PATCH] [media] dvb-frontends: remove extraneous parens

Fixes 2 warnings from Clang about extra parentheses in a conditional, that might have been meant as assignment. Signed-off-by: Nick Desaulniers --- drivers/media/dvb-frontends/drx39xyj/drxj.c | 2 +- drivers/media/dvb-frontends/drxk_hard.c | 2 +- 2 files changed, 2 insertions(+), 2 deletion

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