[PATCH 4.4 36/68] locks: use file_inode()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit 6343a2120862f7023006c8091ad95c1f16a32077 upstream. (Another one for the f_path debacle.) ltp fcntl33 testcase caused an Oops in selinux_file_send_sigiotask. The reason

[PATCH 4.4 17/68] arc: unwind: warn only once if DW2_UNWIND is disabled

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Brodkin commit 9bd54517ee86cb164c734f72ea95aeba4804f10b upstream. If CONFIG_ARC_DW2_UNWIND is disabled every time arc_unwind_core() gets called following message gets printed in debug

[PATCH 4.4 37/68] Revert "ecryptfs: forbid opening files without mmap handler"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 78c4e172412de5d0456dc00d2b34050aa0b683b5 upstream. This reverts commit 2f36db71009304b3f0b95afacd8eba1f9f046b87. It fixed a local root exploit but also introduced a

[PATCH 4.4 35/68] power_supply: power_supply_read_temp only if use_cnt > 0

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Rhyland Klein commit 5bc28b93a36e3cb3acc2870fb75cb6ffb182fece upstream. Change power_supply_read_temp() to use power_supply_get_property() so that it will check the use_cnt and ensure it is >

[PATCH 4.4 55/68] can: fix oops caused by wrong rtnl dellink usage

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Hartkopp commit 25e1ed6e64f52a692ba3191c4fde650aab3ecc07 upstream. For 'real' hardware CAN devices the netlink interface is used to set CAN specific communication parameters. Real CAN

[PATCH 4.4 11/68] mm, compaction: prevent VM_BUG_ON when terminating freeing scanner

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David Rientjes commit a46cbf3bc53b6a93fb84a5ffb288c354fa807954 upstream. It's possible to isolate some freepages in a pageblock and then fail split_free_page() due to the low watermark check.

[PATCH 4.4 61/68] i2c: qup: Fix wrong value of index variable

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sricharan R commit d4f56c7773483b8829e89cfc739b7a5a071f6da0 upstream. index gets incremented during check to determine if the messages can be transferred with dma. But not reset after that,

[PATCH 4.4 62/68] i2c: mux: reg: wrong condition checked for of_address_to_resource return value

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lukasz Gemborowski commit 22ebf00eb56fe77922de8138aa9af9996582c2b3 upstream. of_address_to_resource return 0 on successful call but devm_ioremap_resource is called only if it returns non-zero

[PATCH 4.4 50/68] ovl: handle ATTR_KILL*

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit b99c2d913810e56682a538c9f2394d76fca808f8 upstream. Before 4bacc9c9234c ("overlayfs: Make f_path...") file->f_path pointed to the underlying file,

[PATCH 4.4 65/68] net: mvneta: set real interrupt per packet for tx_done

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitri Epshtein commit 06708f81528725148473c0869d6af5f809c6824b upstream. Commit aebea2ba0f74 ("net: mvneta: fix Tx interrupt delay") intended to set coalescing threshold to

[PATCH 4.4 56/68] RDS: fix rds_tcp_init() error path

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vegard Nossum commit 3dad5424adfb346c871847d467f97dcdca64ea97 upstream. If register_pernet_subsys() fails, we shouldn't try to call unregister_pernet_subsys().

[PATCH 4.4 42/68] spi: sunxi: fix transfer timeout

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michal Suchanek commit 719bd6542044efd9b338a53dba1bef45f40ca169 upstream. The trasfer timeout is fixed at 1000 ms. Reading a 4Mbyte flash over 1MHz SPI bus takes way longer

[PATCH 4.4 15/68] pps: do not crash when failed to register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit 368301f2fe4b07e5fb71dba3cc566bc59eb6705f upstream. With this command sequence: modprobe plip modprobe pps_parport rmmod pps_parport the partport_pps

[PATCH 4.4 15/68] pps: do not crash when failed to register

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Slaby commit 368301f2fe4b07e5fb71dba3cc566bc59eb6705f upstream. With this command sequence: modprobe plip modprobe pps_parport rmmod pps_parport the partport_pps modules causes

[PATCH 4.4 56/68] RDS: fix rds_tcp_init() error path

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vegard Nossum commit 3dad5424adfb346c871847d467f97dcdca64ea97 upstream. If register_pernet_subsys() fails, we shouldn't try to call unregister_pernet_subsys(). Fixes: 467fa15356 ("RDS-TCP:

[PATCH 4.4 50/68] ovl: handle ATTR_KILL*

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit b99c2d913810e56682a538c9f2394d76fca808f8 upstream. Before 4bacc9c9234c ("overlayfs: Make f_path...") file->f_path pointed to the underlying file, hence suid/sgid removal

[PATCH 4.4 42/68] spi: sunxi: fix transfer timeout

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Michal Suchanek commit 719bd6542044efd9b338a53dba1bef45f40ca169 upstream. The trasfer timeout is fixed at 1000 ms. Reading a 4Mbyte flash over 1MHz SPI bus takes way longer than that.

[PATCH 4.4 65/68] net: mvneta: set real interrupt per packet for tx_done

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitri Epshtein commit 06708f81528725148473c0869d6af5f809c6824b upstream. Commit aebea2ba0f74 ("net: mvneta: fix Tx interrupt delay") intended to set coalescing threshold to a value

[PATCH 4.4 58/68] ipr: Clear interrupt on croc/crocodile when running with LSI

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian King commit 54e430bbd490e18ab116afa4cd90dcc45787b3df upstream. If we fall back to using LSI on the Croc or Crocodile chip we need to clear the interrupt so we

[PATCH 4.4 58/68] ipr: Clear interrupt on croc/crocodile when running with LSI

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian King commit 54e430bbd490e18ab116afa4cd90dcc45787b3df upstream. If we fall back to using LSI on the Croc or Crocodile chip we need to clear the interrupt so we don't hang the system.

[PATCH 4.4 45/68] platform/chrome: cros_ec_dev - double fetch bug in ioctl

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 096cdc6f52225835ff503f987a0d68ef770bb78e upstream. We verify "u_cmd.outsize" and "u_cmd.insize" but we need to make sure that those values have

[PATCH 4.4 45/68] platform/chrome: cros_ec_dev - double fetch bug in ioctl

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 096cdc6f52225835ff503f987a0d68ef770bb78e upstream. We verify "u_cmd.outsize" and "u_cmd.insize" but we need to make sure that those values have not changed between the two

[PATCH 4.4 28/68] Input: wacom_w8001 - w8001_MAX_LENGTH should be 13

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ping Cheng commit 12afb34400eb2b301f06b2aa3535497d14faee59 upstream. Somehow the patch that added two-finger touch support forgot to update W8001_MAX_LENGTH from 11 to 13.

[PATCH 4.4 47/68] block: fix use-after-free in sys_ioprio_get()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Omar Sandoval commit 8ba8682107ee2ca3347354e018865d8e1967c5f4 upstream. get_task_ioprio() accesses the task->io_context without holding the task lock and thus can race with

[PATCH 4.4 28/68] Input: wacom_w8001 - w8001_MAX_LENGTH should be 13

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ping Cheng commit 12afb34400eb2b301f06b2aa3535497d14faee59 upstream. Somehow the patch that added two-finger touch support forgot to update W8001_MAX_LENGTH from 11 to 13. Signed-off-by: Ping

[PATCH 4.4 47/68] block: fix use-after-free in sys_ioprio_get()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Omar Sandoval commit 8ba8682107ee2ca3347354e018865d8e1967c5f4 upstream. get_task_ioprio() accesses the task->io_context without holding the task lock and thus can race with exit_io_context(),

Re: [PATCH v2] powerpc: Do not make the entire heap executable

On Mon, Aug 8, 2016 at 7:55 AM, Denys Vlasenko wrote: > On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt, > or with a toolchain which defaults to it) look like this: > > [17] .sbss NOBITS 0002aff8 01aff8 14 00 WA 0 0 >

Re: [PATCH v2] powerpc: Do not make the entire heap executable

On Mon, Aug 8, 2016 at 7:55 AM, Denys Vlasenko wrote: > On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt, > or with a toolchain which defaults to it) look like this: > > [17] .sbss NOBITS 0002aff8 01aff8 14 00 WA 0 0 > 4 > [18] .plt

[PATCH 4.4 05/68] dmaengine: at_xdmac: align descriptors on 64 bits

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 4a9723e8df68cfce4048517ee32e37f78854b6fb upstream. Having descriptors aligned on 64 bits allows update CNDA and CUBC in an atomic way.

[PATCH 4.4 00/68] 4.4.17-stable review

This is the start of the stable review cycle for the 4.4.17 release. There are 68 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 Wed Aug 10 18:01:56 UTC 2016. Anything

[PATCH 4.4 02/68] x86/quirks: Apply nvidia_bugs quirk only on root bus

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 447d29d1d3aed839e74c2401ef63387780ac51ed upstream. Since the following commit: 8659c406ade3 ("x86: only scan the root bus in early PCI quirks") ...

[PATCH 4.4 25/68] Input: vmmouse - remove port reservation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 60842ef8128e7bf58c024814cd0dc14319232b6c upstream. The VMWare EFI BIOS will expose port 0x5658 as an ACPI resource. This causes the port to be reserved by

[PATCH 4.4 05/68] dmaengine: at_xdmac: align descriptors on 64 bits

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 4a9723e8df68cfce4048517ee32e37f78854b6fb upstream. Having descriptors aligned on 64 bits allows update CNDA and CUBC in an atomic way. Signed-off-by: Ludovic

[PATCH 4.4 00/68] 4.4.17-stable review

This is the start of the stable review cycle for the 4.4.17 release. There are 68 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 Wed Aug 10 18:01:56 UTC 2016. Anything

[PATCH 4.4 02/68] x86/quirks: Apply nvidia_bugs quirk only on root bus

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Wunner commit 447d29d1d3aed839e74c2401ef63387780ac51ed upstream. Since the following commit: 8659c406ade3 ("x86: only scan the root bus in early PCI quirks") ... early quirks are

[PATCH 4.4 25/68] Input: vmmouse - remove port reservation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sinclair Yeh commit 60842ef8128e7bf58c024814cd0dc14319232b6c upstream. The VMWare EFI BIOS will expose port 0x5658 as an ACPI resource. This causes the port to be reserved by the APCI module

[PATCH 4.4 21/68] xenbus: dont bail early from xenbus_dev_request_and_reply()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich commit 7469be95a487319514adce2304ad2af3553d2fc9 upstream. xenbus_dev_request_and_reply() needs to track whether a transaction is open. For XS_TRANSACTION_START

[PATCH 3.14 18/21] can: fix oops caused by wrong rtnl dellink usage

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Hartkopp commit 25e1ed6e64f52a692ba3191c4fde650aab3ecc07 upstream. For 'real' hardware CAN devices the netlink interface is used to set CAN specific

[PATCH 4.4 26/68] Input: elantech - add more IC body types to the list

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Torokhov commit 226ba707744a51acb4244724e09caacb1d96aed9 upstream. The touchpad in HP Pavilion 14-ab057ca reports it's version as 12 and according to Elan

[PATCH 4.4 07/68] dmaengine: at_xdmac: double FIFO flush needed to compute residue

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 9295c41d77ca93aac79cfca6fa09fa1ca5cab66f upstream. Due to the way CUBC register is updated, a double flush is needed to compute an

[PATCH 3.14 19/21] ipr: Clear interrupt on croc/crocodile when running with LSI

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Brian King commit 54e430bbd490e18ab116afa4cd90dcc45787b3df upstream. If we fall back to using LSI on the Croc or Crocodile chip we need to clear the interrupt so we

[PATCH 4.4 06/68] dmaengine: at_xdmac: fix residue corruption

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 53398f488821c2b5b15291e3debec6ad33f75d3d upstream. An unexpected value of CUBC can lead to a corrupted residue. A more complex sequence is

[PATCH 3.14 20/21] libceph: apply new_state before new_up_client on incrementals

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 930c532869774ebf8af9efe9484c597f896a7d46 upstream. Currently, osd_weight and osd_state fields are updated in the encoding order. This is wrong,

[PATCH 4.4 26/68] Input: elantech - add more IC body types to the list

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Torokhov commit 226ba707744a51acb4244724e09caacb1d96aed9 upstream. The touchpad in HP Pavilion 14-ab057ca reports it's version as 12 and according to Elan both 11 and 12 are valid IC

[PATCH 4.4 07/68] dmaengine: at_xdmac: double FIFO flush needed to compute residue

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 9295c41d77ca93aac79cfca6fa09fa1ca5cab66f upstream. Due to the way CUBC register is updated, a double flush is needed to compute an accurate residue. First flush aim is

[PATCH 3.14 19/21] ipr: Clear interrupt on croc/crocodile when running with LSI

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Brian King commit 54e430bbd490e18ab116afa4cd90dcc45787b3df upstream. If we fall back to using LSI on the Croc or Crocodile chip we need to clear the interrupt so we don't hang the system.

[PATCH 4.4 06/68] dmaengine: at_xdmac: fix residue corruption

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ludovic Desroches commit 53398f488821c2b5b15291e3debec6ad33f75d3d upstream. An unexpected value of CUBC can lead to a corrupted residue. A more complex sequence is needed to detect an

[PATCH 3.14 20/21] libceph: apply new_state before new_up_client on incrementals

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 930c532869774ebf8af9efe9484c597f896a7d46 upstream. Currently, osd_weight and osd_state fields are updated in the encoding order. This is wrong, because an incremental map

[PATCH 4.4 21/68] xenbus: dont bail early from xenbus_dev_request_and_reply()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Beulich commit 7469be95a487319514adce2304ad2af3553d2fc9 upstream. xenbus_dev_request_and_reply() needs to track whether a transaction is open. For XS_TRANSACTION_START messages it calls

[PATCH 3.14 18/21] can: fix oops caused by wrong rtnl dellink usage

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Oliver Hartkopp commit 25e1ed6e64f52a692ba3191c4fde650aab3ecc07 upstream. For 'real' hardware CAN devices the netlink interface is used to set CAN specific communication parameters. Real CAN

[PATCH 3.14 02/21] arc: unwind: warn only once if DW2_UNWIND is disabled

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Brodkin commit 9bd54517ee86cb164c734f72ea95aeba4804f10b upstream. If CONFIG_ARC_DW2_UNWIND is disabled every time arc_unwind_core() gets called following

[PATCH 3.14 02/21] arc: unwind: warn only once if DW2_UNWIND is disabled

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Brodkin commit 9bd54517ee86cb164c734f72ea95aeba4804f10b upstream. If CONFIG_ARC_DW2_UNWIND is disabled every time arc_unwind_core() gets called following message gets printed in debug

[PATCH 3.14 00/21] 3.14.75-stable review

This is the start of the stable review cycle for the 3.14.75 release. There are 21 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 Wed Aug 10 18:01:28 UTC 2016. Anything

[PATCH 3.14 12/21] ARC: use ASL assembler mnemonic

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta commit a6416f57ce57fb390b6ee30b12c01c29032a26af upstream. ARCompact and ARCv2 only have ASL, while binutils used to support LSL as a alias mnemonic. Newer

[PATCH 3.14 00/21] 3.14.75-stable review

This is the start of the stable review cycle for the 3.14.75 release. There are 21 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 Wed Aug 10 18:01:28 UTC 2016. Anything

[PATCH 3.14 12/21] ARC: use ASL assembler mnemonic

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta commit a6416f57ce57fb390b6ee30b12c01c29032a26af upstream. ARCompact and ARCv2 only have ASL, while binutils used to support LSL as a alias mnemonic. Newer binutils (upstream)

[PATCH 3.14 01/21] fs/nilfs2: fix potential underflow in call to crc32_le

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Torsten Hilbrich commit 63d2f95d63396059200c391ca87161897b99e74a upstream. The value `bytes' comes from the filesystem which is about to be mounted. We cannot

[PATCH 3.14 01/21] fs/nilfs2: fix potential underflow in call to crc32_le

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Torsten Hilbrich commit 63d2f95d63396059200c391ca87161897b99e74a upstream. The value `bytes' comes from the filesystem which is about to be mounted. We cannot trust that the value is always

[PATCH 3.14 10/21] Revert "ecryptfs: forbid opening files without mmap handler"

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 78c4e172412de5d0456dc00d2b34050aa0b683b5 upstream. This reverts commit 2f36db71009304b3f0b95afacd8eba1f9f046b87. It fixed a local root exploit but also

[PATCH 3.14 10/21] Revert "ecryptfs: forbid opening files without mmap handler"

3.14-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit 78c4e172412de5d0456dc00d2b34050aa0b683b5 upstream. This reverts commit 2f36db71009304b3f0b95afacd8eba1f9f046b87. It fixed a local root exploit but also introduced a

Re: [PATCH 0/7] de-stage SW_SYNC validation frawework

2016-08-07 Pavel Machek : > On Sun 2016-07-24 15:21:11, Greg Kroah-Hartman wrote: > > On Mon, Jul 18, 2016 at 04:12:45PM -0300, Gustavo Padovan wrote: > > > Hi, > > > > > > Do you think there is time to get this in for 4.8? > > > > No, it was too late on my end, due to travel and

Re: [PATCH 0/7] de-stage SW_SYNC validation frawework

2016-08-07 Pavel Machek : > On Sun 2016-07-24 15:21:11, Greg Kroah-Hartman wrote: > > On Mon, Jul 18, 2016 at 04:12:45PM -0300, Gustavo Padovan wrote: > > > Hi, > > > > > > Do you think there is time to get this in for 4.8? > > > > No, it was too late on my end, due to travel and vacation,

[PATCH v2] drm/bridge: analogix_dp: Ensure the panel is properly prepared/unprepared

Instead of just preparing the panel on bind, actually prepare/unprepare during modeset/disable. The panel must be prepared in order to read hpd status and edid, so we need to keep state around the prepares in order to ensure we don't accidentally turn the panel off at the wrong time.

[PATCH v2] drm/bridge: analogix_dp: Ensure the panel is properly prepared/unprepared

Instead of just preparing the panel on bind, actually prepare/unprepare during modeset/disable. The panel must be prepared in order to read hpd status and edid, so we need to keep state around the prepares in order to ensure we don't accidentally turn the panel off at the wrong time.

[PATCH 1/3] radix-tree: 'slot' can be NULL in radix_tree_next_slot()

There are four cases I can see where we could end up with a NULL 'slot' in radix_tree_next_slot(). Yet radix_tree_next_slot() never actually checks whether 'slot' is NULL. It just happens that for the cases where 'slot' is NULL, some other combination of factors prevents us from dereferencing

Re: [PATCH v6 RESEND 4/7] perf config: Use combined {fore,back}ground colors value instead of each two color

Em Tue, Aug 02, 2016 at 06:20:46PM +0900, Taeung Song escreveu: > To easily set default config values into actual variables for 'colors' config, > it would be better that actual variables for each 'colors' config > also have only one value like 'default_config_item' type. > > If we use combined

[PATCH 1/3] radix-tree: 'slot' can be NULL in radix_tree_next_slot()

There are four cases I can see where we could end up with a NULL 'slot' in radix_tree_next_slot(). Yet radix_tree_next_slot() never actually checks whether 'slot' is NULL. It just happens that for the cases where 'slot' is NULL, some other combination of factors prevents us from dereferencing

Re: [PATCH v6 RESEND 4/7] perf config: Use combined {fore,back}ground colors value instead of each two color

Em Tue, Aug 02, 2016 at 06:20:46PM +0900, Taeung Song escreveu: > To easily set default config values into actual variables for 'colors' config, > it would be better that actual variables for each 'colors' config > also have only one value like 'default_config_item' type. > > If we use combined

[PATCH 2/3] radix-tree tests: add iteration test

There are four cases I can see where we could end up with a NULL 'slot' in radix_tree_next_slot(). This unit test exercises all four of them, making sure that if in the future we have an unsafe path through radix_tree_next_slot(), we'll catch it. Here are details on the four cases: 1)

[PATCH 2/3] radix-tree tests: add iteration test

There are four cases I can see where we could end up with a NULL 'slot' in radix_tree_next_slot(). This unit test exercises all four of them, making sure that if in the future we have an unsafe path through radix_tree_next_slot(), we'll catch it. Here are details on the four cases: 1)

[PATCH 3/3] radix-tree tests: properly initialize mutex

The pthread_mutex_t in regression1.c wasn't being initialized properly. Signed-off-by: Ross Zwisler --- tools/testing/radix-tree/regression1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/radix-tree/regression1.c

[PATCH 3/3] radix-tree tests: properly initialize mutex

The pthread_mutex_t in regression1.c wasn't being initialized properly. Signed-off-by: Ross Zwisler --- tools/testing/radix-tree/regression1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/radix-tree/regression1.c b/tools/testing/radix-tree/regression1.c

Re: [PATCH] x86/hweight: Don't clobber %rdi

On Mon, 8 Aug 2016, Peter Zijlstra wrote: > > > The caller expects %rdi to remain intact, push+pop it make that happen. > > > > Indeed. Applied, > > See also: > > lkml.kernel.org/r/alpine.lnx.2.00.1608081634530.22...@cbobk.fhfr.pm Ville's patch is the proper thing to do; I still think the

Re: [PATCH] x86/hweight: Don't clobber %rdi

On Mon, 8 Aug 2016, Peter Zijlstra wrote: > > > The caller expects %rdi to remain intact, push+pop it make that happen. > > > > Indeed. Applied, > > See also: > > lkml.kernel.org/r/alpine.lnx.2.00.1608081634530.22...@cbobk.fhfr.pm Ville's patch is the proper thing to do; I still think the

Re: [PATCH] x86/hweight: Don't clobber %rdi

On Mon, Aug 08, 2016 at 11:45:58AM -0700, Linus Torvalds wrote: > That would work (although the clobbered registers have a different > syntax than the in/out registers), but it would be wrong, in my > opinion. > > We want the actual POPCNT instruction to be the common case, and that > instruction

Re: [PATCH v2] x86/hweight: fix open-coded versions of 32bit and 64bit hweight calculations

On Mon, 8 Aug 2016, Borislav Petkov wrote: > > Okay, scratch this thread, it's been just covered (and Linus already > > applied it) in > > > > > > https://lkml.kernel.org/r/1470677729-10561-1-git-send-email-ville.syrj...@linux.intel.com > > Can you confirm it fixes the issue on your

Re: [PATCH] x86/hweight: Don't clobber %rdi

On Mon, Aug 08, 2016 at 11:45:58AM -0700, Linus Torvalds wrote: > That would work (although the clobbered registers have a different > syntax than the in/out registers), but it would be wrong, in my > opinion. > > We want the actual POPCNT instruction to be the common case, and that > instruction

Re: [PATCH v2] x86/hweight: fix open-coded versions of 32bit and 64bit hweight calculations

On Mon, 8 Aug 2016, Borislav Petkov wrote: > > Okay, scratch this thread, it's been just covered (and Linus already > > applied it) in > > > > > > https://lkml.kernel.org/r/1470677729-10561-1-git-send-email-ville.syrj...@linux.intel.com > > Can you confirm it fixes the issue on your

Re: [PATCH v2] x86/hweight: fix open-coded versions of 32bit and 64bit hweight calculations

On Mon, Aug 08, 2016 at 08:48:44PM +0200, Jiri Kosina wrote: > Okay, scratch this thread, it's been just covered (and Linus already > applied it) in > > > https://lkml.kernel.org/r/1470677729-10561-1-git-send-email-ville.syrj...@linux.intel.com Can you confirm it fixes the issue on your

Re: [PATCH v2] x86/hweight: fix open-coded versions of 32bit and 64bit hweight calculations

On Mon, Aug 08, 2016 at 08:48:44PM +0200, Jiri Kosina wrote: > Okay, scratch this thread, it's been just covered (and Linus already > applied it) in > > > https://lkml.kernel.org/r/1470677729-10561-1-git-send-email-ville.syrj...@linux.intel.com Can you confirm it fixes the issue on your

Re: [PATCH] perf-stat: avoid skew when reading events

Em Mon, Aug 08, 2016 at 12:16:23PM +0100, Mark Rutland escreveu: > When we don't have a tracee (i.e. we're attaching to a task or CPU), > counters can still be running after our workload finishes, and can still > be running as we read their values. As we read events one-by-one, there > can be

Re: [PATCH] perf-stat: avoid skew when reading events

Em Mon, Aug 08, 2016 at 12:16:23PM +0100, Mark Rutland escreveu: > When we don't have a tracee (i.e. we're attaching to a task or CPU), > counters can still be running after our workload finishes, and can still > be running as we read their values. As we read events one-by-one, there > can be

[GIT PULL] platform-drivers-x86 for 4.8-3

Hi Linus, This is a corrected version of the "platform-drivers-x86 for 4.8-2" which contained previously merged commits. Please ignore the previous pull request. The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc: Linux 4.8-rc1 (2016-08-07 18:18:00 -0700) are

[GIT PULL] platform-drivers-x86 for 4.8-3

Hi Linus, This is a corrected version of the "platform-drivers-x86 for 4.8-2" which contained previously merged commits. Please ignore the previous pull request. The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc: Linux 4.8-rc1 (2016-08-07 18:18:00 -0700) are

Re: [PATCH v2] x86/hweight: fix open-coded versions of 32bit and 64bit hweight calculations

Okay, scratch this thread, it's been just covered (and Linus already applied it) in https://lkml.kernel.org/r/1470677729-10561-1-git-send-email-ville.syrj...@linux.intel.com -- Jiri Kosina SUSE Labs

Re: [PATCH v2] x86/hweight: fix open-coded versions of 32bit and 64bit hweight calculations

Okay, scratch this thread, it's been just covered (and Linus already applied it) in https://lkml.kernel.org/r/1470677729-10561-1-git-send-email-ville.syrj...@linux.intel.com -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/hweight: Don't clobber %rdi

On Mon, Aug 8, 2016 at 11:37 AM, Borislav Petkov wrote: > > Ok, so do you think it would work too if I stated that the input > register gets clobbered: > > asm (ALTERNATIVE("call __sw_hweight64", POPCNT64, X86_FEATURE_POPCNT) > : "="REG_OUT (res) >

Re: [PATCH] x86/hweight: Don't clobber %rdi

On Mon, Aug 8, 2016 at 11:37 AM, Borislav Petkov wrote: > > Ok, so do you think it would work too if I stated that the input > register gets clobbered: > > asm (ALTERNATIVE("call __sw_hweight64", POPCNT64, X86_FEATURE_POPCNT) > : "="REG_OUT (res) >

Re: [GIT PULL] platform-drivers-x86 for 4.8-2

On Mon, Aug 08, 2016 at 09:54:42AM -0700, Darren Hart wrote: > On Fri, Aug 05, 2016 at 11:23:09PM -0400, Linus Torvalds wrote: > > On Fri, Aug 5, 2016 at 6:51 PM, Darren Hart wrote: > > > > > > Minor platform specific event handling updates and a Kconfig cleanup. > > > >

Re: [GIT PULL] platform-drivers-x86 for 4.8-2

On Mon, Aug 08, 2016 at 09:54:42AM -0700, Darren Hart wrote: > On Fri, Aug 05, 2016 at 11:23:09PM -0400, Linus Torvalds wrote: > > On Fri, Aug 5, 2016 at 6:51 PM, Darren Hart wrote: > > > > > > Minor platform specific event handling updates and a Kconfig cleanup. > > > > No. You already sent a

Re: [PATCH] staging: ion: remove __GFP_NOWARN when use low order gfp flags

On 07/29/2016 07:09 PM, Chen Feng wrote: It's useful to show the current memory in detail when alloc failed. And, there may be a lot of high order alloc failed, just show memory when an order 0 alloc failed. Signed-off-by: Chen Feng ---

Re: [PATCH] staging: ion: remove __GFP_NOWARN when use low order gfp flags

On 07/29/2016 07:09 PM, Chen Feng wrote: It's useful to show the current memory in detail when alloc failed. And, there may be a lot of high order alloc failed, just show memory when an order 0 alloc failed. Signed-off-by: Chen Feng --- drivers/staging/android/ion/ion_system_heap.c | 2 +- 1

[PATCH v1 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization

Default implementation expects 6 pages maximum are needed for low page allocations. If KASLR memory randomization is enabled, the worse case of e820 layout would require 12 pages (no large pages). It is due to the PUD level randomization and the variable e820 memory layout. This bug was found

[PATCH v1 2/2] x86/KASLR: Increase BRK pages for KASLR memory randomization

Default implementation expects 6 pages maximum are needed for low page allocations. If KASLR memory randomization is enabled, the worse case of e820 layout would require 12 pages (no large pages). It is due to the PUD level randomization and the variable e820 memory layout. This bug was found

[PATCH v1 1/2] x86/KASLR: Fix physical memory calculation on KASLR memory randomization

Initialize KASLR memory randomization after max_pfn is initialized. Also ensure the size is rounded up. Could have create problems on machines with more than 1Tb of memory on certain random addresses. Signed-off-by: Thomas Garnier --- Based on next-20160805 ---

[PATCH v1 1/2] x86/KASLR: Fix physical memory calculation on KASLR memory randomization

Initialize KASLR memory randomization after max_pfn is initialized. Also ensure the size is rounded up. Could have create problems on machines with more than 1Tb of memory on certain random addresses. Signed-off-by: Thomas Garnier --- Based on next-20160805 --- arch/x86/kernel/setup.c | 4 ++--

bochs_drv.c:undefined reference to `remove_conflicting_framebuffers'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 65ea11ec6a82b1d44aba62b59e9eb20247e57c6e commit: 0b6320dfdfea4c68602fa3b8a8d944bf9e442079 drm/virtio: make fbdev support really optional date: 3 weeks ago config: x86_64-randconfig-s4-08082227 (attached

bochs_drv.c:undefined reference to `remove_conflicting_framebuffers'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 65ea11ec6a82b1d44aba62b59e9eb20247e57c6e commit: 0b6320dfdfea4c68602fa3b8a8d944bf9e442079 drm/virtio: make fbdev support really optional date: 3 weeks ago config: x86_64-randconfig-s4-08082227 (attached

Re: [BUG] Bad page states

On Mon, Aug 08, 2016 at 10:48:45AM -0700, Linus Torvalds wrote: ... > > [ 43.477693] BUG: Bad page state in process S05containers pfn:1ff02a3 > > [ 43.484417] page:ea007fc0a8c0 count:0 mapcount:-511 mapping: > > (null) index:0x0 > > [ 43.492737] flags: 0x1000() > >

Re: [BUG] Bad page states

On Mon, Aug 08, 2016 at 10:48:45AM -0700, Linus Torvalds wrote: ... > > [ 43.477693] BUG: Bad page state in process S05containers pfn:1ff02a3 > > [ 43.484417] page:ea007fc0a8c0 count:0 mapcount:-511 mapping: > > (null) index:0x0 > > [ 43.492737] flags: 0x1000() > >

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