[PATCH 3.18 30/42] ftrace: Fix selftest goto location on error

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 46320a6acc4fb58f04bcf78c4c942cc43b20f986 upstream. In the second iteration of trace_selftest_ops(), the error goto label is wrong in the

[PATCH 3.18 28/42] scsi: sg: fixup infoleak when using SG_GET_REQUEST_TABLE

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 3e0097499839e0fe3af380410eababe5a47c4cf9 upstream. When calling SG_GET_REQUEST_TABLE ioctl only a half-filled table is returned; the remaining part will

[PATCH 3.18 30/42] ftrace: Fix selftest goto location on error

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 46320a6acc4fb58f04bcf78c4c942cc43b20f986 upstream. In the second iteration of trace_selftest_ops(), the error goto label is wrong in the case where

[PATCH 3.18 28/42] scsi: sg: fixup infoleak when using SG_GET_REQUEST_TABLE

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 3e0097499839e0fe3af380410eababe5a47c4cf9 upstream. When calling SG_GET_REQUEST_TABLE ioctl only a half-filled table is returned; the remaining part will then contain

[PATCH 3.18 03/42] Revert "net: phy: Correctly process PHY_HALTED in phy_stop_machine()"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit ebc8254aeae34226d0bc8fda309fd9790d4dccfe ] This reverts commit 7ad813f208533cebfcc32d3d7474dc1677d1b09a ("net: phy: Correctly process

[PATCH 3.18 04/42] tcp: initialize rcv_mss to TCP_MIN_MSS instead of 0

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Wei Wang [ Upstream commit 499350a5a6e7512d9ed369ed63a4244b6536f4f8 ] When tcp_disconnect() is called, inet_csk_delack_init() sets icsk->icsk_ack.rcv_mss to 0. This could

[PATCH 3.18 29/42] scsi: qla2xxx: Fix an integer overflow in sysfs code

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit e6f77540c067b48dee10f1e33678415bfcc89017 upstream. The value of "size" comes from the user. When we add "start + size" it could lead to an

[PATCH 3.18 31/42] tracing: Apply trace_clock changes to instance max buffer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Baohong Liu commit 170b3b1050e28d1ba0700e262f0899ffa4fccc52 upstream. Currently trace_clock timestamps are applied to both regular and max buffers only for global

[PATCH 3.18 03/42] Revert "net: phy: Correctly process PHY_HALTED in phy_stop_machine()"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit ebc8254aeae34226d0bc8fda309fd9790d4dccfe ] This reverts commit 7ad813f208533cebfcc32d3d7474dc1677d1b09a ("net: phy: Correctly process PHY_HALTED in

[PATCH 3.18 04/42] tcp: initialize rcv_mss to TCP_MIN_MSS instead of 0

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Wei Wang [ Upstream commit 499350a5a6e7512d9ed369ed63a4244b6536f4f8 ] When tcp_disconnect() is called, inet_csk_delack_init() sets icsk->icsk_ack.rcv_mss to 0. This could potentially cause

[PATCH 3.18 29/42] scsi: qla2xxx: Fix an integer overflow in sysfs code

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit e6f77540c067b48dee10f1e33678415bfcc89017 upstream. The value of "size" comes from the user. When we add "start + size" it could lead to an integer overflow bug. It

[PATCH 3.18 31/42] tracing: Apply trace_clock changes to instance max buffer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Baohong Liu commit 170b3b1050e28d1ba0700e262f0899ffa4fccc52 upstream. Currently trace_clock timestamps are applied to both regular and max buffers only for global trace. For instance trace,

[PATCH 3.18 08/42] [PATCH] Revert "usb: musb: fix tx fifo flush handling again"

3.18-stable review patch. If anyone has any objections, please let me know. -- This reverts commit 98b91bfa5e478b9bf332f9f149b1c25ffd58f877 which is commit 45d73860530a14c608f410b91c6c341777bfa85d upstream. It should not have been applied to the 3.18-stable tree at all.

[PATCH 3.18 07/42] f2fs: check hot_data for roll-forward recovery

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 125c9fb1ccb53eb2ea9380df40f3c743f3fb2fed upstream. We need to check HOT_DATA to truncate any previous data block when doing roll-forward recovery.

[PATCH 3.18 08/42] [PATCH] Revert "usb: musb: fix tx fifo flush handling again"

3.18-stable review patch. If anyone has any objections, please let me know. -- This reverts commit 98b91bfa5e478b9bf332f9f149b1c25ffd58f877 which is commit 45d73860530a14c608f410b91c6c341777bfa85d upstream. It should not have been applied to the 3.18-stable tree at all.

[PATCH 3.18 07/42] f2fs: check hot_data for roll-forward recovery

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim commit 125c9fb1ccb53eb2ea9380df40f3c743f3fb2fed upstream. We need to check HOT_DATA to truncate any previous data block when doing roll-forward recovery. Reviewed-by: Chao Yu

[PATCH 3.18 06/42] ipv6: fix typo in fib6_net_exit()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 32a805baf0fb70b6dbedefcd7249ac7f580f9e3b ] IPv6 FIB should use FIB6_TABLE_HASHSZ, not FIB_TABLE_HASHSZ. Fixes: ba1cc08d9488 ("ipv6: fix

[PATCH 3.18 06/42] ipv6: fix typo in fib6_net_exit()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 32a805baf0fb70b6dbedefcd7249ac7f580f9e3b ] IPv6 FIB should use FIB6_TABLE_HASHSZ, not FIB_TABLE_HASHSZ. Fixes: ba1cc08d9488 ("ipv6: fix memory leak with

[PATCH 3.18 35/42] media: uvcvideo: Prevent heap overflow when accessing mapped controls

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 7e09f7d5c790278ab98e5f2c22307ebe8ad6e8ba upstream. The size of uvc_control_mapping is user controlled leading to a potential heap overflow in the uvc

[PATCH 3.18 38/42] bcache: correct cache_dirty_target in __update_writeback_rate()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tang Junhui commit a8394090a9129b40f9d90dcb7f4a49d60c727ca6 upstream. __update_write_rate() uses a Proportion-Differentiation Controller algorithm to control writeback

[PATCH 3.18 37/42] bcache: Fix leak of bdev reference

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 4b758df21ee7081ab41448d21d60367efaa625b3 upstream. If blkdev_get_by_path() in register_bcache() fails, we try to lookup the block device using lookup_bdev() to

[PATCH 3.18 35/42] media: uvcvideo: Prevent heap overflow when accessing mapped controls

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 7e09f7d5c790278ab98e5f2c22307ebe8ad6e8ba upstream. The size of uvc_control_mapping is user controlled leading to a potential heap overflow in the uvc driver. This adds a

[PATCH 3.18 38/42] bcache: correct cache_dirty_target in __update_writeback_rate()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tang Junhui commit a8394090a9129b40f9d90dcb7f4a49d60c727ca6 upstream. __update_write_rate() uses a Proportion-Differentiation Controller algorithm to control writeback rate. A dirty target

[PATCH 3.18 37/42] bcache: Fix leak of bdev reference

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 4b758df21ee7081ab41448d21d60367efaa625b3 upstream. If blkdev_get_by_path() in register_bcache() fails, we try to lookup the block device using lookup_bdev() to detect which

[PATCH 3.18 33/42] PCI: shpchp: Enable bridge bus mastering if MSI is enabled

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Aleksandr Bezzubikov commit 48b79a14505349a29b3e20f03619ada9b33c4b17 upstream. An SHPC may generate MSIs to notify software about slot or controller events (SHPC spec

[PATCH 3.18 33/42] PCI: shpchp: Enable bridge bus mastering if MSI is enabled

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Aleksandr Bezzubikov commit 48b79a14505349a29b3e20f03619ada9b33c4b17 upstream. An SHPC may generate MSIs to notify software about slot or controller events (SHPC spec r1.0, sec 4.7). A PCI

[PATCH 3.18 34/42] media: v4l2-compat-ioctl32: Fix timespec conversion

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mentz commit 9c7ba1d7634cef490b85bc64c4091ff004821bfd upstream. Certain syscalls like recvmmsg support 64 bit timespec values for the X32 ABI. The helper

[PATCH 3.18 34/42] media: v4l2-compat-ioctl32: Fix timespec conversion

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mentz commit 9c7ba1d7634cef490b85bc64c4091ff004821bfd upstream. Certain syscalls like recvmmsg support 64 bit timespec values for the X32 ABI. The helper function compat_put_timespec

[PATCH 3.18 41/42] bcache: fix bch_hprint crash and improve output

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Lyle commit 9276717b9e297a62d1151a43d1cd286213f68eb7 upstream. Most importantly, solve a crash where %llu was used to format signed numbers. This would cause a buffer

[PATCH 3.18 40/42] bcache: fix for gc and write-back race

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tang Junhui commit 9baf30972b5568d8b5bc8b3c46a6ec5b58100463 upstream. gc and write-back get raced (see the email "bcache get stucked" I sended before): gc thread

[PATCH 3.18 36/42] bcache: initialize dirty stripes in flash_dev_run()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tang Junhui commit 175206cf9ab63161dec74d9cd7f9992e062491f5 upstream. bcache uses a Proportion-Differentiation Controller algorithm to control writeback rate to cached

[PATCH 3.18 41/42] bcache: fix bch_hprint crash and improve output

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Michael Lyle commit 9276717b9e297a62d1151a43d1cd286213f68eb7 upstream. Most importantly, solve a crash where %llu was used to format signed numbers. This would cause a buffer overflow when

[PATCH 3.18 40/42] bcache: fix for gc and write-back race

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tang Junhui commit 9baf30972b5568d8b5bc8b3c46a6ec5b58100463 upstream. gc and write-back get raced (see the email "bcache get stucked" I sended before): gc thread

[PATCH 3.18 36/42] bcache: initialize dirty stripes in flash_dev_run()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tang Junhui commit 175206cf9ab63161dec74d9cd7f9992e062491f5 upstream. bcache uses a Proportion-Differentiation Controller algorithm to control writeback rate to cached devices. In the PD

[PATCH 3.18 32/42] ARC: Re-enable MMU upon Machine Check exception

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jose Abreu commit 1ee55a8f7f6b7ca4c0c59e0b4b4e3584a085c2d3 upstream. I recently came upon a scenario where I would get a double fault machine check exception

[PATCH 3.18 39/42] bcache: Correct return value for sysfs attach errors

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tony Asleson commit 77fa100f27475d08a569b9d51c17722130f089e7 upstream. If you encounter any errors in bch_cached_dev_attach it will return a negative error code. The

[PATCH 3.18 39/42] bcache: Correct return value for sysfs attach errors

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tony Asleson commit 77fa100f27475d08a569b9d51c17722130f089e7 upstream. If you encounter any errors in bch_cached_dev_attach it will return a negative error code. The variable 'v' which

[PATCH 3.18 32/42] ARC: Re-enable MMU upon Machine Check exception

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jose Abreu commit 1ee55a8f7f6b7ca4c0c59e0b4b4e3584a085c2d3 upstream. I recently came upon a scenario where I would get a double fault machine check exception tiriggered by a kernel module.

[PATCH 3.18 19/42] scsi: zfcp: add handling for FCP_RESID_OVER to the fcp ingress path

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Block commit a099b7b1fc1f0418ab8d79ecf98153e1e134656e upstream. Up until now zfcp would just ignore the FCP_RESID_OVER flag in the FCP response IU. When

[PATCH 3.18 16/42] skd: Avoid that module unloading triggers a use-after-free

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 7277cc67b3916eed47558c64f9c9c0de00a35cda upstream. Since put_disk() triggers a disk_release() call and since that last function calls

[PATCH 3.18 19/42] scsi: zfcp: add handling for FCP_RESID_OVER to the fcp ingress path

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Block commit a099b7b1fc1f0418ab8d79ecf98153e1e134656e upstream. Up until now zfcp would just ignore the FCP_RESID_OVER flag in the FCP response IU. When this flag is set, it is

[PATCH 3.18 16/42] skd: Avoid that module unloading triggers a use-after-free

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 7277cc67b3916eed47558c64f9c9c0de00a35cda upstream. Since put_disk() triggers a disk_release() call and since that last function calls blk_put_queue() if disk->queue !=

[PATCH 3.18 25/42] scsi: sg: use standard lists for sg_requests

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 109bade9c625c89bb5ea753aaa1a0a97e6fbb548 upstream. 'Sg_request' is using a private list implementation; convert it to standard lists. Signed-off-by:

[PATCH 3.18 21/42] scsi: zfcp: fix payload with full FCP_RSP IU in SCSI trace records

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 12c3e5754c8022a4f2fd1e9f00d19e99ee0d3cc1 upstream. If the FCP_RSP UI has optional parts (FCP_SNS_INFO or FCP_RSP_INFO) and thus does not fit

[PATCH 3.18 27/42] scsi: sg: factor out sg_fill_request_table()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 4759df905a474d245752c9dc94288e779b8734dd upstream. Factor out sg_fill_request_table() for better readability. [mkp: typos, applied by hand]

[PATCH 3.18 17/42] skd: Submit requests to firmware before triggering the doorbell

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 5fbd545cd3fd311ea1d6e8be4ce0ee5684c7 upstream. Ensure that the members of struct skd_msg_buf have been transferred to the PCIe adapter

[PATCH 3.18 09/42] ip6_gre: fix endianness errors in ip6gre_err

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca commit d1e158e2d7a0a91110b206653f0e02376e809150 upstream. info is in network byte order, change it back to host byte order before use. In particular, the

[PATCH 3.18 42/42] mac80211: flush hw_roc_start work before cancelling the ROC

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Avraham Stern commit 6e46d8ce894374fc135c96a8d1057c6af1fef237 upstream. When HW ROC is supported it is possible that after the HW notified that the ROC has started,

[PATCH 3.18 05/42] ipv6: fix memory leak with multiple tables during netns destruction

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit ba1cc08d9488c94cb8d94f545305688b72a2a300 ] fib6_net_exit only frees the main and local tables. If another table was created with

[PATCH 3.18 42/42] mac80211: flush hw_roc_start work before cancelling the ROC

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Avraham Stern commit 6e46d8ce894374fc135c96a8d1057c6af1fef237 upstream. When HW ROC is supported it is possible that after the HW notified that the ROC has started, the ROC was cancelled and

[PATCH 3.18 05/42] ipv6: fix memory leak with multiple tables during netns destruction

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit ba1cc08d9488c94cb8d94f545305688b72a2a300 ] fib6_net_exit only frees the main and local tables. If another table was created with fib6_alloc_table, we leak

[PATCH 3.18 25/42] scsi: sg: use standard lists for sg_requests

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 109bade9c625c89bb5ea753aaa1a0a97e6fbb548 upstream. 'Sg_request' is using a private list implementation; convert it to standard lists. Signed-off-by: Hannes Reinecke

[PATCH 3.18 21/42] scsi: zfcp: fix payload with full FCP_RSP IU in SCSI trace records

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 12c3e5754c8022a4f2fd1e9f00d19e99ee0d3cc1 upstream. If the FCP_RSP UI has optional parts (FCP_SNS_INFO or FCP_RSP_INFO) and thus does not fit into the fsp_rsp field built

[PATCH 3.18 27/42] scsi: sg: factor out sg_fill_request_table()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Reinecke commit 4759df905a474d245752c9dc94288e779b8734dd upstream. Factor out sg_fill_request_table() for better readability. [mkp: typos, applied by hand] Signed-off-by: Hannes

[PATCH 3.18 17/42] skd: Submit requests to firmware before triggering the doorbell

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 5fbd545cd3fd311ea1d6e8be4ce0ee5684c7 upstream. Ensure that the members of struct skd_msg_buf have been transferred to the PCIe adapter before the doorbell is

[PATCH 3.18 09/42] ip6_gre: fix endianness errors in ip6gre_err

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca commit d1e158e2d7a0a91110b206653f0e02376e809150 upstream. info is in network byte order, change it back to host byte order before use. In particular, the current code sets the

[PATCH 3.18 00/42] 3.18.72-stable review

This is the start of the stable review cycle for the 3.18.72 release. There are 42 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 Tue Sep 26 20:26:30 UTC 2017. Anything

[PATCH 3.18 12/42] ext4: fix incorrect quotaoff if the quota feature is enabled

3.18-stable review patch. If anyone has any objections, please let me know. -- From: zhangyi (F) commit b0a5a9589decd07db755d6a8d9c0910d96ff7992 upstream. Current ext4 quota should always "usage enabled" if the quota feautre is enabled. But in

[PATCH 3.18 00/42] 3.18.72-stable review

This is the start of the stable review cycle for the 3.18.72 release. There are 42 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 Tue Sep 26 20:26:30 UTC 2017. Anything

[PATCH 3.18 12/42] ext4: fix incorrect quotaoff if the quota feature is enabled

3.18-stable review patch. If anyone has any objections, please let me know. -- From: zhangyi (F) commit b0a5a9589decd07db755d6a8d9c0910d96ff7992 upstream. Current ext4 quota should always "usage enabled" if the quota feautre is enabled. But in ext4_orphan_cleanup(), it turn

[PATCH 3.18 11/42] [PATCH - RESEND] crypto: AF_ALG - remove SGL terminator indicator when chaining

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stephan Mueller Fixed differently upstream as commit 2d97591ef43d ("crypto: af_alg - consolidation of duplicate code") The SGL is MAX_SGL_ENTS + 1 in size. The last SG

[PATCH 3.18 11/42] [PATCH - RESEND] crypto: AF_ALG - remove SGL terminator indicator when chaining

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stephan Mueller Fixed differently upstream as commit 2d97591ef43d ("crypto: af_alg - consolidation of duplicate code") The SGL is MAX_SGL_ENTS + 1 in size. The last SG entry is used for the

[PATCH 3.18 10/42] Input: i8042 - add Gigabyte P57 to the keyboard reset table

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 697c5d8a36768b36729533fb44622b35d56d6ad0 upstream. Similar to other Gigabyte laptops, the touchpad on P57 requires a keyboard reset to detect

[PATCH 3.18 10/42] Input: i8042 - add Gigabyte P57 to the keyboard reset table

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit 697c5d8a36768b36729533fb44622b35d56d6ad0 upstream. Similar to other Gigabyte laptops, the touchpad on P57 requires a keyboard reset to detect Elantech touchpad correctly.

Re: [PATCH 03/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in sanitize_restored_xstate()

On Sun, Sep 24, 2017 at 09:02:42PM +0200, Ingo Molnar wrote: > > * Eric Biggers wrote: > > > On Sun, Sep 24, 2017 at 12:59:06PM +0200, Ingo Molnar wrote: > > > @@ -328,10 +331,8 @@ static int __fpu__restore_sig(void __user *buf, void > > > __user *buf_fx, int size) > > >

Re: [PATCH 03/10] x86/fpu: Use validate_xstate_header() to validate the xstate_header in sanitize_restored_xstate()

On Sun, Sep 24, 2017 at 09:02:42PM +0200, Ingo Molnar wrote: > > * Eric Biggers wrote: > > > On Sun, Sep 24, 2017 at 12:59:06PM +0200, Ingo Molnar wrote: > > > @@ -328,10 +331,8 @@ static int __fpu__restore_sig(void __user *buf, void > > > __user *buf_fx, int size) > > > err

[PATCH v2 2/2] pidmap(2)

From: Tatsiana Brouka Implement system call for bulk retrieveing of pids in binary form. Using /proc is slower than necessary: 3 syscalls + another 3 for each thread + converting with atoi() + instantiating dentries and inodes. /proc may be not mounted especially in

[PATCH v2 2/2] pidmap(2)

From: Tatsiana Brouka Implement system call for bulk retrieveing of pids in binary form. Using /proc is slower than necessary: 3 syscalls + another 3 for each thread + converting with atoi() + instantiating dentries and inodes. /proc may be not mounted especially in containers. Natural

[PATCH 1/2 v2] fdmap(2)

From: Aliaksandr Patseyenak Implement system call for bulk retrieveing of opened descriptors in binary form. Some daemons could use it to reliably close file descriptors before starting. Currently they close everything upto some number which formally is not

[PATCH 1/2 v2] fdmap(2)

From: Aliaksandr Patseyenak Implement system call for bulk retrieveing of opened descriptors in binary form. Some daemons could use it to reliably close file descriptors before starting. Currently they close everything upto some number which formally is not reliable. Other natural users are

[PATCH v4 04/10] clk: rework calls to round and determine rate callbacks

Rework the way the callbacks round_rate() and determine_rate() are called. The goal is to do this at a single point and make it easier to add conditions before calling them. Because of this factorization, rate returned by determine_rate() is also checked against the min and max rate values This

[PATCH v4 02/10] clk: take the prepare lock out of clk_core_set_parent

Rework set_parent core function so it can be called when the prepare lock is already held by the caller. This rework is done to ease the integration of the "protected" clock functionality. Acked-by: Linus Walleij Tested-by: Quentin Schulz

[PATCH v4 04/10] clk: rework calls to round and determine rate callbacks

Rework the way the callbacks round_rate() and determine_rate() are called. The goal is to do this at a single point and make it easier to add conditions before calling them. Because of this factorization, rate returned by determine_rate() is also checked against the min and max rate values This

[PATCH v4 02/10] clk: take the prepare lock out of clk_core_set_parent

Rework set_parent core function so it can be called when the prepare lock is already held by the caller. This rework is done to ease the integration of the "protected" clock functionality. Acked-by: Linus Walleij Tested-by: Quentin Schulz Signed-off-by: Jerome Brunet --- drivers/clk/clk.c |

[PATCH v4 08/10] clk: fix CLK_SET_RATE_GATE with clock rate protection

Using clock rate protection, we can now enforce CLK_SET_RATE_GATE along the clock tree Acked-by: Linus Walleij Tested-by: Quentin Schulz Signed-off-by: Jerome Brunet --- drivers/clk/clk.c | 16 +---

[PATCH v4 07/10] clk: cosmetic changes to clk_summary debugfs entry

clk_summary debugfs entry was already well over the traditional 80 characters per line limit but it grew even larger with the addition of clock protection. clock enable_cnt prepare_cnt protect_cnt rate accuracy phase

[PATCH v4 08/10] clk: fix CLK_SET_RATE_GATE with clock rate protection

Using clock rate protection, we can now enforce CLK_SET_RATE_GATE along the clock tree Acked-by: Linus Walleij Tested-by: Quentin Schulz Signed-off-by: Jerome Brunet --- drivers/clk/clk.c | 16 +--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/drivers/clk/clk.c

[PATCH v4 07/10] clk: cosmetic changes to clk_summary debugfs entry

clk_summary debugfs entry was already well over the traditional 80 characters per line limit but it grew even larger with the addition of clock protection. clock enable_cnt prepare_cnt protect_cnt rate accuracy phase

[PATCH v4 03/10] clk: add clk_core_set_phase_nolock function

Create a core function for set_phase, as it is done for set_rate and set_parent. This rework is done to ease the integration of "protected" clock functionality. Acked-by: Linus Walleij Tested-by: Quentin Schulz Signed-off-by: Jerome

[PATCH v4 03/10] clk: add clk_core_set_phase_nolock function

Create a core function for set_phase, as it is done for set_rate and set_parent. This rework is done to ease the integration of "protected" clock functionality. Acked-by: Linus Walleij Tested-by: Quentin Schulz Signed-off-by: Jerome Brunet --- drivers/clk/clk.c | 33

[PATCH v4 01/10] clk: fix incorrect usage of ENOSYS

ENOSYS is special and should only be used for incorrect syscall number. It does not seem to be the case here. Reported by checkpatch.pl while working on clock protection. Acked-by: Linus Walleij Tested-by: Quentin Schulz

[PATCH v4 01/10] clk: fix incorrect usage of ENOSYS

ENOSYS is special and should only be used for incorrect syscall number. It does not seem to be the case here. Reported by checkpatch.pl while working on clock protection. Acked-by: Linus Walleij Tested-by: Quentin Schulz Signed-off-by: Jerome Brunet --- drivers/clk/clk.c | 2 +- 1 file

[PATCH v4 05/10] clk: use round rate to bail out early in set_rate

The current implementation of clk_core_set_rate_nolock() bails out early if the requested rate is exactly the same as the one set. It should bail out if the request would not result in a rate a change. This is important when the rate is not exactly what is requested, which is fairly common with

[PATCH v4 09/10] clk: add clk_rate_exclusive api

Using clock rate protection, we can now provide a way for clock consumer to claim exclusive control over the rate of a producer So far, rate change operations have been a "last write wins" affair. This changes allows drivers to explicitly protect against this behavior, if required. Of course, if

[PATCH v4 05/10] clk: use round rate to bail out early in set_rate

The current implementation of clk_core_set_rate_nolock() bails out early if the requested rate is exactly the same as the one set. It should bail out if the request would not result in a rate a change. This is important when the rate is not exactly what is requested, which is fairly common with

[PATCH v4 09/10] clk: add clk_rate_exclusive api

Using clock rate protection, we can now provide a way for clock consumer to claim exclusive control over the rate of a producer So far, rate change operations have been a "last write wins" affair. This changes allows drivers to explicitly protect against this behavior, if required. Of course, if

[PATCH v4 06/10] clk: add clock protection mechanism to clk core

The patch adds clk_core_protect and clk_core_unprotect to the internal CCF API. These functions allow to set a new constraint along the clock tree to prevent any change, even indirect, which may result in rate change or glitch. Signed-off-by: Jerome Brunet ---

[PATCH v4 10/10] clk: fix set_rate_range when current rate is out of range

Calling clk_core_set_rate() with core->req_rate is basically a no-op because of the early bail-out mechanism. This may leave the clock in inconsistent state if the rate is out the requested range. Calling clk_core_set_rate() with the closest rate limit could solve the problem but: - The

[PATCH v4 06/10] clk: add clock protection mechanism to clk core

The patch adds clk_core_protect and clk_core_unprotect to the internal CCF API. These functions allow to set a new constraint along the clock tree to prevent any change, even indirect, which may result in rate change or glitch. Signed-off-by: Jerome Brunet --- drivers/clk/clk.c| 119

[PATCH v4 10/10] clk: fix set_rate_range when current rate is out of range

Calling clk_core_set_rate() with core->req_rate is basically a no-op because of the early bail-out mechanism. This may leave the clock in inconsistent state if the rate is out the requested range. Calling clk_core_set_rate() with the closest rate limit could solve the problem but: - The

[PATCH v4 00/10] clk: implement clock rate protection mechanism

This Patchset is related the RFC [0] and the discussion around CLK_SET_RATE_GATE available here [1] This patchset introduce clock protection to the CCF core. This can then be used for: * Provide a way for a consumer to claim exclusivity over the rate control of a provider. Some clock consumers

[PATCH v4 00/10] clk: implement clock rate protection mechanism

This Patchset is related the RFC [0] and the discussion around CLK_SET_RATE_GATE available here [1] This patchset introduce clock protection to the CCF core. This can then be used for: * Provide a way for a consumer to claim exclusivity over the rate control of a provider. Some clock consumers

Re: [PATCH 1/8] extcon: gpio: Add DT bindings

On Sun, Sep 24, 2017 at 9:56 AM, Linus Walleij wrote: > Add some reasonable device tree bindings and also add the cable defines > to the extcon include in since > the GPIO extcon definately need to specify which cable/connector it is > detecting. > > Adding the include

Re: [PATCH 1/8] extcon: gpio: Add DT bindings

On Sun, Sep 24, 2017 at 9:56 AM, Linus Walleij wrote: > Add some reasonable device tree bindings and also add the cable defines > to the extcon include in since > the GPIO extcon definately need to specify which cable/connector it is > detecting. > > Adding the include file makes the (as it

Re: [PATCH 1/4] rcu: Allow for page faults in NMI handlers

On Sat, Sep 23, 2017 at 1:56 PM, Steven Rostedt wrote: > + > + /* Page faults can happen in NMI handlers, so check... */ > + if (READ_ONCE(rdtp->dynticks_nmi_nesting)) > + return; > + What is the reason for the READ_ONCE() here (and in the other

Re: [PATCH 1/4] rcu: Allow for page faults in NMI handlers

On Sat, Sep 23, 2017 at 1:56 PM, Steven Rostedt wrote: > + > + /* Page faults can happen in NMI handlers, so check... */ > + if (READ_ONCE(rdtp->dynticks_nmi_nesting)) > + return; > + What is the reason for the READ_ONCE() here (and in the other case)? It doesn't seem

Re: [PATCH v6 1/2] media:imx274 device tree binding file

On Sun, Sep 24, 2017 at 12:53:28AM -0700, Leon Luo wrote: > The binding file for imx274 CMOS sensor V4l2 driver > > Signed-off-by: Leon Luo > --- > v6: > - no changes > v5: > - add 'port' and 'endpoint' information > v4: > - no changes > v3: > - remove redundant

Re: [PATCH v6 1/2] media:imx274 device tree binding file

On Sun, Sep 24, 2017 at 12:53:28AM -0700, Leon Luo wrote: > The binding file for imx274 CMOS sensor V4l2 driver > > Signed-off-by: Leon Luo > --- > v6: > - no changes > v5: > - add 'port' and 'endpoint' information > v4: > - no changes > v3: > - remove redundant properties and references >

Re: [PATCH] mm: fix RODATA_TEST failure "rodata_test: test data was not read only"

On Thu, Sep 21, 2017 at 2:37 AM, Christophe Leroy wrote: > On powerpc, RODATA_TEST fails with message the following messages: > > [6.199505] Freeing unused kernel memory: 528K > [6.203935] rodata_test: test data was not read only > > This is because GCC allocates

Re: [PATCH] mm: fix RODATA_TEST failure "rodata_test: test data was not read only"

On Thu, Sep 21, 2017 at 2:37 AM, Christophe Leroy wrote: > On powerpc, RODATA_TEST fails with message the following messages: > > [6.199505] Freeing unused kernel memory: 528K > [6.203935] rodata_test: test data was not read only > > This is because GCC allocates it to .data section: > >

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