4.19.42-stable review
Subsystems (4)
Greg Kroah-Hartman
maintainerPATCH 43/66 drm/mediatek: fix possible object reference leak
In reply to Greg Kroah-Hartman[ Upstream commit 2ae2c3316fb77dcf64275d011596b60104c45426 ]
The call to of_parse_phandle returns a node pointer with refcount incremented thus it must be explicitly decremented after the last usage.
Detected by coccinelle with the following warnings:
drivers/gpu/drm/mediatek/mtk_hdmi.c:1521:2-8: ERROR: missing of_node_put; acquired a node pointer with refcount incremented on line 1509, but without a corresponding object release within this function. drivers/gpu/drm/mediatek/mtk_hdmi.c:1524:1-7: ERROR: missing of_node_put; acquired a node pointer with refcount incremented on line 1509, but without a corresponding object release within this function.
--- drivers/gpu/drm/mediatek/mtk_hdmi.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/mediatek/mtk_hdmi.c +1 -0
@@ -1508,6 +1508,7 @@ static int mtk_hdmi_dt_parse_pdata(struct mtk_hdmi *hdmi,of_node_put (remote); hdmi->ddc_adpt =of_find_i2c_adapter_by_node (i2c_np); +of_node_put (i2c_np);if (!hdmi->ddc_adpt) {dev_err (dev,"Failed to get ddc i2c adapter by node\n" );return -EINVAL ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 3/66 Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup()
In reply to Greg Kroah-HartmanFrom: Dexuan Cui <[email protected]>
commit a0033bd1eae4650b69be07c17cb87393da584563 upstream.
With CONFIG_DEBUG_PREEMPT=y, the put_cpu_ptr() triggers an underflow warning in preempt_count_sub().
--- drivers/hv/hv.c | 1 - 1 file changed, 1 deletion(-)
drivers/hv/hv.c +0 -1
@@ -402,7 +402,6 @@ int hv_synic_cleanup(unsigned int cpu)clockevents_unbind_device (hv_cpu->clk_evt, cpu);hv_ce_shutdown (hv_cpu->clk_evt); -put_cpu_ptr (hv_cpu); }hv_get_synint_state (VMBUS_MESSAGE_SINT , shared_sint.as_uint64);
Greg Kroah-Hartman
maintainerPATCH 4/66 ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings
In reply to Greg Kroah-HartmanFrom: Andrey Ryabinin <[email protected]>
commit f0996bc2978e02d2ea898101462b960f6119b18f upstream.
Building lib/ubsan.c with gcc-9 results in a ton of nasty warnings like this one:
lib/ubsan.c warning: conflicting types for built-in function
‘__ubsan_handle_negate_overflow’; expected ‘void(void *, void *)’ [-Wbuiltin-declaration-mismatch]
The kernel's declarations of __ubsan_handle_*() often uses 'unsigned long' types in parameters while GCC these parameters as 'void *' types, hence the mismatch.
Fix this by using 'void *' to match GCC's declarations.
--- lib/ubsan.c | 49 +++++++++++++++++++++++-------------------------- 1 file changed, 23 insertions(+), 26 deletions(-)
lib/ubsan.c +23 -26
@@ -86,11 +86,13 @@ static bool is_inline_int(struct type_dereturn bits <= inline_bits; } -static s_max get_signed_val (struct type_descriptor *type,unsigned long val) +static s_max get_signed_val (struct type_descriptor *type,void *val) {if (is_inline_int (type)) {unsigned extra_bits =sizeof (s_max)*8 -type_bit_width (type); -return ((s_max )val) << extra_bits >> extra_bits; +unsigned long ulong_val = (unsigned long )val; + +return ((s_max )ulong_val) << extra_bits >> extra_bits; }if (type_bit_width (type) ==64 )
@@ -99,15 +101,15 @@ static s_max get_signed_val(struct type_return *(s_max *)val; } -static bool val_is_negative (struct type_descriptor *type,unsigned long val) +static bool val_is_negative (struct type_descriptor *type,void *val) {return type_is_signed (type) &&get_signed_val (type, val) <0 ; } -static u_max get_unsigned_val (struct type_descriptor *type,unsigned long val) +static u_max get_unsigned_val (struct type_descriptor *type,void *val) {if (is_inline_int (type)) -return val; +return (unsigned long )val;if (type_bit_width (type) ==64 )return *(u64 *)val;
@@ -116,7 +118,7 @@ static u_max get_unsigned_val(struct typ }static void val_to_string (char *str,size_t size,struct type_descriptor *type, -unsigned long value) +void *value) {if (type_is_int (type)) {if (type_bit_width (type) ==128 ) {
@@ -163,8 +165,8 @@ static void ubsan_epilogue(unsigned long current->in_ubsan--; } -static void handle_overflow (struct overflow_data *data,unsigned long lhs, -unsigned long rhs,char op) +static void handle_overflow (struct overflow_data *data,void *lhs, +void *rhs,char op) {struct type_descriptor *type = data->type;
@@ -191,8 +193,7 @@ static void handle_overflow(struct overf }void __ubsan_handle_add_overflow (struct overflow_data *data, -unsigned long lhs, -unsigned long rhs) +void *lhs,void *rhs) {handle_overflow (data, lhs, rhs,'+' );
@@ -200,23 +201,21 @@ void __ubsan_handle_add_overflow(structEXPORT_SYMBOL (__ubsan_handle_add_overflow);void __ubsan_handle_sub_overflow (struct overflow_data *data, -unsigned long lhs, -unsigned long rhs) +void *lhs,void *rhs) {handle_overflow (data, lhs, rhs,'-' ); }EXPORT_SYMBOL (__ubsan_handle_sub_overflow);void __ubsan_handle_mul_overflow (struct overflow_data *data, -unsigned long lhs, -unsigned long rhs) +void *lhs,void *rhs) {handle_overflow (data, lhs, rhs,'*' ); }EXPORT_SYMBOL (__ubsan_handle_mul_overflow);void __ubsan_handle_negate_overflow (struct overflow_data *data, -unsigned long old_val) +void *old_val) {unsigned long flags;char old_val_str[VALUE_LENGTH ];
@@ -237,8 +236,7 @@ EXPORT_SYMBOL(__ubsan_handle_negate_overvoid __ubsan_handle_divrem_overflow (struct overflow_data *data, -unsigned long lhs, -unsigned long rhs) +void *lhs,void *rhs) {unsigned long flags;char rhs_val_str[VALUE_LENGTH ];
@@ -323,7 +321,7 @@ static void ubsan_type_mismatch_common(s }void __ubsan_handle_type_mismatch (struct type_mismatch_data *data, -unsigned long ptr) +void *ptr) {struct type_mismatch_data_common common_data = { .location = &data->location,
@@ -332,12 +330,12 @@ void __ubsan_handle_type_mismatch(struct .type_check_kind = data->type_check_kind }; -ubsan_type_mismatch_common (&common_data, ptr); +ubsan_type_mismatch_common (&common_data, (unsigned long )ptr); }EXPORT_SYMBOL (__ubsan_handle_type_mismatch);void __ubsan_handle_type_mismatch_v1 (struct type_mismatch_data_v1 *data, -unsigned long ptr) +void *ptr) {struct type_mismatch_data_common common_data = {
@@ -347,12 +345,12 @@ void __ubsan_handle_type_mismatch_v1(str .type_check_kind = data->type_check_kind }; -ubsan_type_mismatch_common (&common_data, ptr); +ubsan_type_mismatch_common (&common_data, (unsigned long )ptr); }EXPORT_SYMBOL (__ubsan_handle_type_mismatch_v1);void __ubsan_handle_vla_bound_not_positive (struct vla_bound_data *data, -unsigned long bound) +void *bound) {unsigned long flags;char bound_str[VALUE_LENGTH ];
@@ -369,8 +367,7 @@ void __ubsan_handle_vla_bound_not_positi }EXPORT_SYMBOL (__ubsan_handle_vla_bound_not_positive); -void __ubsan_handle_out_of_bounds (struct out_of_bounds_data *data, -unsigned long index) +void __ubsan_handle_out_of_bounds (struct out_of_bounds_data *data,void *index) {unsigned long flags;char index_str[VALUE_LENGTH ];
@@ -388,7 +385,7 @@ void __ubsan_handle_out_of_bounds(structEXPORT_SYMBOL (__ubsan_handle_out_of_bounds);void __ubsan_handle_shift_out_of_bounds (struct shift_out_of_bounds_data *data, -unsigned long lhs,unsigned long rhs) +void *lhs,void *rhs) {unsigned long flags;struct type_descriptor *rhs_type = data->rhs_type;
@@ -439,7 +436,7 @@ void __ubsan_handle_builtin_unreachable(EXPORT_SYMBOL (__ubsan_handle_builtin_unreachable);void __ubsan_handle_load_invalid_value (struct invalid_value_data *data, -unsigned long val) +void *val) {unsigned long flags;char val_str[VALUE_LENGTH ];
Greg Kroah-Hartman
maintainerPATCH 5/66 staging: greybus: power_supply: fix prop-descriptor request size
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit 47830c1127ef166af787caf2f871f23089610a7f upstream.
Since moving the message buffers off the stack, the dynamically allocated get-prop-descriptor request buffer is incorrectly sized due to using the pointer rather than request-struct size when creating the operation.
Fortunately, the pointer size is always larger than this one-byte request, but this could still cause trouble on the remote end due to the unexpected message size.
--- drivers/staging/greybus/power_supply.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/staging/greybus/power_supply.c +1 -1
@@ -520,7 +520,7 @@ static int gb_power_supply_prop_descript op =gb_operation_create (connection,GB_POWER_SUPPLY_TYPE_GET_PROP_DESCRIPTORS , -sizeof (req),sizeof (*resp) + props_count * +sizeof (*req),sizeof (*resp) + props_count *sizeof (struct gb_power_supply_props_desc ),GFP_KERNEL );if (!op)
Greg Kroah-Hartman
maintainerPATCH 6/66 staging: most: cdev: fix chrdev_region leak in mod_exit
In reply to Greg Kroah-HartmanFrom: Suresh Udipi <[email protected]>
commit af708900e9a48c0aa46070c8a8cdf0608a1d2025 upstream.
It looks like v4.18-rc1 commit [0] which upstreams mld-1.8.0 commit [1] missed to fix the memory leak in mod_exit function.
Do it now.
[0] aba258b7310167 ("staging: most: cdev: fix chrdev_region leak")
[1] https://github.com/microchip-ais/linux/commit/a2d8f7ae7ea381
("staging: most: cdev: fix leak for chrdev_region")
--- drivers/staging/most/cdev/cdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/staging/most/cdev/cdev.c +1 -1
@@ -546,7 +546,7 @@ static void __exit mod_exit(void)destroy_cdev (c);destroy_channel (c); } -unregister_chrdev_region (comp.devno,1 ); +unregister_chrdev_region (comp.devno,CHRDEV_REGION_SIZE );ida_destroy (&comp.minor_id);class_destroy (comp.class); }
Greg Kroah-Hartman
maintainerPATCH 7/66 ASoC: tlv320aic3x: fix reset gpio reference counting
In reply to Greg Kroah-Hartman[ Upstream commit 82ad759143ed77673db0d93d53c1cde7b99917ee ]
This patch fixes a bug that prevents freeing the reset gpio on unloading the module.
aic3x_i2c_probe is called when loading the module and it calls list_add with a probably uninitialized list entry aic3x->list (next = prev = NULL)). So even if list_del is called it does nothing and in the end the gpio_reset is not freed. Then a repeated module probing fails silently because gpio_request fails.
When moving INIT_LIST_HEAD to aic3x_i2c_probe we also have to move list_del to aic3x_i2c_remove because aic3x_remove may be called multiple times without aic3x_i2c_remove being called which leads to a NULL pointer dereference.
--- sound/soc/codecs/tlv320aic3x.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
sound/soc/codecs/tlv320aic3x.c +3 -2
@@ -1599,7 +1599,6 @@ static int aic3x_probe(struct snd_soc_component *component)struct aic3x_priv *aic3x =snd_soc_component_get_drvdata (component);int ret, i; -INIT_LIST_HEAD (&aic3x->list); aic3x->component = component;for (i =0 ; i <ARRAY_SIZE (aic3x->supplies); i++) {
@@ -1682,7 +1681,6 @@ static void aic3x_remove(struct snd_soc_component *component)struct aic3x_priv *aic3x =snd_soc_component_get_drvdata (component);int i; -list_del (&aic3x->list);for (i =0 ; i <ARRAY_SIZE (aic3x->supplies); i++)regulator_unregister_notifier (aic3x->supplies[i].consumer, &aic3x->disable_nb[i].nb);
@@ -1880,6 +1878,7 @@ static int aic3x_i2c_probe(struct i2c_client *i2c,if (ret !=0 ) goto err_gpio; +INIT_LIST_HEAD (&aic3x->list);list_add (&aic3x->list, &reset_list);return 0 ;
@@ -1896,6 +1895,8 @@ static int aic3x_i2c_remove(struct i2c_client *client) {struct aic3x_priv *aic3x =i2c_get_clientdata (client); +list_del (&aic3x->list); +if (gpio_is_valid (aic3x->gpio_reset) && !aic3x_is_shared_reset (aic3x)) {gpio_set_value (aic3x->gpio_reset,0 );
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 18/66 clk: meson-gxbb: round the vdec dividers to closest
In reply to Greg Kroah-Hartman[ Upstream commit 9b70c697e87286ade406e6a02091757307dd4b7c ]
We want the video decoder clocks to always round to closest. While the muxes are already using CLK_MUX_ROUND_CLOSEST, the corresponding CLK_DIVIDER_ROUND_CLOSEST was forgotten for the dividers.
Fix this by adding the flag to the two vdec dividers.
--- drivers/clk/meson/gxbb.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/clk/meson/gxbb.c +2 -0
@@ -1571,6 +1571,7 @@ static struct clk_regmap gxbb_vdec_1_div = { .offset = HHI_VDEC_CLK_CNTL, .shift = 0, .width = 7, + .flags = CLK_DIVIDER_ROUND_CLOSEST, }, .hw.init = &(struct clk_init_data ){ .name ="vdec_1_div" ,
@@ -1616,6 +1617,7 @@ static struct clk_regmap gxbb_vdec_hevc_div = { .offset = HHI_VDEC2_CLK_CNTL, .shift = 16, .width = 7, + .flags = CLK_DIVIDER_ROUND_CLOSEST, }, .hw.init = &(struct clk_init_data ){ .name ="vdec_hevc_div" ,
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 9/66 ASoC: stm32: sai: fix iec958 controls indexation
In reply to Greg Kroah-Hartman[ Upstream commit 5f8a1000c3e630c3ac06f1d664eeaa755bce8823 ]
Allow indexation of sai iec958 controls according
to device id.
--- sound/soc/stm/stm32_sai_sub.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
sound/soc/stm/stm32_sai_sub.c +4 -3
@@ -96,7 +96,7 @@* @slot_mask: rx or tx active slots mask. set at init or at runtime * @data_size: PCM data width. corresponds to PCM substream width. * @spdif_frm_cnt: S/PDIF playback frame counter -* @snd_aes_iec958: iec958 data +* @iec958: iec958 data * @ctrl_lock: control lock */ struct stm32_sai_sub_data {
@@ -888,11 +888,12 @@ static int stm32_sai_pcm_new(struct snd_soc_pcm_runtime *rtd, struct snd_soc_dai *cpu_dai) {struct stm32_sai_sub_data *sai =dev_get_drvdata (cpu_dai->dev); +struct snd_kcontrol_new knew = iec958_ctls;if (STM_SAI_PROTOCOL_IS_SPDIF (sai)) {dev_dbg (&sai->pdev->dev,"%s: register iec controls" , __func__); -return snd_ctl_add (rtd->pcm->card, -snd_ctl_new1 (&iec958_ctls, sai)); + knew.device = rtd->pcm->device; +return snd_ctl_add (rtd->pcm->card,snd_ctl_new1 (&knew, sai)); }return 0 ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 20/66 ASoC: stm32: dfsdm: fix debugfs warnings on entry creation
In reply to Greg Kroah-Hartman[ Upstream commit c47255b61129857b74b0d86eaf59335348be05e0 ]
Register platform component with a prefix, to avoid warnings on debugfs entries creation, due to component name redundancy.
--- sound/soc/stm/stm32_adfsdm.c | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-)
sound/soc/stm/stm32_adfsdm.c +18 -3
@@ -304,6 +304,7 @@ MODULE_DEVICE_TABLE(of, stm32_adfsdm_of_match);static int stm32_adfsdm_probe (struct platform_device *pdev) {struct stm32_adfsdm_priv *priv; +struct snd_soc_component *component;int ret; priv =devm_kzalloc (&pdev->dev,sizeof (*priv),GFP_KERNEL );
@@ -331,9 +332,15 @@ static int stm32_adfsdm_probe(struct platform_device *pdev)if (IS_ERR (priv->iio_cb))return PTR_ERR (priv->iio_cb); - ret =devm_snd_soc_register_component (&pdev->dev, - &stm32_adfsdm_soc_platform, -NULL ,0 ); + component =devm_kzalloc (&pdev->dev,sizeof (*component),GFP_KERNEL ); +if (!component) +return -ENOMEM ; +#ifdef CONFIG_DEBUG_FS + component->debugfs_prefix ="pcm" ; +#endif + + ret =snd_soc_add_component (&pdev->dev, component, + &stm32_adfsdm_soc_platform,NULL ,0 );if (ret <0 )dev_err (&pdev->dev,"%s: Failed to register PCM platform\n" , __func__);
@@ -341,12 +348,20 @@ static int stm32_adfsdm_probe(struct platform_device *pdev)return ret; } +static int stm32_adfsdm_remove (struct platform_device *pdev) +{ +snd_soc_unregister_component (&pdev->dev); + +return 0 ; +} +static struct platform_driver stm32_adfsdm_driver = { .driver = { .name =STM32_ADFSDM_DRV_NAME , .of_match_table = stm32_adfsdm_of_match, }, .probe = stm32_adfsdm_probe, + .remove = stm32_adfsdm_remove, };module_platform_driver (stm32_adfsdm_driver);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 22/66 ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol
In reply to Greg Kroah-Hartman[ Upstream commit cacea3a90e211f0c111975535508d446a4a928d2 ]
w_text_param can be NULL and it is being dereferenced without checking. Add the missing sanity check to prevent NULL pointer dereference.
--- sound/soc/soc-dapm.c | 4 ++++ 1 file changed, 4 insertions(+)
sound/soc/soc-dapm.c +4 -0
@@ -3847,6 +3847,10 @@ snd_soc_dapm_free_kcontrol(struct snd_soc_card *card,int count;devm_kfree (card->dev, (void *)*private_value); + +if (!w_param_text) +return ; +for (count =0 ; count < num_params; count++)devm_kfree (card->dev, (void *)w_param_text[count]);devm_kfree (card->dev, w_param_text);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 23/66 drm/omap: hdmi4_cec: Fix CEC clock handling for PM
In reply to Greg Kroah-Hartman[ Upstream commit 36a1da15b5df493241b0011d2185fdd724ac1ed1 ]
If CONFIG_OMAP4_DSS_HDMI_CEC is enabled in .config, deeper SoC idle states are blocked because the CEC clock gets always enabled on init.
Let's fix the issue by moving the CEC clock handling to happen later in hdmi_cec_adap_enable() as suggested by Hans Verkuil <[email protected]>. This way the CEC clock gets only enabled when needed. This can be tested by doing cec-ctl --playback to enable the CEC, and doing cec-ctl --clear to disable it.
Let's also fix the typo for "divider" in the comments while at it.
--- drivers/gpu/drm/omapdrm/dss/hdmi4_cec.c | 26 ++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-)
drivers/gpu/drm/omapdrm/dss/hdmi4_cec.c +19 -7
@@ -175,6 +175,7 @@ static int hdmi_cec_adap_enable(struct cec_adapter *adap, bool enable)REG_FLD_MOD (core->base,HDMI_CORE_SYS_INTR_UNMASK4 ,0 ,3 ,3 );hdmi_wp_clear_irqenable (core->wp,HDMI_IRQ_CORE );hdmi_wp_set_irqstatus (core->wp,HDMI_IRQ_CORE ); +REG_FLD_MOD (core->wp->base,HDMI_WP_CLK ,0 ,5 ,0 );hdmi4_core_disable (core);return 0 ; }
@@ -182,16 +183,24 @@ static int hdmi_cec_adap_enable(struct cec_adapter *adap, bool enable)if (err)return err; +/* +* Initialize CEC clock divider: CEC needs 2MHz clock hence +* set the divider to 24 to get 48/24=2MHz clock +*/ +REG_FLD_MOD (core->wp->base,HDMI_WP_CLK ,0x18 ,5 ,0 ); +/* Clear TX FIFO */ if (!hdmi_cec_clear_tx_fifo (adap)) {pr_err ("cec-%s: could not clear TX FIFO\n" , adap->name); -return -EIO ; + err = -EIO ; + goto err_disable_clk; }/* Clear RX FIFO */ if (!hdmi_cec_clear_rx_fifo (adap)) {pr_err ("cec-%s: could not clear RX FIFO\n" , adap->name); -return -EIO ; + err = -EIO ; + goto err_disable_clk; }/* Clear CEC interrupts */
@@ -236,6 +245,12 @@ static int hdmi_cec_adap_enable(struct cec_adapter *adap, bool enable)hdmi_write_reg (core->base,HDMI_CEC_INT_STATUS_1 , temp); }return 0 ; + +err_disable_clk: +REG_FLD_MOD (core->wp->base,HDMI_WP_CLK ,0 ,5 ,0 ); +hdmi4_core_disable (core); + +return err; }static int hdmi_cec_adap_log_addr (struct cec_adapter *adap,u8 log_addr)
@@ -333,11 +348,8 @@ int hdmi4_cec_init(struct platform_device *pdev, struct hdmi_core_data *core,return ret; core->wp = wp; -/* -* Initialize CEC clock divider: CEC needs 2MHz clock hence -* set the devider to 24 to get 48/24=2MHz clock -*/ -REG_FLD_MOD (core->wp->base,HDMI_WP_CLK ,0x18 ,5 ,0 ); +/* Disable clock initially, hdmi_cec_adap_enable() manages it */ +REG_FLD_MOD (core->wp->base,HDMI_WP_CLK ,0 ,5 ,0 ); ret =cec_register_adapter (core->adap, &pdev->dev);if (ret <0 ) {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 24/66 IB/hfi1: Eliminate opcode tests on mr deref
In reply to Greg Kroah-Hartman[ Upstream commit a8639a79e85c18c16c10089edd589c7948f19bbd ]
When an old ack_queue entry is used to store an incoming request, it may need to clean up the old entry if it is still referencing the MR. Originally only RDMA READ request needed to reference MR on the responder side and therefore the opcode was tested when cleaning up the old entry. The introduction of tid rdma specific operations in the ack_queue makes the specific opcode tests wrong. Multiple opcodes (RDMA READ, TID RDMA READ, and TID RDMA WRITE) may need MR ref cleanup.
Remove the opcode specific tests associated with the ack_queue.
--- drivers/infiniband/hw/hfi1/rc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/infiniband/hw/hfi1/rc.c +2 -2
@@ -2303,7 +2303,7 @@ void hfi1_rc_rcv(struct hfi1_packet *packet)update_ack_queue (qp, next); } e = &qp->s_ack_queue[qp->r_head_ack_queue]; -if (e->opcode ==OP (RDMA_READ_REQUEST ) && e->rdma_sge.mr) { +if (e->rdma_sge.mr) {rvt_put_mr (e->rdma_sge.mr); e->rdma_sge.mr =NULL ; }
@@ -2377,7 +2377,7 @@ void hfi1_rc_rcv(struct hfi1_packet *packet)update_ack_queue (qp, next); } e = &qp->s_ack_queue[qp->r_head_ack_queue]; -if (e->opcode ==OP (RDMA_READ_REQUEST ) && e->rdma_sge.mr) { +if (e->rdma_sge.mr) {rvt_put_mr (e->rdma_sge.mr); e->rdma_sge.mr =NULL ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 25/66 IB/hfi1: Fix the allocation of RSM table
In reply to Greg Kroah-Hartman[ Upstream commit d0294344470e6b52d097aa7369173f32d11f2f52 ]
The receive side mapping (RSM) on hfi1 hardware is a special matching mechanism to direct an incoming packet to a given hardware receive context. It has 4 instances of matching capabilities (RSM0 - RSM3) that share the same RSM table (RMT). The RMT has a total of 256 entries, each of which points to a receive context.
Currently, three instances of RSM have been used:
1. RSM0 by QOS;
2. RSM1 by PSM FECN;
3. RSM2 by VNIC.
Each RSM instance should reserve enough entries in RMT to function properly. Since both PSM and VNIC could allocate any receive context between dd->first_dyn_alloc_ctxt and dd->num_rcv_contexts, PSM FECN must reserve enough RMT entries to cover the entire receive context index range (dd->num_rcv_contexts - dd->first_dyn_alloc_ctxt) instead of only the user receive contexts allocated for PSM (dd->num_user_contexts). Consequently, the sizing of dd->num_user_contexts in set_up_context_variables is incorrect.
--- drivers/infiniband/hw/hfi1/chip.c | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-)
drivers/infiniband/hw/hfi1/chip.c +19 -7
@@ -13388,7 +13388,7 @@ static int set_up_context_variables(struct hfi1_devdata *dd)int total_contexts;int ret;unsigned ngroups; -int qos_rmt_count; +int rmt_count;int user_rmt_reduced;u32 n_usr_ctxts;u32 send_contexts =chip_send_contexts (dd);
@@ -13450,10 +13450,20 @@ static int set_up_context_variables(struct hfi1_devdata *dd) n_usr_ctxts = rcv_contexts - total_contexts; } -/* each user context requires an entry in the RMT */ - qos_rmt_count =qos_rmt_entries (dd,NULL ,NULL ); -if (qos_rmt_count + n_usr_ctxts >NUM_MAP_ENTRIES ) { - user_rmt_reduced =NUM_MAP_ENTRIES - qos_rmt_count; +/* +* The RMT entries are currently allocated as shown below: +* 1. QOS (0 to 128 entries); +* 2. FECN for PSM (num_user_contexts + num_vnic_contexts); +* 3. VNIC (num_vnic_contexts). +* It should be noted that PSM FECN oversubscribe num_vnic_contexts +* entries of RMT because both VNIC and PSM could allocate any receive +* context between dd->first_dyn_alloc_text and dd->num_rcv_contexts, +* and PSM FECN must reserve an RMT entry for each possible PSM receive +* context. +*/ + rmt_count =qos_rmt_entries (dd,NULL ,NULL ) + (num_vnic_contexts *2 ); +if (rmt_count + n_usr_ctxts >NUM_MAP_ENTRIES ) { + user_rmt_reduced =NUM_MAP_ENTRIES - rmt_count; dd_dev_err(dd, "RMT size is reducing the number of user receive contexts from %u to %d\n", n_usr_ctxts,
@@ -14441,9 +14451,11 @@ static void init_user_fecn_handling(struct hfi1_devdata *dd,u64 reg;int i, idx, regoff, regidx;u8 offset; +u32 total_cnt;/* there needs to be enough room in the map table */ -if (rmt->used + dd->num_user_contexts >=NUM_MAP_ENTRIES ) { + total_cnt = dd->num_rcv_contexts - dd->first_dyn_alloc_ctxt; +if (rmt->used + total_cnt >=NUM_MAP_ENTRIES ) {dd_dev_err (dd,"User FECN handling disabled - too many user contexts allocated\n" );return ; }
@@ -14497,7 +14509,7 @@ static void init_user_fecn_handling(struct hfi1_devdata *dd,/* add rule 1 */ add_rsm_rule (dd,RSM_INS_FECN , &rrd); - rmt->used += dd->num_user_contexts; + rmt->used += total_cnt; }/* Initialize RSM for VNIC */
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 27/66 ASoC: tlv320aic32x4: Fix Common Pins
In reply to Greg Kroah-Hartman[ Upstream commit c63adb28f6d913310430f14c69f0a2ea55eed0cc ]
The common pins were mistakenly not added to the DAPM graph. Adding these pins will allow valid graphs to be created.
--- sound/soc/codecs/tlv320aic32x4.c | 2 ++ 1 file changed, 2 insertions(+)
sound/soc/codecs/tlv320aic32x4.c +2 -0
@@ -462,6 +462,8 @@ static const struct snd_soc_dapm_widget aic32x4_dapm_widgets[] = {SND_SOC_DAPM_INPUT ("IN2_R" ),SND_SOC_DAPM_INPUT ("IN3_L" ),SND_SOC_DAPM_INPUT ("IN3_R" ), +SND_SOC_DAPM_INPUT ("CM_L" ), + SND_SOC_DAPM_INPUT("CM_R"), }; static const struct snd_soc_dapm_route aic32x4_dapm_routes[] = {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 10/66 ASoC: stm32: sai: fix exposed capabilities in spdif mode
In reply to Greg Kroah-Hartman[ Upstream commit b8468192971807c43a80d6e2c41f83141cb7b211 ]
Change capabilities exposed in SAI S/PDIF mode, to match actually supported formats.
In S/PDIF mode only 32 bits stereo is supported.
--- sound/soc/stm/stm32_sai_sub.c | 8 ++++++++ 1 file changed, 8 insertions(+)
sound/soc/stm/stm32_sai_sub.c +8 -0
@@ -498,6 +498,14 @@ static int stm32_sai_startup(struct snd_pcm_substream *substream, sai->substream = substream; +if (STM_SAI_PROTOCOL_IS_SPDIF (sai)) { +snd_pcm_hw_constraint_mask64 (substream->runtime, +SNDRV_PCM_HW_PARAM_FORMAT , +SNDRV_PCM_FMTBIT_S32_LE ); +snd_pcm_hw_constraint_single (substream->runtime, +SNDRV_PCM_HW_PARAM_CHANNELS ,2 ); + } + ret =clk_prepare_enable (sai->sai_ck);if (ret <0 ) {dev_err (cpu_dai->dev,"Failed to enable clock: %d\n" , ret);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 29/66 perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS
In reply to Greg Kroah-Hartman[ Upstream commit 583feb08e7f7ac9d533b446882eb3a54737a6dbb ]
When an event is programmed with attr.wakeup_events=N (N>0), it means the caller is interested in getting a user level notification after N samples have been recorded in the kernel sampling buffer.
With precise events on Intel processors, the kernel uses PEBS. The kernel tries minimize sampling overhead by verifying
if the event configuration is compatible with multi-entry PEBS mode. If so, the kernel is notified only when the buffer has reached its threshold. Other PEBS operates in single-entry mode, the kenrel is notified for each PEBS sample.
The problem is that the current implementation look at frequency mode and event sample_type but ignores the wakeup_events field. Thus, it may not be possible to receive a notification after each precise event.
This patch fixes this problem by disabling multi-entry PEBS if wakeup_events is non-zero.
--- arch/x86/events/intel/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/events/intel/core.c +1 -1
@@ -3068,7 +3068,7 @@ static int intel_pmu_hw_config(struct perf_event *event)return ret;if (event->attr.precise_ip) { -if (!event->attr.freq) { +if (!(event->attr.freq || event->attr.wakeup_events)) { event->hw.flags |=PERF_X86_EVENT_AUTO_RELOAD ;if (!(event->attr.sample_type & ~intel_pmu_large_pebs_flags (event)))
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 30/66 perf/x86/intel: Initialize TFA MSR
In reply to Greg Kroah-Hartman[ Upstream commit d7262457e35dbe239659e62654e56f8ddb814bed ]
Stephane reported that the TFA MSR is not initialized by the kernel, but the TFA bit could set by firmware or as a leftover from a kexec, which makes the state inconsistent.
--- arch/x86/events/intel/core.c | 6 ++++++ 1 file changed, 6 insertions(+)
arch/x86/events/intel/core.c +6 -0
@@ -3447,6 +3447,12 @@ static void intel_pmu_cpu_starting(int cpu) cpuc->lbr_sel =NULL ; +if (x86_pmu.flags &PMU_FL_TFA ) { +WARN_ON_ONCE (cpuc->tfa_shadow); + cpuc->tfa_shadow = ~0ULL ; +intel_set_tfa (cpuc, false); + } +if (x86_pmu.version >1 )flip_smm_bit (&x86_pmu.attr_freeze_on_smi);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 32/66 xtensa: fix initialization of pt_regs::syscall in start_thread
In reply to Greg Kroah-Hartman[ Upstream commit 2663147dc7465cb29040a05cc4286fdd839978b5 ]
New pt_regs should indicate that there's no syscall, not that there's syscall #0. While at it wrap macro body in do/while and parenthesize macro arguments.
--- arch/xtensa/include/asm/processor.h | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)
arch/xtensa/include/asm/processor.h +12 -9
@@ -194,15 +194,18 @@ struct thread_struct {/* Clearing a0 terminates the backtrace. */ #define start_thread (regs, new_pc, new_sp) \ - memset(regs, 0, sizeof(*regs)); \ - regs->pc = new_pc; \ - regs->ps = USER_PS_VALUE; \ - regs->areg[1] = new_sp; \ - regs->areg[0] = 0; \ - regs->wmask = 1; \ - regs->depc = 0; \ - regs->windowbase = 0; \ - regs->windowstart = 1; + do { \ + memset((regs), 0, sizeof(*(regs))); \ + (regs)->pc = (new_pc); \ + (regs)->ps = USER_PS_VALUE; \ + (regs)->areg[1] = (new_sp); \ + (regs)->areg[0] = 0; \ + (regs)->wmask = 1; \ + (regs)->depc = 0; \ + (regs)->windowbase = 0; \ + (regs)->windowstart = 1; \ + (regs)->syscall = NO_SYSCALL; \ + } while (0)/* Forward declaration */ struct task_struct ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 33/66 ASoC: rockchip: pdm: fix regmap_ops hang issue
In reply to Greg Kroah-Hartman[ Upstream commit c85064435fe7a216ec0f0238ef2b8f7cd850a450 ]
This is because set_fmt ops maybe called when PD is off, and in such case, regmap_ops will lead system hang. enale PD before doing regmap_ops.
--- sound/soc/rockchip/rockchip_pdm.c | 2 ++ 1 file changed, 2 insertions(+)
sound/soc/rockchip/rockchip_pdm.c +2 -0
@@ -208,7 +208,9 @@ static int rockchip_pdm_set_fmt(struct snd_soc_dai *cpu_dai,return -EINVAL ; } +pm_runtime_get_sync (cpu_dai->dev);regmap_update_bits (pdm->regmap,PDM_CLK_CTRL , mask, val); +pm_runtime_put (cpu_dai->dev);return 0 ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 34/66 drm/amd/display: fix cursor black issue
In reply to Greg Kroah-Hartman[ Upstream commit c1cefe115d1cdc460014483319d440b2f0d07c68 ]
[Why]
the member sdr_white_level of struct dc_cursor_attributes was not initialized, then the random value result that dcn10_set_cursor_sdr_white_level() set error hw_scale value 0x20D9(normal value is 0x3c00), this cause the black cursor issue.
[how]
just initilize the obj of struct dc_cursor_attributes to zero to avoid the random value.
--- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +1 -0
@@ -4028,6 +4028,7 @@ static void handle_cursor_update(struct drm_plane *plane, amdgpu_crtc->cursor_width = plane->state->crtc_w; amdgpu_crtc->cursor_height = plane->state->crtc_h; +memset (&attributes,0 ,sizeof (attributes)); attributes.address.high_part =upper_32_bits (address); attributes.address.low_part =lower_32_bits (address); attributes.width = plane->state->crtc_w;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 35/66 ASoC: cs35l35: Disable regulators on driver removal
In reply to Greg Kroah-Hartman[ Upstream commit 47c4cc08cb5b34e93ab337b924c5ede77ca3c936 ]
The chips main power supplies VA and VP are enabled during probe but then never disabled, this will cause warnings from the regulator framework on driver removal. Fix this by adding a remove callback and disabling the supplies, whilst doing so follow best practice and put the chip back into reset as well.
--- sound/soc/codecs/cs35l35.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
sound/soc/codecs/cs35l35.c +11 -0
@@ -1634,6 +1634,16 @@ static int cs35l35_i2c_probe(struct i2c_client *i2c_client,return ret; } +static int cs35l35_i2c_remove (struct i2c_client *i2c_client) +{ +struct cs35l35_private *cs35l35 =i2c_get_clientdata (i2c_client); + +regulator_bulk_disable (cs35l35->num_supplies, cs35l35->supplies); +gpiod_set_value_cansleep (cs35l35->reset_gpio,0 ); + +return 0 ; +} +static const struct of_device_id cs35l35_of_match[] = { {.compatible ="cirrus,cs35l35" }, {},
@@ -1654,6 +1664,7 @@ static struct i2c_driver cs35l35_i2c_driver = { }, .id_table = cs35l35_id, .probe = cs35l35_i2c_probe, + .remove = cs35l35_i2c_remove, };module_i2c_driver (cs35l35_i2c_driver);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 37/66 slab: fix a crash by reading /proc/slab_allocators
In reply to Greg Kroah-Hartman[ Upstream commit fcf88917dd435c6a4cb2830cb086ee58605a1d85 ]
The commit 510ded33e075 ("slab: implement slab_root_caches list") changes the name of the list node within "struct kmem_cache" from "list" to "root_caches_node", but leaks_show() still use the "list" which causes a crash when reading /proc/slab_allocators.
You need to have CONFIG_SLAB=y and CONFIG_MEMCG=y to see the problem, because without MEMCG all slab caches are root caches, and the "list" node happens to be the right one.
--- mm/slab.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
mm/slab.c +2 -1
@@ -4305,7 +4305,8 @@ static void show_symbol(struct seq_file *m, unsigned long address)static int leaks_show (struct seq_file *m,void *p) { - struct kmem_cache *cachep = list_entry(p, struct kmem_cache, list); + struct kmem_cache *cachep = list_entry(p, struct kmem_cache, + root_caches_node);struct page *page;struct kmem_cache_node *n;const char *name;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 38/66 drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind
In reply to Greg Kroah-Hartman[ Upstream commit 1a07a94b47b1f528f39c3e6187b5eaf02efe44ea ]
There are two problems here:
1. Not all clk_data->hws[] need to be initialized, depending on various configured quirks. This leads to NULL ptr deref in clk_hw_unregister_gate() in sun8i_tcon_top_unbind()
2. If there is error when registering the clk_data->hws[], err_unregister_gates error path will try to unregister IS_ERR()=true (invalid) pointer.
For problem (1) I have this stack trace:
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 Call trace: clk_hw_unregister+0x8/0x18 clk_hw_unregister_gate+0x14/0x28 sun8i_tcon_top_unbind+0x2c/0x60 component_unbind.isra.4+0x2c/0x50 component_bind_all+0x1d4/0x230 sun4i_drv_bind+0xc4/0x1a0 try_to_bring_up_master+0x164/0x1c0 __component_add+0xa0/0x168 component_add+0x10/0x18 sun8i_dw_hdmi_probe+0x18/0x20 platform_drv_probe+0x3c/0x70 really_probe+0xcc/0x278 driver_probe_device+0x34/0xa8
Problem (2) was identified by head scratching.
--- drivers/gpu/drm/sun4i/sun8i_tcon_top.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/gpu/drm/sun4i/sun8i_tcon_top.c +3 -2
@@ -217,7 +217,7 @@ static int sun8i_tcon_top_bind(struct device *dev, struct device *master, err_unregister_gates:for (i =0 ; i <CLK_NUM ; i++) -if (clk_data->hws[i]) +if (!IS_ERR_OR_NULL (clk_data->hws[i]))clk_hw_unregister_gate (clk_data->hws[i]);clk_disable_unprepare (tcon_top->bus); err_assert_reset:
@@ -235,7 +235,8 @@ static void sun8i_tcon_top_unbind(struct device *dev, struct device *master,of_clk_del_provider (dev->of_node);for (i =0 ; i <CLK_NUM ; i++) -clk_hw_unregister_gate (clk_data->hws[i]); +if (clk_data->hws[i]) +clk_hw_unregister_gate (clk_data->hws[i]);clk_disable_unprepare (tcon_top->bus);reset_control_assert (tcon_top->rst);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 39/66 virtio_pci: fix a NULL pointer reference in vp_del_vqs
In reply to Greg Kroah-Hartman[ Upstream commit 6a8aae68c87349dbbcd46eac380bc43cdb98a13b ]
If the msix_affinity_masks is alloced failed, then we'll try to free some resources in vp_free_vectors() that may access it directly.
We met the following stack in our production:
[ 29.296767] BUG: unable to handle kernel NULL pointer dereference at (null) [ 29.311151] IP: [<ffffffffc04fe35a>] vp_free_vectors+0x6a/0x150 [virtio_pci] [ 29.324787] PGD 0 [ 29.333224] Oops: 0000 [#1] SMP [...] [ 29.425175] RIP: 0010:[<ffffffffc04fe35a>] [<ffffffffc04fe35a>] vp_free_vectors+0x6a/0x150 [virtio_pci] [ 29.441405] RSP: 0018:ffff9a55c2dcfa10 EFLAGS: 00010206 [ 29.453491] RAX: 0000000000000000 RBX: ffff9a55c322c400 RCX: 0000000000000000 [ 29.467488] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9a55c322c400 [ 29.481461] RBP: ffff9a55c2dcfa20 R08: 0000000000000000 R09: ffffc1b6806ff020 [ 29.495427] R10: 0000000000000e95 R11: 0000000000aaaaaa R12: 0000000000000000 [ 29.509414] R13: 0000000000010000 R14: ffff9a55bd2d9e98 R15: ffff9a55c322c400 [ 29.523407] FS: 00007fdcba69f8c0(0000) GS:ffff9a55c2840000(0000) knlGS:0000000000000000 [ 29.538472] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 29.551621] CR2: 0000000000000000 CR3: 000000003ce52000 CR4: 00000000003607a0 [ 29.565886] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 29.580055] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 29.594122] Call Trace: [ 29.603446] [<ffffffffc04fe8a2>] vp_request_msix_vectors+0xe2/0x260 [virtio_pci] [ 29.618017] [<ffffffffc04fedc5>] vp_try_to_find_vqs+0x95/0x3b0 [virtio_pci] [ 29.632152] [<ffffffffc04ff117>] vp_find_vqs+0x37/0xb0 [virtio_pci] [ 29.645582] [<ffffffffc057bf63>] init_vq+0x153/0x260 [virtio_blk] [ 29.658831] [<ffffffffc057c1e8>] virtblk_probe+0xe8/0x87f [virtio_blk]
[...]
--- drivers/virtio/virtio_pci_common.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
drivers/virtio/virtio_pci_common.c +5 -3
@@ -255,9 +255,11 @@ void vp_del_vqs(struct virtio_device *vdev)for (i =0 ; i < vp_dev->msix_used_vectors; ++i)free_irq (pci_irq_vector (vp_dev->pci_dev, i), vp_dev); -for (i =0 ; i < vp_dev->msix_vectors; i++) -if (vp_dev->msix_affinity_masks[i]) -free_cpumask_var (vp_dev->msix_affinity_masks[i]); +if (vp_dev->msix_affinity_masks) { +for (i =0 ; i < vp_dev->msix_vectors; i++) +if (vp_dev->msix_affinity_masks[i]) +free_cpumask_var (vp_dev->msix_affinity_masks[i]); + }if (vp_dev->msix_enabled) {/* Disable the vector used for configuration */
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 41/66 RDMA/hns: Fix bug that caused srq creation to fail
In reply to Greg Kroah-Hartman[ Upstream commit 4772e03d239484f3461e33c79d721c8ea03f7416 ]
Due to the incorrect use of the seg and obj information, the position of the mtt is calculated incorrectly, and the free space of the page is not enough to store the entire mtt, resulting in access to the next page. This patch fixes this problem.
Unable to handle kernel paging request at virtual address ffff00006e3cd000 ... Call trace: hns_roce_write_mtt+0x154/0x2f0 [hns_roce] hns_roce_buf_write_mtt+0xa8/0xd8 [hns_roce] hns_roce_create_srq+0x74c/0x808 [hns_roce] ib_create_srq+0x28/0xc8
--- drivers/infiniband/hw/hns/hns_roce_hem.c | 6 ++++-- drivers/infiniband/hw/hns/hns_roce_mr.c | 4 ++-- 2 files changed, 6 insertions(+), 4 deletions(-)
drivers/infiniband/hw/hns/hns_roce_hem.c +4 -2
@@ -745,6 +745,8 @@ void *hns_roce_table_find(struct hns_roce_dev *hr_dev, idx_offset = (obj & (table->num_obj -1 )) % obj_per_chunk; dma_offset = offset = idx_offset * table->obj_size; }else { +u32 seg_size =64 ;/* 8 bytes per BA and 8 BA per segment */ +hns_roce_calc_hem_mhop (hr_dev, table, &mhop_obj, &mhop);/* mtt mhop */ i = mhop.l0_idx;
@@ -756,8 +758,8 @@ void *hns_roce_table_find(struct hns_roce_dev *hr_dev, hem_idx = i; hem = table->hem[hem_idx]; - dma_offset = offset = (obj & (table->num_obj -1 )) * - table->obj_size % mhop.bt_chunk_size; + dma_offset = offset = (obj & (table->num_obj -1 )) * seg_size % + mhop.bt_chunk_size;if (mhop.hop_num ==2 ) dma_offset = offset =0 ; }
drivers/infiniband/hw/hns/hns_roce_mr.c +2 -2
@@ -707,7 +707,6 @@ static int hns_roce_write_mtt_chunk(struct hns_roce_dev *hr_dev,struct hns_roce_hem_table *table;dma_addr_t dma_handle;__le64 *mtts; -u32 s = start_index *sizeof (u64);u32 bt_page_size;u32 i;
@@ -730,7 +729,8 @@ static int hns_roce_write_mtt_chunk(struct hns_roce_dev *hr_dev, table = &hr_dev->mr_table.mtt_cqe_table; mtts =hns_roce_table_find (hr_dev, table, - mtt->first_seg + s / hr_dev->caps.mtt_entry_sz, + mtt->first_seg + + start_index /HNS_ROCE_MTT_ENTRY_PER_SEG , &dma_handle);if (!mtts)return -ENOMEM ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 42/66 scsi: csiostor: fix missing data copy in csio_scsi_err_handler()
In reply to Greg Kroah-Hartman[ Upstream commit 5c2442fd78998af60e13aba506d103f7f43f8701 ]
If scsi cmd sglist is not suitable for DDP then csiostor driver uses preallocated buffers for DDP, because of this data copy is required from DDP buffer to scsi cmd sglist before calling ->scsi_done().
--- drivers/scsi/csiostor/csio_scsi.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/scsi/csiostor/csio_scsi.c +4 -1
@@ -1713,8 +1713,11 @@ csio_scsi_err_handler(struct csio_hw *hw, struct csio_ioreq *req) } out: -if (req->nsge >0 ) +if (req->nsge >0 ) {scsi_dma_unmap (cmnd); +if (req->dcopy && (host_status ==DID_OK )) + host_status =csio_scsi_copy_to_sgl (hw, req); + } cmnd->result = (((host_status) <<16 ) | scsi_status); cmnd->scsi_done (cmnd);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 12/66 ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform
In reply to Greg Kroah-Hartman[ Upstream commit c899df3e9b0bf7b76e642aed1a214582ea7012d5 ]
If playback and capture are enabled concurrently, when the capture stops the output becomes inaudile. The playback application will become stuck and underrun after a timeout.
This is caused by mistaken use of the stream_id, which should only be set for playback and not for capture
Tested on Apollolake and Kabylake with SST driver.
--- sound/soc/intel/skylake/skl-pcm.c | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-)
sound/soc/intel/skylake/skl-pcm.c +14 -5
@@ -180,6 +180,7 @@ int skl_pcm_link_dma_prepare(struct device *dev, struct skl_pipe_params *params)struct hdac_stream *hstream;struct hdac_ext_stream *stream;struct hdac_ext_link *link; +unsigned char stream_tag; hstream =snd_hdac_get_stream (bus, params->stream, params->link_dma_id +1 );
@@ -198,10 +199,13 @@ int skl_pcm_link_dma_prepare(struct device *dev, struct skl_pipe_params *params)snd_hdac_ext_link_stream_setup (stream, format_val); -list_for_each_entry (link, &bus->hlink_list, list) { -if (link->index == params->link_index) -snd_hdac_ext_link_set_stream_id (link, - hstream->stream_tag); + stream_tag = hstream->stream_tag; +if (stream->hstream.direction ==SNDRV_PCM_STREAM_PLAYBACK ) { +list_for_each_entry (link, &bus->hlink_list, list) { +if (link->index == params->link_index) +snd_hdac_ext_link_set_stream_id (link, + stream_tag); + } } stream->link_prepared =1 ;
@@ -640,6 +644,7 @@ static int skl_link_hw_free(struct snd_pcm_substream *substream,struct hdac_ext_stream *link_dev =snd_soc_dai_get_dma_data (dai, substream);struct hdac_ext_link *link; +unsigned char stream_tag;dev_dbg (dai->dev,"%s: %s\n" , __func__, dai->name);
@@ -649,7 +654,11 @@ static int skl_link_hw_free(struct snd_pcm_substream *substream,if (!link)return -EINVAL ; -snd_hdac_ext_link_clear_stream_id (link,hdac_stream (link_dev)->stream_tag); +if (substream->stream ==SNDRV_PCM_STREAM_PLAYBACK ) { + stream_tag =hdac_stream (link_dev)->stream_tag; +snd_hdac_ext_link_clear_stream_id (link, stream_tag); + } +snd_hdac_ext_stream_release (link_dev,HDAC_EXT_STREAM_TYPE_LINK );return 0 ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 14/66 ASoC: nau8810: fix the issue of widget with prefixed name
In reply to Greg Kroah-Hartman[ Upstream commit 54d1cf78b0f4ba348a7c7fb8b7d0708d71b6cc8a ]
The driver changes the stream name of DAC and ADC to avoid the issue of widget with prefixed name. When the machine adds prefixed name for codec, the stream name of DAI may not find the widgets.
--- sound/soc/codecs/nau8810.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
sound/soc/codecs/nau8810.c +2 -2
@@ -411,9 +411,9 @@ static const struct snd_soc_dapm_widget nau8810_dapm_widgets[] = {SND_SOC_DAPM_MIXER ("Mono Mixer" ,NAU8810_REG_POWER3 ,NAU8810_MOUTMX_EN_SFT ,0 , &nau8810_mono_mixer_controls[0 ],ARRAY_SIZE (nau8810_mono_mixer_controls)), -SND_SOC_DAPM_DAC ("DAC" ,"HiFi Playback" ,NAU8810_REG_POWER3 , +SND_SOC_DAPM_DAC ("DAC" ,"Playback" ,NAU8810_REG_POWER3 ,NAU8810_DAC_EN_SFT ,0 ), -SND_SOC_DAPM_ADC ("ADC" ,"HiFi Capture" ,NAU8810_REG_POWER2 , +SND_SOC_DAPM_ADC ("ADC" ,"Capture" ,NAU8810_REG_POWER2 ,NAU8810_ADC_EN_SFT ,0 ),SND_SOC_DAPM_PGA ("SpkN Out" ,NAU8810_REG_POWER3 , NAU8810_NSPK_EN_SFT, 0, NULL, 0),
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 16/66 ASoC: rt5682: recording has no sound after booting
In reply to Greg Kroah-Hartman[ Upstream commit 1c5b6a27e432e4fe170a924c8b41012271496a4c ]
If ASRC turns on, HW will use clk_dac as the reference clock whether recording or playback.
Both of clk_dac and clk_adc should set proper clock while using ASRC.
--- sound/soc/codecs/rt5682.c | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-)
sound/soc/codecs/rt5682.c +5 -9
@@ -1196,7 +1196,7 @@ static int set_filter_clk(struct snd_soc_dapm_widget *w,struct snd_soc_component *component =snd_soc_dapm_to_component (w->dapm);struct rt5682_priv *rt5682 =snd_soc_component_get_drvdata (component); -int ref, val, reg, sft, mask, idx = -EINVAL ; +int ref, val, reg, idx = -EINVAL ;static const int div_f[] = {1 ,2 ,3 ,4 ,6 ,8 ,12 ,16 ,24 ,32 ,48 };static const int div_o[] = {1 ,2 ,4 ,6 ,8 ,12 ,16 ,24 ,32 ,48 };
@@ -1210,15 +1210,10 @@ static int set_filter_clk(struct snd_soc_dapm_widget *w, idx =rt5682_div_sel (rt5682, ref, div_f,ARRAY_SIZE (div_f)); -if (w->shift ==RT5682_PWR_ADC_S1F_BIT ) { +if (w->shift ==RT5682_PWR_ADC_S1F_BIT ) reg =RT5682_PLL_TRACK_3 ; - sft =RT5682_ADC_OSR_SFT ; - mask =RT5682_ADC_OSR_MASK ; - }else { +else reg =RT5682_PLL_TRACK_2 ; - sft =RT5682_DAC_OSR_SFT ; - mask =RT5682_DAC_OSR_MASK ; - }snd_soc_component_update_bits (component, reg,RT5682_FILTER_CLK_DIV_MASK , idx <<RT5682_FILTER_CLK_DIV_SFT );
@@ -1230,7 +1225,8 @@ static int set_filter_clk(struct snd_soc_dapm_widget *w, }snd_soc_component_update_bits (component,RT5682_ADDA_CLK_1 , - mask, idx << sft); +RT5682_ADC_OSR_MASK |RT5682_DAC_OSR_MASK , + (idx <<RT5682_ADC_OSR_SFT ) | (idx <<RT5682_DAC_OSR_SFT ));return 0 ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 17/66 ASoC: wm_adsp: Add locking to wm_adsp2_bus_error
In reply to Greg Kroah-Hartman[ Upstream commit a2225a6d155fcb247fe4c6d87f7c91807462966d ]
Best to lock across handling the bus error to ensure the DSP doesn't change power state as we are reading the status registers.
--- sound/soc/codecs/wm_adsp.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
sound/soc/codecs/wm_adsp.c +8 -3
@@ -3819,11 +3819,13 @@ irqreturn_t wm_adsp2_bus_error(struct wm_adsp *dsp)struct regmap *regmap = dsp->regmap;int ret =0 ; +mutex_lock (&dsp->pwr_lock); + ret =regmap_read (regmap, dsp->base +ADSP2_LOCK_REGION_CTRL , &val);if (ret) {adsp_err (dsp,"Failed to read Region Lock Ctrl register: %d\n" , ret); -return IRQ_HANDLED ; + goto error; }if (val &ADSP2_WDT_TIMEOUT_STS_MASK ) {
@@ -3842,7 +3844,7 @@ irqreturn_t wm_adsp2_bus_error(struct wm_adsp *dsp)adsp_err (dsp,"Failed to read Bus Err Addr register: %d\n" , ret); -return IRQ_HANDLED ; + goto error; } adsp_err(dsp, "bus error address = 0x%x\n",
@@ -3855,7 +3857,7 @@ irqreturn_t wm_adsp2_bus_error(struct wm_adsp *dsp)adsp_err (dsp,"Failed to read Pmem Xmem Err Addr register: %d\n" , ret); -return IRQ_HANDLED ; + goto error; } adsp_err(dsp, "xmem error address = 0x%x\n",
@@ -3868,6 +3870,9 @@ irqreturn_t wm_adsp2_bus_error(struct wm_adsp *dsp)regmap_update_bits (regmap, dsp->base +ADSP2_LOCK_REGION_CTRL ,ADSP2_CTRL_ERR_EINT ,ADSP2_CTRL_ERR_EINT ); +error: +mutex_unlock (&dsp->pwr_lock); +return IRQ_HANDLED ; }EXPORT_SYMBOL_GPL (wm_adsp2_bus_error);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 45/66 virtio-blk: limit number of hw queues by nr_cpu_ids
In reply to Greg Kroah-Hartman[ Upstream commit bf348f9b78d413e75bb079462751a1d86b6de36c ]
When tag_set->nr_maps is 1, the block layer limits the number of hw queues by nr_cpu_ids. No matter how many hw queues are used by virtio-blk, as it has (tag_set->nr_maps == 1), it can use at most nr_cpu_ids hw queues.
In addition, specifically for pci scenario, when the 'num-queues' specified by qemu is more than maxcpus, virtio-blk would not be able to allocate more than maxcpus vectors in order to have a vector for each queue. As a result, it falls back into MSI-X with one vector for config and one shared for queues.
Considering above reasons, this patch limits the number of hw queues used by virtio-blk by nr_cpu_ids.
--- drivers/block/virtio_blk.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/block/virtio_blk.c +2 -0
@@ -446,6 +446,8 @@ static int init_vq(struct virtio_blk *vblk)if (err) num_vqs =1 ; + num_vqs = min_t(unsigned int, nr_cpu_ids, num_vqs); + vblk->vqs =kmalloc_array (num_vqs,sizeof (*vblk->vqs),GFP_KERNEL );if (!vblk->vqs)return -ENOMEM ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 54/66 usb-storage: Set virt_boundary_mask to avoid SG overflows
In reply to Greg Kroah-HartmanFrom: Alan Stern <[email protected]>
commit 747668dbc061b3e62bc1982767a3a1f9815fcf0e upstream.
The USB subsystem has always had an unusual requirement for its scatter-gather transfers: Each element in the scatterlist (except the last one) must have a length divisible by the bulk maxpacket size. This is a particular issue for USB mass storage, which uses SG lists created by the block layer rather than setting up its own.
So far we have scraped by okay because most devices have a logical block size of 512 bytes or larger, and the bulk maxpacket sizes for USB 2 and below are all <= 512. However, USB 3 has a bulk maxpacket size of 1024. Since the xhci-hcd driver includes native SG support, this hasn't mattered much. But now people are trying to use USB-3 mass storage devices with USBIP, and the vhci-hcd driver currently does not have full SG support.
The result is an overflow error, when the driver attempts to implement an SG transfer of 63 512-byte blocks as a single
3584-byte (7 blocks) transfer followed by seven 4096-byte (8 blocks) transfers. The device instead sends 31 1024-byte packets followed by a 512-byte packet, and this overruns the first SG buffer.
Ideally this would be fixed by adding better SG support to vhci-hcd. But for now it appears we can work around the problem by asking the block layer to respect the maxpacket limitation, through the use of the virt_boundary_mask.
--- drivers/usb/storage/scsiglue.c | 26 ++++++++++++-------------- 1 file changed, 12 insertions(+), 14 deletions(-)
drivers/usb/storage/scsiglue.c +12 -14
@@ -65,6 +65,7 @@ static const char* host_info(struct Scsistatic int slave_alloc (struct scsi_device *sdev) {struct us_data *us =host_to_us (sdev->host); +int maxp;/* * Set the INQUIRY transfer length to 36. We don't use any of
@@ -74,20 +75,17 @@ static int slave_alloc (struct scsi_devi sdev->inquiry_len =36 ;/* -* USB has unusual DMA-alignment requirements: Although the -* starting address of each scatter-gather element doesn't matter, -* the length of each element except the last must be divisible -* by the Bulk maxpacket value. There's currently no way to -* express this by block-layer constraints, so we'll cop out -* and simply require addresses to be aligned at 512-byte -* boundaries. This is okay since most block I/O involves -* hardware sectors that are multiples of 512 bytes in length, -* and since host controllers up through USB 2.0 have maxpacket -* values no larger than 512. -* -* But it doesn't suffice for Wireless USB, where Bulk maxpacket -* values can be as large as 2048. To make that work properly -* will require changes to the block layer. +* USB has unusual scatter-gather requirements: the length of each +* scatterlist element except the last must be divisible by the +* Bulk maxpacket value. Fortunately this value is always a +* power of 2. Inform the block layer about this requirement. +*/ + maxp =usb_maxpacket (us->pusb_dev, us->recv_bulk_pipe,0 ); +blk_queue_virt_boundary (sdev->request_queue, maxp -1 ); + +/* +* Some host controllers may have alignment requirements. +* We'll play it safe by requiring 512-byte alignment always. */ blk_queue_update_dma_alignment (sdev->request_queue, (512 -1 ));
Greg Kroah-Hartman
maintainerPATCH 55/66 intel_th: pci: Add Comet Lake support
In reply to Greg Kroah-HartmanFrom: Alexander Shishkin <[email protected]>
commit e60e9a4b231a20a199d7a61caadc48693c30d695 upstream.
This adds support for Intel TH on Comet Lake.
--- drivers/hwtracing/intel_th/pci.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/hwtracing/intel_th/pci.c +5 -0
@@ -165,6 +165,11 @@ static const struct pci_device_id intel_ PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x34a6), .driver_data = (kernel_ulong_t)&intel_th_2x, }, + { +/* Comet Lake */ + PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x02a6), + .driver_data = (kernel_ulong_t)&intel_th_2x, + }, { 0 }, };
Greg Kroah-Hartman
maintainerPATCH 56/66 cpufreq: armada-37xx: fix frequency calculation for opp
In reply to Greg Kroah-HartmanFrom: Gregory CLEMENT <[email protected]>
commit 8db82563451f976597ab7b282ec655e4390a4088 upstream.
The frequency calculation was based on the current(max) frequency of the CPU. However for low frequency, the value used was already the parent frequency divided by a factor of 2.
Instead of using this frequency, this fix directly get the frequency from the parent clock.
--- drivers/cpufreq/armada-37xx-cpufreq.c | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-)
drivers/cpufreq/armada-37xx-cpufreq.c +19 -3
@@ -359,11 +359,11 @@ static int __init armada37xx_cpufreq_dristruct armada_37xx_dvfs *dvfs;struct platform_device *pdev;unsigned long freq; -unsigned int cur_frequency; +unsigned int cur_frequency, base_frequency;struct regmap *nb_pm_base, *avs_base;struct device *cpu_dev;int load_lvl, ret; -struct clk *clk; +struct clk *clk, *parent; nb_pm_base =syscon_regmap_lookup_by_compatible ("marvell,armada-3700-nb-pm" );
@@ -399,6 +399,22 @@ static int __init armada37xx_cpufreq_drireturn PTR_ERR (clk); } + parent =clk_get_parent (clk); +if (IS_ERR (parent)) { +dev_err (cpu_dev,"Cannot get parent clock for CPU0\n" ); +clk_put (clk); +return PTR_ERR (parent); + } + +/* Get parent CPU frequency */ + base_frequency =clk_get_rate (parent); + +if (!base_frequency) { +dev_err (cpu_dev,"Failed to get parent clock rate for CPU\n" ); +clk_put (clk); +return -EINVAL ; + } +/* Get nominal (current) CPU frequency */ cur_frequency =clk_get_rate (clk);if (!cur_frequency) {
@@ -431,7 +447,7 @@ static int __init armada37xx_cpufreq_drifor (load_lvl =ARMADA_37XX_DVFS_LOAD_0 ; load_lvl <LOAD_LEVEL_NR ; load_lvl++) {unsigned long u_volt = avs_map[dvfs->avs[load_lvl]] *1000 ; - freq = cur_frequency / dvfs->divider[load_lvl]; + freq = base_frequency / dvfs->divider[load_lvl]; ret =dev_pm_opp_add (cpu_dev, freq, u_volt);if (ret) goto remove_opp;
Greg Kroah-Hartman
maintainerPATCH 58/66 scsi: lpfc: change snprintf to scnprintf for possible overflow
In reply to Greg Kroah-HartmanFrom: Silvio Cesare <[email protected]>
commit e7f7b6f38a44697428f5a2e7c606de028df2b0e3 upstream.
Change snprintf to scnprintf. There are generally two cases where using snprintf causes problems.
1) Uses of size += snprintf(buf, SIZE - size, fmt, ...)
In this case, if snprintf would have written more characters than what the buffer size (SIZE) is, then size will end up larger than SIZE. In later uses of snprintf, SIZE - size will result in a negative number, leading to problems. Note that size might already be too large by using size = snprintf before the code reaches a case of size += snprintf.
2) If size is ultimately used as a length parameter for a copy back to user space, then it will potentially allow for a buffer overflow and information disclosure when size is greater than SIZE. When the size is used to index the buffer directly, we can have memory corruption. This also means when size = snprintf... is used, it may also cause problems since size may become large. Copying to userspace is mitigated by the HARDENED_USERCOPY kernel configuration.
The solution to these issues is to use scnprintf which returns the number of characters actually written to the buffer, so the size variable will never exceed SIZE.
--- drivers/scsi/lpfc/lpfc_attr.c | 180 +++++++-------- drivers/scsi/lpfc/lpfc_ct.c | 12 - drivers/scsi/lpfc/lpfc_debugfs.c | 453 +++++++++++++++++++-------------------- drivers/scsi/lpfc/lpfc_debugfs.h | 6 4 files changed, 329 insertions(+), 322 deletions(-)
drivers/scsi/lpfc/lpfc_attr.c +92 -88
@@ -117,7 +117,7 @@ static ssize_t lpfc_drvr_version_show(struct device *dev, struct device_attribute *attr, char *buf) { - return snprintf(buf, PAGE_SIZE, LPFC_MODULE_DESC "\n"); + return scnprintf(buf, PAGE_SIZE, LPFC_MODULE_DESC "\n"); }/**
@@ -137,9 +137,9 @@ lpfc_enable_fip_show(struct device *dev,struct lpfc_hba *phba = vport->phba;if (phba->hba_flag &HBA_FIP_SUPPORT ) -return snprintf (buf,PAGE_SIZE ,"1\n" ); +return scnprintf (buf,PAGE_SIZE ,"1\n" );else -return snprintf (buf,PAGE_SIZE ,"0\n" ); +return scnprintf (buf,PAGE_SIZE ,"0\n" ); } static ssize_t
@@ -517,14 +517,15 @@ lpfc_bg_info_show(struct device *dev, ststruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -if (phba->cfg_enable_bg) +if (phba->cfg_enable_bg) {if (phba->sli3_options &LPFC_SLI3_BG_ENABLED ) -return snprintf (buf,PAGE_SIZE ,"BlockGuard Enabled\n" ); +return scnprintf (buf,PAGE_SIZE , +"BlockGuard Enabled\n" );else -return snprintf (buf,PAGE_SIZE , +return scnprintf (buf,PAGE_SIZE ,"BlockGuard Not Supported\n" ); -else -return snprintf (buf,PAGE_SIZE , + }else +return scnprintf (buf,PAGE_SIZE ,"BlockGuard Disabled\n" ); }
@@ -536,7 +537,7 @@ lpfc_bg_guard_err_show(struct device *destruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%llu\n" , +return scnprintf (buf,PAGE_SIZE ,"%llu\n" , (unsigned long long )phba->bg_guard_err_cnt); }
@@ -548,7 +549,7 @@ lpfc_bg_apptag_err_show(struct device *dstruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%llu\n" , +return scnprintf (buf,PAGE_SIZE ,"%llu\n" , (unsigned long long )phba->bg_apptag_err_cnt); }
@@ -560,7 +561,7 @@ lpfc_bg_reftag_err_show(struct device *dstruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%llu\n" , +return scnprintf (buf,PAGE_SIZE ,"%llu\n" , (unsigned long long )phba->bg_reftag_err_cnt); }
@@ -578,7 +579,7 @@ lpfc_info_show(struct device *dev, struc {struct Scsi_Host *host =class_to_shost (dev); -return snprintf (buf,PAGE_SIZE ,"%s\n" ,lpfc_info (host)); +return scnprintf (buf,PAGE_SIZE ,"%s\n" ,lpfc_info (host)); }/**
@@ -597,7 +598,7 @@ lpfc_serialnum_show(struct device *dev,struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%s\n" ,phba->SerialNumber); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , phba->SerialNumber); }/**
@@ -619,7 +620,7 @@ lpfc_temp_sensor_show(struct device *devstruct Scsi_Host *shost =class_to_shost (dev);struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" ,phba->temp_sensor_support); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->temp_sensor_support); }/**
@@ -638,7 +639,7 @@ lpfc_modeldesc_show(struct device *dev,struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%s\n" ,phba->ModelDesc); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , phba->ModelDesc); }/**
@@ -657,7 +658,7 @@ lpfc_modelname_show(struct device *dev,struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%s\n" ,phba->ModelName); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , phba->ModelName); }/**
@@ -676,7 +677,7 @@ lpfc_programtype_show(struct device *devstruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%s\n" ,phba->ProgramType); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , phba->ProgramType); }/**
@@ -694,7 +695,7 @@ lpfc_mlomgmt_show(struct device *dev, ststruct lpfc_vport *vport = (struct lpfc_vport *)shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" , +return scnprintf (buf,PAGE_SIZE ,"%d\n" , (phba->sli.sli_flag &LPFC_MENLO_MAINT )); }
@@ -714,7 +715,7 @@ lpfc_vportnum_show(struct device *dev, sstruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%s\n" ,phba->Port); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , phba->Port); }/**
@@ -742,10 +743,10 @@ lpfc_fwrev_show(struct device *dev, stru sli_family = phba->sli4_hba.pc_sli4_params.sli_family;if (phba->sli_rev <LPFC_SLI_REV4 ) - len =snprintf (buf,PAGE_SIZE ,"%s, sli-%d\n" , + len =scnprintf (buf,PAGE_SIZE ,"%s, sli-%d\n" , fwrev, phba->sli_rev);else - len =snprintf (buf,PAGE_SIZE ,"%s, sli-%d:%d:%x\n" , + len =scnprintf (buf,PAGE_SIZE ,"%s, sli-%d:%d:%x\n" , fwrev, phba->sli_rev, if_type, sli_family);return len;
@@ -769,7 +770,7 @@ lpfc_hdw_show(struct device *dev, structlpfc_vpd_t *vp = &phba->vpd;lpfc_jedec_to_ascii (vp->rev.biuRev, hdw); -return snprintf (buf,PAGE_SIZE ,"%s\n" , hdw); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , hdw); }/**
@@ -790,10 +791,11 @@ lpfc_option_rom_version_show(struct devichar fwrev[FW_REV_STR_SIZE ];if (phba->sli_rev <LPFC_SLI_REV4 ) -return snprintf (buf,PAGE_SIZE ,"%s\n" , phba->OptionROMVersion); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , + phba->OptionROMVersion);lpfc_decode_firmware_rev (phba, fwrev,1 ); -return snprintf (buf,PAGE_SIZE ,"%s\n" , fwrev); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , fwrev); }/**
@@ -824,20 +826,20 @@ lpfc_link_state_show(struct device *dev,case LPFC_LINK_DOWN :case LPFC_HBA_ERROR :if (phba->hba_flag &LINK_DISABLED ) - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len,"Link Down - User disabled\n" );else - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len,"Link Down\n" );break ;case LPFC_LINK_UP :case LPFC_CLEAR_LA :case LPFC_HBA_READY : - len +=snprintf (buf + len,PAGE_SIZE -len,"Link Up - " ); + len +=scnprintf (buf + len,PAGE_SIZE -len,"Link Up - " );switch (vport->port_state) {case LPFC_LOCAL_CFG_LINK : - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len,"Configuring Link\n" );break ;case LPFC_FDISC :
@@ -847,38 +849,40 @@ lpfc_link_state_show(struct device *dev,case LPFC_NS_QRY :case LPFC_BUILD_DISC_LIST :case LPFC_DISC_AUTH : - len +=snprintf (buf + len,PAGE_SIZE - len, + len +=scnprintf (buf + len,PAGE_SIZE - len,"Discovery\n" );break ;case LPFC_VPORT_READY : - len +=snprintf (buf + len,PAGE_SIZE - len,"Ready\n" ); + len +=scnprintf (buf + len,PAGE_SIZE - len, +"Ready\n" );break ;case LPFC_VPORT_FAILED : - len +=snprintf (buf + len,PAGE_SIZE - len,"Failed\n" ); + len +=scnprintf (buf + len,PAGE_SIZE - len, +"Failed\n" );break ;case LPFC_VPORT_UNKNOWN : - len +=snprintf (buf + len,PAGE_SIZE - len, + len +=scnprintf (buf + len,PAGE_SIZE - len,"Unknown\n" );break ; }if (phba->sli.sli_flag &LPFC_MENLO_MAINT ) - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len," Menlo Maint Mode\n" );else if (phba->fc_topology ==LPFC_TOPOLOGY_LOOP ) {if (vport->fc_flag &FC_PUBLIC_LOOP ) - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len," Public Loop\n" );else - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len," Private Loop\n" ); }else {if (vport->fc_flag &FC_FABRIC ) - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len," Fabric\n" );else - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len," Point-2-Point\n" ); } }
@@ -903,15 +907,15 @@ lpfc_sli4_protocol_show(struct device *dstruct lpfc_hba *phba = vport->phba;if (phba->sli_rev <LPFC_SLI_REV4 ) -return snprintf (buf,PAGE_SIZE ,"fc\n" ); +return scnprintf (buf,PAGE_SIZE ,"fc\n" );if (phba->sli4_hba.lnk_info.lnk_dv ==LPFC_LNK_DAT_VAL ) {if (phba->sli4_hba.lnk_info.lnk_tp ==LPFC_LNK_TYPE_GE ) -return snprintf (buf,PAGE_SIZE ,"fcoe\n" ); +return scnprintf (buf,PAGE_SIZE ,"fcoe\n" );if (phba->sli4_hba.lnk_info.lnk_tp ==LPFC_LNK_TYPE_FC ) -return snprintf (buf,PAGE_SIZE ,"fc\n" ); +return scnprintf (buf,PAGE_SIZE ,"fc\n" ); } -return snprintf (buf,PAGE_SIZE ,"unknown\n" ); +return scnprintf (buf,PAGE_SIZE ,"unknown\n" ); }/**
@@ -931,7 +935,7 @@ lpfc_oas_supported_show(struct device *dstruct lpfc_vport *vport = (struct lpfc_vport *)shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" , +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->sli4_hba.pc_sli4_params.oas_supported); }
@@ -989,7 +993,7 @@ lpfc_num_discovered_ports_show(struct destruct Scsi_Host *shost =class_to_shost (dev);struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata; -return snprintf (buf,PAGE_SIZE ,"%d\n" , +return scnprintf (buf,PAGE_SIZE ,"%d\n" , vport->fc_map_cnt + vport->fc_unmap_cnt); }
@@ -1427,7 +1431,7 @@ lpfc_nport_evt_cnt_show(struct device *dstruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" , phba->nport_event_cnt); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->nport_event_cnt); }/**
@@ -1456,7 +1460,7 @@ lpfc_board_mode_show(struct device *dev,else state ="online" ; -return snprintf (buf,PAGE_SIZE ,"%s\n" , state); +return scnprintf (buf,PAGE_SIZE ,"%s\n" , state); }/**
@@ -1669,8 +1673,8 @@ lpfc_max_rpi_show(struct device *dev, stuint32_t cnt;if (lpfc_get_hba_info (phba,NULL ,NULL , &cnt,NULL ,NULL ,NULL )) -return snprintf (buf,PAGE_SIZE ,"%d\n" , cnt); -return snprintf (buf,PAGE_SIZE ,"Unknown\n" ); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , cnt); +return scnprintf (buf,PAGE_SIZE ,"Unknown\n" ); }/**
@@ -1697,8 +1701,8 @@ lpfc_used_rpi_show(struct device *dev, suint32_t cnt, acnt;if (lpfc_get_hba_info (phba,NULL ,NULL , &cnt, &acnt,NULL ,NULL )) -return snprintf (buf,PAGE_SIZE ,"%d\n" , (cnt - acnt)); -return snprintf (buf,PAGE_SIZE ,"Unknown\n" ); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , (cnt - acnt)); +return scnprintf (buf,PAGE_SIZE ,"Unknown\n" ); }/**
@@ -1725,8 +1729,8 @@ lpfc_max_xri_show(struct device *dev, stuint32_t cnt;if (lpfc_get_hba_info (phba, &cnt,NULL ,NULL ,NULL ,NULL ,NULL )) -return snprintf (buf,PAGE_SIZE ,"%d\n" , cnt); -return snprintf (buf,PAGE_SIZE ,"Unknown\n" ); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , cnt); +return scnprintf (buf,PAGE_SIZE ,"Unknown\n" ); }/**
@@ -1753,8 +1757,8 @@ lpfc_used_xri_show(struct device *dev, suint32_t cnt, acnt;if (lpfc_get_hba_info (phba, &cnt, &acnt,NULL ,NULL ,NULL ,NULL )) -return snprintf (buf,PAGE_SIZE ,"%d\n" , (cnt - acnt)); -return snprintf (buf,PAGE_SIZE ,"Unknown\n" ); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , (cnt - acnt)); +return scnprintf (buf,PAGE_SIZE ,"Unknown\n" ); }/**
@@ -1781,8 +1785,8 @@ lpfc_max_vpi_show(struct device *dev, stuint32_t cnt;if (lpfc_get_hba_info (phba,NULL ,NULL ,NULL ,NULL , &cnt,NULL )) -return snprintf (buf,PAGE_SIZE ,"%d\n" , cnt); -return snprintf (buf,PAGE_SIZE ,"Unknown\n" ); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , cnt); +return scnprintf (buf,PAGE_SIZE ,"Unknown\n" ); }/**
@@ -1809,8 +1813,8 @@ lpfc_used_vpi_show(struct device *dev, suint32_t cnt, acnt;if (lpfc_get_hba_info (phba,NULL ,NULL ,NULL ,NULL , &cnt, &acnt)) -return snprintf (buf,PAGE_SIZE ,"%d\n" , (cnt - acnt)); -return snprintf (buf,PAGE_SIZE ,"Unknown\n" ); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , (cnt - acnt)); +return scnprintf (buf,PAGE_SIZE ,"Unknown\n" ); }/**
@@ -1835,10 +1839,10 @@ lpfc_npiv_info_show(struct device *dev,struct lpfc_hba *phba = vport->phba;if (!(phba->max_vpi)) -return snprintf (buf,PAGE_SIZE ,"NPIV Not Supported\n" ); +return scnprintf (buf,PAGE_SIZE ,"NPIV Not Supported\n" );if (vport->port_type ==LPFC_PHYSICAL_PORT ) -return snprintf (buf,PAGE_SIZE ,"NPIV Physical\n" ); -return snprintf (buf,PAGE_SIZE ,"NPIV Virtual (VPI %d)\n" , vport->vpi); +return scnprintf (buf,PAGE_SIZE ,"NPIV Physical\n" ); +return scnprintf (buf,PAGE_SIZE ,"NPIV Virtual (VPI %d)\n" , vport->vpi); }/**
@@ -1860,7 +1864,7 @@ lpfc_poll_show(struct device *dev, strucstruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%#x\n" , phba->cfg_poll); +return scnprintf (buf,PAGE_SIZE ,"%#x\n" , phba->cfg_poll); }/**
@@ -1964,7 +1968,7 @@ lpfc_fips_level_show(struct device *dev,struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" , phba->fips_level); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->fips_level); }/**
@@ -1983,7 +1987,7 @@ lpfc_fips_rev_show(struct device *dev,struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" , phba->fips_spec_rev); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->fips_spec_rev); }/**
@@ -2002,7 +2006,7 @@ lpfc_dss_show(struct device *dev, structstruct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"%s - %sOperational\n" , +return scnprintf (buf,PAGE_SIZE ,"%s - %sOperational\n" , (phba->cfg_enable_dss) ?"Enabled" :"Disabled" , (phba->sli3_options &LPFC_SLI3_DSS_ENABLED ) ?"" :"Not " );
@@ -2031,7 +2035,7 @@ lpfc_sriov_hw_max_virtfn_show(struct devuint16_t max_nr_virtfn; max_nr_virtfn =lpfc_sli_sriov_nr_virtfn_get (phba); -return snprintf (buf,PAGE_SIZE ,"%d\n" , max_nr_virtfn); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , max_nr_virtfn); }static inline bool lpfc_rangecheck (uint val,uint min,uint max)
@@ -2091,7 +2095,7 @@ lpfc_##attr##_show(struct device *dev, sstruct Scsi_Host *shost =class_to_shost (dev);\struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;\struct lpfc_hba *phba = vport->phba;\ -return snprintf (buf,PAGE_SIZE ,"%d\n" ,\ +return scnprintf (buf,PAGE_SIZE ,"%d\n" ,\ phba->cfg_##attr);\ }
@@ -2119,7 +2123,7 @@ lpfc_##attr##_show(struct device *dev, sstruct lpfc_hba *phba = vport->phba;\uint val =0 ;\ val = phba->cfg_##attr;\ - return snprintf(buf, PAGE_SIZE, "%#x\n",\ + return scnprintf(buf, PAGE_SIZE, "%#x\n",\ phba->cfg_##attr);\ }
@@ -2255,7 +2259,7 @@ lpfc_##attr##_show(struct device *dev, s { \struct Scsi_Host *shost =class_to_shost (dev);\struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;\ - return snprintf(buf, PAGE_SIZE, "%d\n", vport->cfg_##attr);\ + return scnprintf(buf, PAGE_SIZE, "%d\n", vport->cfg_##attr);\ }/**
@@ -2280,7 +2284,7 @@ lpfc_##attr##_show(struct device *dev, s { \struct Scsi_Host *shost =class_to_shost (dev);\struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;\ - return snprintf(buf, PAGE_SIZE, "%#x\n", vport->cfg_##attr);\ + return scnprintf(buf, PAGE_SIZE, "%#x\n", vport->cfg_##attr);\ }/**
@@ -2551,7 +2555,7 @@ lpfc_soft_wwpn_show(struct device *dev,struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata;struct lpfc_hba *phba = vport->phba; -return snprintf (buf,PAGE_SIZE ,"0x%llx\n" , +return scnprintf (buf,PAGE_SIZE ,"0x%llx\n" , (unsigned long long )phba->cfg_soft_wwpn); }
@@ -2648,7 +2652,7 @@ lpfc_soft_wwnn_show(struct device *dev, {struct Scsi_Host *shost =class_to_shost (dev);struct lpfc_hba *phba = ((struct lpfc_vport *)shost->hostdata)->phba; -return snprintf (buf,PAGE_SIZE ,"0x%llx\n" , +return scnprintf (buf,PAGE_SIZE ,"0x%llx\n" , (unsigned long long )phba->cfg_soft_wwnn); }
@@ -2714,7 +2718,7 @@ lpfc_oas_tgt_show(struct device *dev, ststruct Scsi_Host *shost =class_to_shost (dev);struct lpfc_hba *phba = ((struct lpfc_vport *)shost->hostdata)->phba; -return snprintf (buf,PAGE_SIZE ,"0x%llx\n" , +return scnprintf (buf,PAGE_SIZE ,"0x%llx\n" ,wwn_to_u64 (phba->cfg_oas_tgt_wwpn)); }
@@ -2782,7 +2786,7 @@ lpfc_oas_priority_show(struct device *destruct Scsi_Host *shost =class_to_shost (dev);struct lpfc_hba *phba = ((struct lpfc_vport *)shost->hostdata)->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" , phba->cfg_oas_priority); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->cfg_oas_priority); }/**
@@ -2845,7 +2849,7 @@ lpfc_oas_vpt_show(struct device *dev, ststruct Scsi_Host *shost =class_to_shost (dev);struct lpfc_hba *phba = ((struct lpfc_vport *)shost->hostdata)->phba; -return snprintf (buf,PAGE_SIZE ,"0x%llx\n" , +return scnprintf (buf,PAGE_SIZE ,"0x%llx\n" ,wwn_to_u64 (phba->cfg_oas_vpt_wwpn)); }
@@ -2916,7 +2920,7 @@ lpfc_oas_lun_state_show(struct device *dstruct Scsi_Host *shost =class_to_shost (dev);struct lpfc_hba *phba = ((struct lpfc_vport *)shost->hostdata)->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" , phba->cfg_oas_lun_state); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->cfg_oas_lun_state); }/**
@@ -2980,7 +2984,7 @@ lpfc_oas_lun_status_show(struct device *if (!(phba->cfg_oas_flags &OAS_LUN_VALID ))return -EFAULT ; -return snprintf (buf,PAGE_SIZE ,"%d\n" , phba->cfg_oas_lun_status); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->cfg_oas_lun_status); } static DEVICE_ATTR(lpfc_xlane_lun_status, S_IRUGO, lpfc_oas_lun_status_show, NULL);
@@ -3132,7 +3136,7 @@ lpfc_oas_lun_show(struct device *dev, stif (oas_lun !=NOT_OAS_ENABLED_LUN ) phba->cfg_oas_flags |=OAS_LUN_VALID ; - len +=snprintf (buf + len,PAGE_SIZE -len,"0x%llx" , oas_lun); + len +=scnprintf (buf + len,PAGE_SIZE -len,"0x%llx" , oas_lun);return len; }
@@ -3266,7 +3270,7 @@ lpfc_iocb_hw_show(struct device *dev, ststruct Scsi_Host *shost =class_to_shost (dev);struct lpfc_hba *phba = ((struct lpfc_vport *) shost->hostdata)->phba; -return snprintf (buf,PAGE_SIZE ,"%d\n" , phba->iocb_max); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , phba->iocb_max); } static DEVICE_ATTR(iocb_hw, S_IRUGO,
@@ -3278,7 +3282,7 @@ lpfc_txq_hw_show(struct device *dev, strstruct lpfc_hba *phba = ((struct lpfc_vport *) shost->hostdata)->phba;struct lpfc_sli_ring *pring =lpfc_phba_elsring (phba); -return snprintf (buf,PAGE_SIZE ,"%d\n" , +return scnprintf (buf,PAGE_SIZE ,"%d\n" , pring ? pring->txq_max :0 ); }
@@ -3292,7 +3296,7 @@ lpfc_txcmplq_hw_show(struct device *dev,struct lpfc_hba *phba = ((struct lpfc_vport *) shost->hostdata)->phba;struct lpfc_sli_ring *pring =lpfc_phba_elsring (phba); -return snprintf (buf,PAGE_SIZE ,"%d\n" , +return scnprintf (buf,PAGE_SIZE ,"%d\n" , pring ? pring->txcmplq_max :0 ); }
@@ -3328,7 +3332,7 @@ lpfc_nodev_tmo_show(struct device *dev,struct Scsi_Host *shost =class_to_shost (dev);struct lpfc_vport *vport = (struct lpfc_vport *) shost->hostdata; -return snprintf (buf,PAGE_SIZE ,"%d\n" , vport->cfg_devloss_tmo); +return scnprintf (buf,PAGE_SIZE ,"%d\n" , vport->cfg_devloss_tmo); }/**
@@ -4830,19 +4834,19 @@ lpfc_fcp_cpu_map_show(struct device *devswitch (phba->cfg_fcp_cpu_map) {case 0 : - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len,"fcp_cpu_map: No mapping (%d)\n" , phba->cfg_fcp_cpu_map);return len;case 1 : - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len,"fcp_cpu_map: HBA centric mapping (%d): " "%d online CPUs\n" , phba->cfg_fcp_cpu_map, phba->sli4_hba.num_online_cpu);break ;case 2 : - len += snprintf(buf + len, PAGE_SIZE-len, + len += scnprintf(buf + len, PAGE_SIZE-len, "fcp_cpu_map: Driver centric mapping (%d): " "%d online CPUs\n", phba->cfg_fcp_cpu_map,
@@ -4855,14 +4859,14 @@ lpfc_fcp_cpu_map_show(struct device *dev/* margin should fit in this and the truncated message */ if (cpup->irq ==LPFC_VECTOR_MAP_EMPTY ) - len +=snprintf (buf + len,PAGE_SIZE -len, + len +=scnprintf (buf + len,PAGE_SIZE -len,"CPU %02d io_chan %02d " "physid %d coreid %d\n" , phba->sli4_hba.curr_disp_cpu, cpup->channel_id, cpup->phys_id, cpup->core_id);else - len += snprintf(buf + len, PAGE_SIZE-len, + len += scnprintf(buf + len, PAGE_SIZE-len, "CPU %02d io_chan %02d " "physid %d coreid %d IRQ %d\n", phba->sli4_hba.curr_disp_cpu,
@@ -4875,7 +4879,7 @@ lpfc_fcp_cpu_map_show(struct device *devif (phba->sli4_hba.curr_disp_cpu < phba->sli4_hba.num_present_cpu && (len >= (PAGE_SIZE -64 ))) { - len +=snprintf (buf + len,PAGE_SIZE -len,"more...\n" ); + len +=scnprintf (buf + len,PAGE_SIZE -len,"more...\n" );break ; } }
@@ -6296,7 +6300,7 @@ lpfc_show_rport_##field (struct device * { \struct fc_rport *rport =transport_class_to_rport (dev); \struct lpfc_rport_data *rdata = rport->hostdata; \ -return snprintf (buf, sz, format_string, \ +return scnprintf (buf, sz, format_string, \ (rdata->target) ? cast rdata->target->field : 0); \ }
drivers/scsi/lpfc/lpfc_ct.c +6 -6
@@ -1220,7 +1220,7 @@ lpfc_vport_symbolic_port_name(struct lpf* Name object. NPIV is not in play so this integer * value is sufficient and unique per FC-ID. */ - n =snprintf (symbol, size,"%d" , vport->phba->brd_no); + n =scnprintf (symbol, size,"%d" , vport->phba->brd_no);return n; }
@@ -1234,26 +1234,26 @@ lpfc_vport_symbolic_node_name(struct lpflpfc_decode_firmware_rev (vport->phba, fwrev,0 ); - n =snprintf (symbol, size,"Emulex %s" , vport->phba->ModelName); + n =scnprintf (symbol, size,"Emulex %s" , vport->phba->ModelName);if (size < n)return n; - n +=snprintf (symbol + n, size - n," FV%s" , fwrev); + n +=scnprintf (symbol + n, size - n," FV%s" , fwrev);if (size < n)return n; - n +=snprintf (symbol + n, size - n," DV%s." , + n +=scnprintf (symbol + n, size - n," DV%s." , lpfc_release_version);if (size < n)return n; - n +=snprintf (symbol + n, size - n," HN:%s." , + n +=scnprintf (symbol + n, size - n," HN:%s." ,init_utsname ()->nodename);if (size < n)return n;/* Note :- OS name is "Linux" */ - n +=snprintf (symbol + n, size - n," OS:%s\n" , + n +=scnprintf (symbol + n, size - n," OS:%s\n" ,init_utsname ()->sysname);return n; }
drivers/scsi/lpfc/lpfc_debugfs.c +228 -225
1,384 lines not on this page · raw message
drivers/scsi/lpfc/lpfc_debugfs.h +3 -3
@@ -342,7 +342,7 @@ lpfc_debug_dump_qe(struct lpfc_queue *q, pword = q->qe[idx].address; len =0 ; - len +=snprintf (line_buf+len,LPFC_LBUF_SZ -len,"QE[%04d]: " , idx); + len +=scnprintf (line_buf+len,LPFC_LBUF_SZ -len,"QE[%04d]: " , idx);if (qe_word_cnt >8 )printk (KERN_ERR "%s\n" , line_buf);
@@ -353,11 +353,11 @@ lpfc_debug_dump_qe(struct lpfc_queue *q,if (qe_word_cnt >8 ) { len =0 ;memset (line_buf,0 ,LPFC_LBUF_SZ ); - len +=snprintf (line_buf+len,LPFC_LBUF_SZ -len, + len +=scnprintf (line_buf+len,LPFC_LBUF_SZ -len,"%03d: " , i); } } - len +=snprintf (line_buf+len,LPFC_LBUF_SZ -len,"%08x " , + len +=scnprintf (line_buf+len,LPFC_LBUF_SZ -len,"%08x " , ((uint32_t )*pword) &0xffffffff ); pword++; }
Greg Kroah-Hartman
maintainerPATCH 60/66 scsi: qla2xxx: Fix device staying in blocked state
In reply to Greg Kroah-HartmanFrom: Quinn Tran <[email protected]>
commit 2137490f2147a8d0799b72b9a1023efb012d40c7 upstream.
This patch fixes issue reported by some of the customers, who discovered that after cable pull scenario the devices disappear and path seems to remain in blocked state. Once the device reappears, driver does not seem to update path to online. This issue appears because of the defer flag creating race condition where the same session reappears. This patch fixes this issue by indicating SCSI-ML of device lost when qlt_free_session_done() is called from qlt_unreg_sess().
--- drivers/scsi/qla2xxx/qla_target.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/scsi/qla2xxx/qla_target.c +2 -2
@@ -981,6 +981,8 @@ void qlt_free_session_done(struct work_s sess->send_els_logo);if (!IS_SW_RESV_ADDR (sess->d_id)) { +qla2x00_mark_device_lost (vha, sess,0 ,0 ); +if (sess->send_els_logo) {qlt_port_logo_t logo;
@@ -1161,8 +1163,6 @@ void qlt_unreg_sess(struct fc_port *sessif (sess->se_sess) vha->hw->tgt.tgt_ops->clear_nacl_from_fcport_map (sess); -qla2x00_mark_device_lost (vha, sess,0 ,0 ); - sess->deleted =QLA_SESS_DELETION_IN_PROGRESS ; sess->disc_state =DSC_DELETE_PEND ; sess->last_rscn_gen = sess->rscn_gen;
Greg Kroah-Hartman
maintainerPATCH 62/66 Bluetooth: Align minimum encryption key size for LE and BR/EDR connections
In reply to Greg Kroah-HartmanFrom: Marcel Holtmann <[email protected]>
commit d5bb334a8e171b262e48f378bd2096c0ea458265 upstream.
The minimum encryption key size for LE connections is 56 bits and to align LE with BR/EDR, enforce 56 bits of minimum encryption key size for BR/EDR connections as well.
--- include/net/bluetooth/hci_core.h | 3 +++ net/bluetooth/hci_conn.c | 8 ++++++++ 2 files changed, 11 insertions(+)
include/net/bluetooth/hci_core.h +3 -0
@@ -182,6 +182,9 @@ struct adv_info {#define HCI_MAX_SHORT_NAME_LENGTH 10 +/* Min encryption key size to match with SMP */ +#define HCI_MIN_ENC_KEY_SIZE 7 +/* Default LE RPA expiry time, 15 minutes */ #define HCI_DEFAULT_RPA_TIMEOUT (15 * 60)
net/bluetooth/hci_conn.c +8 -0
@@ -1276,6 +1276,14 @@ int hci_conn_check_link_mode(struct hci_ !test_bit(HCI_CONN_ENCRYPT, &conn->flags))return 0 ; +/* The minimum encryption key size needs to be enforced by the +* host stack before establishing any L2CAP connections. The +* specification in theory allows a minimum of 1, but to align +* BR/EDR and LE transports, a minimum of 7 is chosen. +*/ +if (conn->enc_key_size <HCI_MIN_ENC_KEY_SIZE ) +return 0 ; +return 1 ; }
Greg Kroah-Hartman
maintainerPATCH 63/66 UAS: fix alignment of scatter/gather segments
In reply to Greg Kroah-HartmanFrom: Oliver Neukum <[email protected]>
commit 3ae62a42090f1ed48e2313ed256a1182a85fb575 upstream.
This is the UAS version of
747668dbc061b3e62bc1982767a3a1f9815fcf0e
usb-storage: Set virt_boundary_mask to avoid SG overflows
We are not as likely to be vulnerable as storage, as it is unlikelier that UAS is run over a controller without native support for SG, but the issue exists.
The issue has been existing since the inception of the driver.
--- drivers/usb/storage/uas.c | 35 ++++++++++++++++++++++------------- 1 file changed, 22 insertions(+), 13 deletions(-)
drivers/usb/storage/uas.c +22 -13
@@ -796,24 +796,33 @@ static int uas_slave_alloc(struct scsi_d {struct uas_dev_info *devinfo = (struct uas_dev_info *)sdev->host->hostdata; +int maxp; sdev->hostdata = devinfo;/* -* USB has unusual DMA-alignment requirements: Although the -* starting address of each scatter-gather element doesn't matter, -* the length of each element except the last must be divisible -* by the Bulk maxpacket value. There's currently no way to -* express this by block-layer constraints, so we'll cop out -* and simply require addresses to be aligned at 512-byte -* boundaries. This is okay since most block I/O involves -* hardware sectors that are multiples of 512 bytes in length, -* and since host controllers up through USB 2.0 have maxpacket -* values no larger than 512. +* We have two requirements here. We must satisfy the requirements +* of the physical HC and the demands of the protocol, as we +* definitely want no additional memory allocation in this path +* ruling out using bounce buffers. * -* But it doesn't suffice for Wireless USB, where Bulk maxpacket -* values can be as large as 2048. To make that work properly -* will require changes to the block layer. +* For a transmission on USB to continue we must never send +* a package that is smaller than maxpacket. Hence the length of each +* scatterlist element except the last must be divisible by the +* Bulk maxpacket value. +* If the HC does not ensure that through SG, +* the upper layer must do that. We must assume nothing +* about the capabilities off the HC, so we use the most +* pessimistic requirement. +*/ + + maxp =usb_maxpacket (devinfo->udev, devinfo->data_in_pipe,0 ); +blk_queue_virt_boundary (sdev->request_queue, maxp -1 ); + +/* +* The protocol has no requirements on alignment in the strict sense. +* Controllers may or may not have alignment restrictions. +* As this is not exported, we use an extremely conservative guess. */ blk_queue_update_dma_alignment (sdev->request_queue, (512 -1 ));
Greg Kroah-Hartman
maintainerPATCH 46/66 nvme-fc: correct csn initialization and increments on error
In reply to Greg Kroah-Hartman[ Upstream commit 67f471b6ed3b09033c4ac77ea03f92afdb1989fe ]
This patch fixes a long-standing bug that initialized the FC-NVME cmnd iu CSN value to 1. Early FC-NVME specs had the connection starting with CSN=1. By the time the spec reached approval, the language had changed to state a connection should start with CSN=0. This patch corrects the initialization value for FC-NVME connections.
Additionally, in reviewing the transport, the CSN value is assigned to the new IU early in the start routine. It's possible that a later dma map request may fail, causing the command to never be sent to the controller. Change the location of the assignment so that it is immediately prior to calling the lldd. Add a comment block to explain the impacts if the lldd were to additionally fail sending the command.
--- drivers/nvme/host/fc.c | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-)
drivers/nvme/host/fc.c +15 -5
@@ -1844,7 +1844,7 @@ nvme_fc_init_queue(struct nvme_fc_ctrl *ctrl, int idx)memset (queue,0 ,sizeof (*queue)); queue->ctrl = ctrl; queue->qnum = idx; -atomic_set (&queue->csn,1 ); +atomic_set (&queue->csn,0 ); queue->dev = ctrl->dev;if (idx >0 )
@@ -1886,7 +1886,7 @@ nvme_fc_free_queue(struct nvme_fc_queue *queue)*/ queue->connection_id =0 ; -atomic_set (&queue->csn,1 ); +atomic_set (&queue->csn,0 ); } static void
@@ -2182,7 +2182,6 @@ nvme_fc_start_fcp_op(struct nvme_fc_ctrl *ctrl, struct nvme_fc_queue *queue, {struct nvme_fc_cmd_iu *cmdiu = &op->cmd_iu;struct nvme_command *sqe = &cmdiu->sqe; -u32 csn;int ret, opstate;/*
@@ -2197,8 +2196,6 @@ nvme_fc_start_fcp_op(struct nvme_fc_ctrl *ctrl, struct nvme_fc_queue *queue,/* format the FC-NVME CMD IU and fcp_req */ cmdiu->connection_id =cpu_to_be64 (queue->connection_id); - csn =atomic_inc_return (&queue->csn); - cmdiu->csn =cpu_to_be32 (csn); cmdiu->data_len =cpu_to_be32 (data_len);switch (io_dir) {case NVMEFC_FCP_WRITE :
@@ -2256,11 +2253,24 @@ nvme_fc_start_fcp_op(struct nvme_fc_ctrl *ctrl, struct nvme_fc_queue *queue,if (!(op->flags &FCOP_FLAGS_AEN ))blk_mq_start_request (op->rq); + cmdiu->csn =cpu_to_be32 (atomic_inc_return (&queue->csn)); ret = ctrl->lport->ops->fcp_io (&ctrl->lport->localport, &ctrl->rport->remoteport, queue->lldd_handle, &op->fcp_req);if (ret) { +/* +* If the lld fails to send the command is there an issue with +* the csn value? If the command that fails is the Connect, +* no - as the connection won't be live. If it is a command +* post-connect, it's possible a gap in csn may be created. +* Does this matter? As Linux initiators don't send fused +* commands, no. The gap would exist, but as there's nothing +* that depends on csn order to be delivered on the target +* side, it shouldn't hurt. It would be difficult for a +* target to even detect the csn gap as it has no idea when the +* cmd with the csn was supposed to arrive. +*/ opstate =atomic_xchg (&op->state,FCPOP_STATE_COMPLETE );__nvme_fc_fcpop_chk_teardowns (ctrl, op, opstate);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 64/66 ASoC: Intel: avoid Oops if DMA setup fails
In reply to Greg Kroah-HartmanFrom: Ross Zwisler <[email protected]>
commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream.
Currently in sst_dsp_new() if we get an error return from sst_dma_new() we just print an error message and then still complete the function successfully. This means that we are trying to run without sst->dma properly set up, which will result in NULL pointer dereference when sst->dma is later used. This was happening for me in sst_dsp_dma_get_channel():
struct sst_dma *dma = dsp->dma;
...
dma->ch = dma_request_channel(mask, dma_chan_filter, dsp);This resulted in:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 IP: sst_dsp_dma_get_channel+0x4f/0x125 [snd_soc_sst_firmware]
Fix this by adding proper error handling for the case where we fail to set up DMA.
This change only affects Haswell and Broadwell systems. Baytrail systems explicilty opt-out of DMA via sst->pdata->resindex_dma_base being set to -1.
--- sound/soc/intel/common/sst-firmware.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
sound/soc/intel/common/sst-firmware.c +6 -2
@@ -1251,11 +1251,15 @@ struct sst_dsp *sst_dsp_new(struct devic goto irq_err; err =sst_dma_new (sst); -if (err) -dev_warn (dev,"sst_dma_new failed %d\n" , err); +if (err) { +dev_err (dev,"sst_dma_new failed %d\n" , err); + goto dma_err; + }return sst; +dma_err: +free_irq (sst->irq, sst); irq_err:if (sst->ops->free) sst->ops->free (sst);
Greg Kroah-Hartman
maintainerPATCH 65/66 locking/futex: Allow low-level atomic operations to return -EAGAIN
In reply to Greg Kroah-HartmanFrom: Will Deacon <[email protected]>
commit 6b4f4bc9cb22875f97023984a625386f0c7cc1c0 upstream.
Some futex() operations, including FUTEX_WAKE_OP, require the kernel to perform an atomic read-modify-write of the futex word via the userspace mapping. These operations are implemented by each architecture in arch_futex_atomic_op_inuser() and futex_atomic_cmpxchg_inatomic(), which are called in atomic context with the relevant hash bucket locks held.
Although these routines may return -EFAULT in response to a page fault generated when accessing userspace, they are expected to succeed (i.e. return 0) in all other cases. This poses a problem for architectures that do not provide bounded forward progress guarantees or fairness of contended atomic operations and can lead to starvation in some cases.
In these problematic scenarios, we must return back to the core futex code so that we can drop the hash bucket locks and reschedule if necessary, much like we do in the case of a page fault.
Allow architectures to return -EAGAIN from their implementations of arch_futex_atomic_op_inuser() and futex_atomic_cmpxchg_inatomic(), which will cause the core futex code to reschedule if necessary and return back to the architecture code later on.
--- kernel/futex.c | 188 +++++++++++++++++++++++++++++++++++---------------------- 1 file changed, 117 insertions(+), 71 deletions(-)
kernel/futex.c +117 -71
@@ -1306,13 +1306,15 @@ static int lookup_pi_state(u32 __user *ustatic int lock_pi_update_atomic (u32 __user *uaddr,u32 uval,u32 newval) { +int err;u32 uninitialized_var (curval );if (unlikely (should_fail_futex (true)))return -EFAULT ; -if (unlikely (cmpxchg_futex_value_locked (&curval, uaddr, uval, newval))) -return -EFAULT ; + err =cmpxchg_futex_value_locked (&curval, uaddr, uval, newval); +if (unlikely (err)) +return err;/* If user space value changed, let the caller retry */ return curval != uval ? -EAGAIN :0 ;
@@ -1498,10 +1500,8 @@ static int wake_futex_pi(u32 __user *uadif (unlikely (should_fail_futex (true))) ret = -EFAULT ; -if (cmpxchg_futex_value_locked (&curval, uaddr, uval, newval)) { - ret = -EFAULT ; - - }else if (curval != uval) { + ret =cmpxchg_futex_value_locked (&curval, uaddr, uval, newval); +if (!ret && (curval != uval)) {/* * If a unconditional UNLOCK_PI operation (user space did not * try the TID->0 transition) raced with a waiter setting the
@@ -1696,32 +1696,32 @@ retry_private:double_lock_hb (hb1, hb2); op_ret =futex_atomic_op_inuser (op, uaddr2);if (unlikely (op_ret <0 )) { -double_unlock_hb (hb1, hb2); -#ifndef CONFIG_MMU -/* -* we don't get EFAULT from MMU faults if we don't have an MMU, -* but we might get them from range checking -*/ - ret = op_ret; - goto out_put_keys; -#endif - -if (unlikely (op_ret != -EFAULT )) { +if (!IS_ENABLED (CONFIG_MMU ) || +unlikely (op_ret != -EFAULT && op_ret != -EAGAIN )) { +/* +* we don't get EFAULT from MMU faults if we don't have +* an MMU, but we might get them from range checking +*/ ret = op_ret; goto out_put_keys; } - ret =fault_in_user_writeable (uaddr2); -if (ret) - goto out_put_keys; +if (op_ret == -EFAULT ) { + ret =fault_in_user_writeable (uaddr2); +if (ret) + goto out_put_keys; + } -if (!(flags &FLAGS_SHARED )) +if (!(flags &FLAGS_SHARED )) { +cond_resched (); goto retry_private; + }put_futex_key (&key2);put_futex_key (&key1); +cond_resched (); goto retry; }
@@ -2346,7 +2346,7 @@ static int fixup_pi_state_owner(u32 __usu32 uval,uninitialized_var (curval ), newval;struct task_struct *oldowner, *newowner;u32 newtid; -int ret; +int ret, err =0 ;lockdep_assert_held (q->lock_ptr);
@@ -2417,14 +2417,17 @@ retry:if (!pi_state->owner) newtid |=FUTEX_OWNER_DIED ; -if (get_futex_value_locked (&uval, uaddr)) - goto handle_fault; + err =get_futex_value_locked (&uval, uaddr); +if (err) + goto handle_err;for (;;) { newval = (uval &FUTEX_OWNER_DIED ) | newtid; -if (cmpxchg_futex_value_locked (&curval, uaddr, uval, newval)) - goto handle_fault; + err =cmpxchg_futex_value_locked (&curval, uaddr, uval, newval); +if (err) + goto handle_err; +if (curval == uval)break ; uval = curval;
@@ -2452,23 +2455,37 @@ retry:return 0 ;/* -* To handle the page fault we need to drop the locks here. That gives -* the other task (either the highest priority waiter itself or the -* task which stole the rtmutex) the chance to try the fixup of the -* pi_state. So once we are back from handling the fault we need to -* check the pi_state after reacquiring the locks and before trying to -* do another fixup. When the fixup has been done already we simply -* return. +* In order to reschedule or handle a page fault, we need to drop the +* locks here. In the case of a fault, this gives the other task +* (either the highest priority waiter itself or the task which stole +* the rtmutex) the chance to try the fixup of the pi_state. So once we +* are back from handling the fault we need to check the pi_state after +* reacquiring the locks and before trying to do another fixup. When +* the fixup has been done already we simply return. * * Note: we hold both hb->lock and pi_mutex->wait_lock. We can safely * drop hb->lock since the caller owns the hb -> futex_q relation. * Dropping the pi_mutex->wait_lock requires the state revalidate. */ -handle_fault: +handle_err:raw_spin_unlock_irq (&pi_state->pi_mutex.wait_lock);spin_unlock (q->lock_ptr); - ret =fault_in_user_writeable (uaddr); +switch (err) { +case -EFAULT : + ret =fault_in_user_writeable (uaddr); +break ; + +case -EAGAIN : +cond_resched (); + ret =0 ; +break ; + +default : +WARN_ON_ONCE (1 ); + ret = err; +break ; + }spin_lock (q->lock_ptr);raw_spin_lock_irq (&pi_state->pi_mutex.wait_lock);
@@ -3037,10 +3054,8 @@ retry:* A unconditional UNLOCK_PI op raced against a waiter * setting the FUTEX_WAITERS bit. Try again. */ -if (ret == -EAGAIN ) { -put_futex_key (&key); - goto retry; - } +if (ret == -EAGAIN ) + goto pi_retry;/* * wake_futex_pi has detected invalid state. Tell user * space.
@@ -3055,9 +3070,19 @@ retry:* preserve the WAITERS bit not the OWNER_DIED one. We are the * owner. */ -if (cmpxchg_futex_value_locked (&curval, uaddr, uval,0 )) { +if ((ret =cmpxchg_futex_value_locked (&curval, uaddr, uval,0 ))) {spin_unlock (&hb->lock); - goto pi_faulted; +switch (ret) { +case -EFAULT : + goto pi_faulted; + +case -EAGAIN : + goto pi_retry; + +default : +WARN_ON_ONCE (1 ); + goto out_putkey; + } }/*
@@ -3071,6 +3096,11 @@ out_putkey:put_futex_key (&key);return ret; +pi_retry: +put_futex_key (&key); +cond_resched (); + goto retry; + pi_faulted:put_futex_key (&key);
@@ -3431,6 +3461,7 @@ err_unlock:int handle_futex_death (u32 __user *uaddr,struct task_struct *curr,int pi) {u32 uval,uninitialized_var (nval ), mval; +int err;/* Futex address must be 32bit aligned */ if ((((unsigned long )uaddr) %sizeof (*uaddr)) !=0 )
@@ -3440,42 +3471,57 @@ retry:if (get_user (uval, uaddr))return -1 ; -if ((uval &FUTEX_TID_MASK ) ==task_pid_vnr (curr)) { -/* -* Ok, this dying thread is truly holding a futex -* of interest. Set the OWNER_DIED bit atomically -* via cmpxchg, and if the value had FUTEX_WAITERS -* set, wake up a waiter (if any). (We have to do a -* futex_wake() even if OWNER_DIED is already set - -* to handle the rare but possible case of recursive -* thread-death.) The rest of the cleanup is done in -* userspace. -*/ - mval = (uval &FUTEX_WAITERS ) |FUTEX_OWNER_DIED ; -/* -* We are not holding a lock here, but we want to have -* the pagefault_disable/enable() protection because -* we want to handle the fault gracefully. If the -* access fails we try to fault in the futex with R/W -* verification via get_user_pages. get_user() above -* does not guarantee R/W access. If that fails we -* give up and leave the futex locked. -*/ -if (cmpxchg_futex_value_locked (&nval, uaddr, uval, mval)) { +if ((uval &FUTEX_TID_MASK ) !=task_pid_vnr (curr)) +return 0 ; + +/* +* Ok, this dying thread is truly holding a futex +* of interest. Set the OWNER_DIED bit atomically +* via cmpxchg, and if the value had FUTEX_WAITERS +* set, wake up a waiter (if any). (We have to do a +* futex_wake() even if OWNER_DIED is already set - +* to handle the rare but possible case of recursive +* thread-death.) The rest of the cleanup is done in +* userspace. +*/ + mval = (uval &FUTEX_WAITERS ) |FUTEX_OWNER_DIED ; + +/* +* We are not holding a lock here, but we want to have +* the pagefault_disable/enable() protection because +* we want to handle the fault gracefully. If the +* access fails we try to fault in the futex with R/W +* verification via get_user_pages. get_user() above +* does not guarantee R/W access. If that fails we +* give up and leave the futex locked. +*/ +if ((err =cmpxchg_futex_value_locked (&nval, uaddr, uval, mval))) { +switch (err) { +case -EFAULT :if (fault_in_user_writeable (uaddr))return -1 ; goto retry; - } -if (nval != uval) + +case -EAGAIN : +cond_resched (); goto retry; -/* -* Wake robust non-PI futexes here. The wakeup of -* PI futexes happens in exit_pi_state(): -*/ -if (!pi && (uval &FUTEX_WAITERS )) -futex_wake (uaddr,1 ,1 ,FUTEX_BITSET_MATCH_ANY ); +default : +WARN_ON_ONCE (1 ); +return err; + } } + +if (nval != uval) + goto retry; + +/* +* Wake robust non-PI futexes here. The wakeup of +* PI futexes happens in exit_pi_state(): +*/ +if (!pi && (uval &FUTEX_WAITERS )) +futex_wake (uaddr,1 ,1 ,FUTEX_BITSET_MATCH_ANY ); +return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 66/66 arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP
In reply to Greg Kroah-HartmanFrom: Will Deacon <[email protected]>
commit 03110a5cb2161690ae5ac04994d47ed0cd6cef75 upstream.
Our futex implementation makes use of LDXR/STXR loops to perform atomic updates to user memory from atomic context. This can lead to latency problems if we end up spinning around the LL/SC sequence at the expense of doing something useful.
Rework our futex atomic operations so that we return -EAGAIN if we fail to update the futex word after 128 attempts. The core futex code will reschedule if necessary and we'll try again later.
--- arch/arm64/include/asm/futex.h | 55 +++++++++++++++++++++++++---------------- 1 file changed, 34 insertions(+), 21 deletions(-)
arch/arm64/include/asm/futex.h +34 -21
@@ -23,26 +23,34 @@#include <asm/errno.h> +#define FUTEX_MAX_LOOPS 128/* What's the largest number you can think of? */ +#define __futex_atomic_op (insn, ret, oldval, uaddr, tmp, oparg) \ do { \ + unsigned int loops = FUTEX_MAX_LOOPS; \ + \ uaccess_enable(); \ asm volatile( \ " prfm pstl1strm, %2\n" \ "1: ldxr %w1, %2\n" \ insn "\n" \ "2: stlxr %w0, %w3, %2\n" \ -" cbnz %w0, 1b\n" \ -" dmb ish\n" \ +" cbz %w0, 3f\n" \ +" sub %w4, %w4, %w0\n" \ +" cbnz %w4, 1b\n" \ +" mov %w0, %w7\n" \ "3:\n" \ +" dmb ish\n" \ " .pushsection .fixup,\"ax\"\n" \ " .align 2\n" \ -"4: mov %w0, %w5\n" \ +"4: mov %w0, %w6\n" \ " b 3b\n" \ " .popsection\n" \ _ASM_EXTABLE(1b, 4b) \ _ASM_EXTABLE(2b, 4b) \ - : "=&r" (ret), "=&r" (oldval), "+Q" (*uaddr), "=&r" (tmp) \ - : "r" (oparg), "Ir" (-EFAULT) \ + : "=&r" (ret), "=&r" (oldval), "+Q" (*uaddr), "=&r" (tmp), \ + "+r" (loops) \ + : "r" (oparg), "Ir" (-EFAULT), "Ir" (-EAGAIN) \ : "memory"); \ uaccess_disable(); \ } while (0)
@@ -57,23 +65,23 @@ arch_futex_atomic_op_inuser(int op, intswitch (op) {case FUTEX_OP_SET : -__futex_atomic_op ("mov %w3, %w4" , +__futex_atomic_op ("mov %w3, %w5" , ret, oldval, uaddr, tmp, oparg);break ;case FUTEX_OP_ADD : -__futex_atomic_op ("add %w3, %w1, %w4" , +__futex_atomic_op ("add %w3, %w1, %w5" , ret, oldval, uaddr, tmp, oparg);break ;case FUTEX_OP_OR : -__futex_atomic_op ("orr %w3, %w1, %w4" , +__futex_atomic_op ("orr %w3, %w1, %w5" , ret, oldval, uaddr, tmp, oparg);break ;case FUTEX_OP_ANDN : -__futex_atomic_op ("and %w3, %w1, %w4" , +__futex_atomic_op ("and %w3, %w1, %w5" , ret, oldval, uaddr, tmp, ~oparg);break ;case FUTEX_OP_XOR : -__futex_atomic_op ("eor %w3, %w1, %w4" , +__futex_atomic_op ("eor %w3, %w1, %w5" , ret, oldval, uaddr, tmp, oparg);break ;default :
@@ -93,6 +101,7 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, u32 oldval, u32 newval) {int ret =0 ; +unsigned int loops =FUTEX_MAX_LOOPS ;u32 val, tmp;u32 __user *uaddr;
@@ -104,20 +113,24 @@ futex_atomic_cmpxchg_inatomic(u32 *uval, asmvolatile ("// futex_atomic_cmpxchg_inatomic\n" " prfm pstl1strm, %2\n" "1: ldxr %w1, %2\n" -" sub %w3, %w1, %w4\n" -" cbnz %w3, 3f\n" -"2: stlxr %w3, %w5, %2\n" -" cbnz %w3, 1b\n" -" dmb ish\n" +" sub %w3, %w1, %w5\n" +" cbnz %w3, 4f\n" +"2: stlxr %w3, %w6, %2\n" +" cbz %w3, 3f\n" +" sub %w4, %w4, %w3\n" +" cbnz %w4, 1b\n" +" mov %w0, %w8\n" "3:\n" +" dmb ish\n" +"4:\n" " .pushsection .fixup,\"ax\"\n" -"4: mov %w0, %w6\n" -" b 3b\n" +"5: mov %w0, %w7\n" +" b 4b\n" " .popsection\n" - _ASM_EXTABLE(1b, 4b) - _ASM_EXTABLE(2b, 4b) - : "+r" (ret), "=&r" (val), "+Q" (*uaddr), "=&r" (tmp) - : "r" (oldval), "r" (newval), "Ir" (-EFAULT) + _ASM_EXTABLE(1b, 5b) + _ASM_EXTABLE(2b, 5b) + : "+r" (ret), "=&r" (val), "+Q" (*uaddr), "=&r" (tmp), "+r" (loops) + : "r" (oldval), "r" (newval), "Ir" (-EFAULT), "Ir" (-EAGAIN) : "memory");uaccess_disable ();
Greg Kroah-Hartman
maintainerPATCH 47/66 platform/x86: pmc_atom: Drop __initconst on dmi table
In reply to Greg Kroah-Hartman[ Upstream commit b995dcca7cf12f208cfd95fd9d5768dca7cccec7 ]
It's used by probe and that isn't an init function. Drop this so that we don't get a section mismatch.
--- drivers/platform/x86/pmc_atom.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/platform/x86/pmc_atom.c +1 -1
@@ -396,7 +396,7 @@ static int pmc_dbgfs_register(struct pmc_dev *pmc)* Some systems need one or more of their pmc_plt_clks to be * marked as critical. */ -static const struct dmi_system_id critclk_systems[]__initconst = { +static const struct dmi_system_id critclk_systems[] = { { .ident ="MPL CEC1x" , .matches = {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 50/66 genirq: Prevent use-after-free and work list corruption
In reply to Greg Kroah-Hartman[ Upstream commit 59c39840f5abf4a71e1810a8da71aaccd6c17d26 ]
When irq_set_affinity_notifier() replaces the notifier, then the reference count on the old notifier is dropped which causes it to be freed. But nothing ensures that the old notifier is not longer queued in the work list. If it is queued this results in a use after free and possibly in work list corruption.
Ensure that the work is canceled before the reference is dropped.
--- kernel/irq/manage.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
kernel/irq/manage.c +3 -1
@@ -356,8 +356,10 @@ irq_set_affinity_notifier(unsigned int irq, struct irq_affinity_notify *notify) desc->affinity_notify = notify;raw_spin_unlock_irqrestore (&desc->lock, flags); -if (old_notify) +if (old_notify) { +cancel_work_sync (&old_notify->work);kref_put (&old_notify->kref, old_notify->release); + }return 0 ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 51/66 usb: dwc3: Fix default lpm_nyet_threshold value
In reply to Greg Kroah-HartmanFrom: Thinh Nguyen <[email protected]>
commit 8d791929b2fbdf7734c1596d808e55cb457f4562 upstream.
The max possible value for DCTL.LPM_NYET_THRES is 15 and not 255. Change the default value to 15.
--- drivers/usb/dwc3/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/dwc3/core.c +1 -1
@@ -1214,7 +1214,7 @@ static void dwc3_get_properties(struct du8 tx_max_burst_prd;/* default to highest possible threshold */ - lpm_nyet_threshold =0xff ; + lpm_nyet_threshold =0xf ;/* default to -3.5dB de-emphasis */ tx_de_emphasis =1 ;
Greg Kroah-Hartman
maintainerPATCH 52/66 USB: serial: f81232: fix interrupt worker not stop
In reply to Greg Kroah-HartmanFrom: Ji-Ze Hong (Peter Hong) <[email protected]>
commit 804dbee1e49774918339c1e5a87400988c0819e8 upstream.
The F81232 will use interrupt worker to handle MSR change. This patch will fix the issue that interrupt work should stop in close() and suspend().
This also fixes line-status events being disabled after a suspend cycle until the port is re-opened.
--- drivers/usb/serial/f81232.c | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+)
drivers/usb/serial/f81232.c +39 -0
@@ -556,9 +556,12 @@ static int f81232_open(struct tty_structstatic void f81232_close (struct usb_serial_port *port) { +struct f81232_private *port_priv =usb_get_serial_port_data (port); +f81232_port_disable (port);usb_serial_generic_close (port);usb_kill_urb (port->interrupt_in_urb); +flush_work (&port_priv->interrupt_work); }static void f81232_dtr_rts (struct usb_serial_port *port,int on)
@@ -652,6 +655,40 @@ static int f81232_port_remove(struct usbreturn 0 ; } +static int f81232_suspend (struct usb_serial *serial,pm_message_t message) +{ +struct usb_serial_port *port = serial->port[0 ]; +struct f81232_private *port_priv =usb_get_serial_port_data (port); +int i; + +for (i =0 ; i <ARRAY_SIZE (port->read_urbs); ++i) +usb_kill_urb (port->read_urbs[i]); + +usb_kill_urb (port->interrupt_in_urb); + +if (port_priv) +flush_work (&port_priv->interrupt_work); + +return 0 ; +} + +static int f81232_resume (struct usb_serial *serial) +{ +struct usb_serial_port *port = serial->port[0 ]; +int result; + +if (tty_port_initialized (&port->port)) { + result =usb_submit_urb (port->interrupt_in_urb,GFP_NOIO ); +if (result) { +dev_err (&port->dev,"submit interrupt urb failed: %d\n" , + result); +return result; + } + } + +return usb_serial_generic_resume (serial); +} +static struct usb_serial_driver f81232_device = { .driver = { .owner =THIS_MODULE ,
@@ -675,6 +712,8 @@ static struct usb_serial_driver f81232_d .read_int_callback = f81232_read_int_callback, .port_probe = f81232_port_probe, .port_remove = f81232_port_remove, + .suspend = f81232_suspend, + .resume = f81232_resume, };static struct usb_serial_driver *const serial_drivers[] = {
Greg Kroah-Hartman
maintainerPATCH 44/66 ASoC: Intel: kbl: fix wrong number of channels
In reply to Greg Kroah-Hartman[ Upstream commit d6ba3f815bc5f3c4249d15c8bc5fbb012651b4a4 ]
Fix wrong setting on number of channels. The context wants to set constraint to 2 channels instead of 4.
--- sound/soc/intel/boards/kbl_rt5663_rt5514_max98927.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/intel/boards/kbl_rt5663_rt5514_max98927.c +1 -1
@@ -406,7 +406,7 @@ static const struct snd_pcm_hw_constraint_list constraints_dmic_channels = { };static const unsigned int dmic_2ch[] = { -4 , +2 , };static const struct snd_pcm_hw_constraint_list constraints_dmic_2ch = {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 53/66 USB: cdc-acm: fix unthrottle races
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit 764478f41130f1b8d8057575b89e69980a0f600d upstream.
Fix two long-standing bugs which could potentially lead to memory corruption or leave the port throttled until it is reopened (on weakly ordered systems), respectively, when read-URB completion races with unthrottle().
First, the URB must not be marked as free before processing is complete to prevent it from being submitted by unthrottle() on another CPU.
CPU 1 CPU 2 ================ ================ complete() unthrottle() process_urb(); smp_mb__before_atomic(); set_bit(i, free); if (test_and_clear_bit(i, free)) submit_urb();
Second, the URB must be marked as free before checking the throttled flag to prevent unthrottle() on another CPU from failing to observe that the URB needs to be submitted if complete() sees that the throttled flag is set.
CPU 1 CPU 2 ================ ================ complete() unthrottle() set_bit(i, free); throttled = 0; smp_mb__after_atomic(); smp_mb(); if (throttled) if (test_and_clear_bit(i, free)) return; submit_urb();
Note that test_and_clear_bit() only implies barriers when the test is successful. To handle the case where the URB is still in use an explicit barrier needs to be added to unthrottle() for the second race condition.
Also note that the first race was fixed by 36e59e0d70d6 ("cdc-acm: fix race between callback and unthrottle") back in 2015, but the bug was reintroduced a year later.
--- drivers/usb/class/cdc-acm.c | 32 +++++++++++++++++++++++++------- 1 file changed, 25 insertions(+), 7 deletions(-)
drivers/usb/class/cdc-acm.c +25 -7
@@ -470,12 +470,12 @@ static void acm_read_bulk_callback(strucstruct acm *acm = rb->instance;unsigned long flags;int status = urb->status; +bool stopped = false; +bool stalled = false;dev_vdbg (&acm->data->dev,"got urb %d, len %d, status %d\n" , rb->index, urb->actual_length, status); -set_bit (rb->index, &acm->read_urbs_free); -if (!acm->dev) {dev_dbg (&acm->data->dev,"%s - disconnected\n" , __func__);return ;
@@ -488,15 +488,16 @@ static void acm_read_bulk_callback(strucbreak ;case -EPIPE :set_bit (EVENT_RX_STALL , &acm->flags); -schedule_work (&acm->work); -return ; + stalled = true; +break ;case -ENOENT :case -ECONNRESET :case -ESHUTDOWN :dev_dbg (&acm->data->dev,"%s - urb shutting down with status: %d\n" , __func__, status); -return ; + stopped = true; +break ;default : dev_dbg(&acm->data->dev, "%s - nonzero urb status received: %d\n",
@@ -505,10 +506,24 @@ static void acm_read_bulk_callback(struc }/* -* Unthrottle may run on another CPU which needs to see events -* in the same order. Submission has an implict barrier +* Make sure URB processing is done before marking as free to avoid +* racing with unthrottle() on another CPU. Matches the barriers +* implied by the test_and_clear_bit() in acm_submit_read_urb(). */ smp_mb__before_atomic (); +set_bit (rb->index, &acm->read_urbs_free); +/* +* Make sure URB is marked as free before checking the throttled flag +* to avoid racing with unthrottle() on another CPU. Matches the +* smp_mb() in unthrottle(). +*/ +smp_mb__after_atomic (); + +if (stopped || stalled) { +if (stalled) +schedule_work (&acm->work); +return ; + }/* throttle device if requested by tty */ spin_lock_irqsave (&acm->read_lock, flags);
@@ -842,6 +857,9 @@ static void acm_tty_unthrottle(struct tt acm->throttle_req =0 ;spin_unlock_irq (&acm->read_lock); +/* Matches the smp_mb__after_atomic() in acm_read_bulk_callback(). */ +smp_mb (); +if (was_throttled)acm_submit_read_urbs (acm,GFP_KERNEL ); }
Re: [PATCH 4.19 32/66] xtensa: fix initialization of pt_regs::syscall in start_thread
In reply to Greg Kroah-HartmanHello,
Quoted 7 lines · Greg Kroah-Hartman
[ Upstream commit
2663147dc7465cb29040a05cc4286fdd839978b5]New
pt_regsshould indicate that there's no syscall, not that there's syscall #0. While at it wrap macro body in do/while and parenthesize macro arguments.
Quoted 5 lines
Signed-off-by Max Filippov <[email protected]>Signed-off-by Sasha Levin <[email protected]>--- arch/xtensa/include/asm/processor.h | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)
This patch should not be taken to any of the stable trees, except maybe 5.0.y, because NO_SYSCALL was introduced to arch/xtensa in 5.0.
This patch doesn't have any cc:stable tags, I'm curious why was it chosen for stable and what can I do to prevent that in the future?
Signature · 2 lines
Thanks. -- Max
Greg Kroah-Hartman
maintainerPATCH 49/66 iommu/amd: Set exclusion range correctly
In reply to Greg Kroah-Hartman[ Upstream commit 3c677d206210f53a4be972211066c0f1cd47fe12 ]
The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons.
So correctly set the exclusion range in the hardware to the last page which is _in_ the range.
--- drivers/iommu/amd_iommu_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/iommu/amd_iommu_init.c +1 -1
@@ -356,7 +356,7 @@ static void iommu_write_l2(struct amd_iommu *iommu, u8 address, u32 val)static void iommu_set_exclusion_range (struct amd_iommu *iommu) {u64 start = iommu->exclusion_start &PAGE_MASK ; -u64 limit = (start + iommu->exclusion_length) &PAGE_MASK ; +u64 limit = (start + iommu->exclusion_length -1 ) &PAGE_MASK ;u64 entry;if (!iommu->exclusion_start)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 48/66 perf/core: Fix perf_event_disable_inatomic() race
In reply to Greg Kroah-Hartman[ Upstream commit 1d54ad944074010609562da5c89e4f5df2f4e5db ]
Thomas-Mich Richter reported he triggered a WARN()ing from event_function_local() on his s390. The problem boils down to:
CPU-A CPU-B perf_event_overflow() perf_event_disable_inatomic() @pending_disable = 1 irq_work_queue(); sched-out event_sched_out() @pending_disable = 0 sched-in perf_event_overflow() perf_event_disable_inatomic() @pending_disable = 1; irq_work_queue(); // FAILS irq_work_run() perf_pending_event() if (@pending_disable) perf_event_disable_local(); // WHOOPS
The problem exists in generic, but s390 is particularly sensitive because it doesn't implement arch_irq_work_raise(), nor does it call irq_work_run() from it's PMU interrupt handler (nor would that be sufficient in this case, because s390 also generates perf_event_overflow() from pmu::stop). Add to that the fact that s390 is a virtual architecture and (virtual) CPU-A can stall long enough for the above race to happen, even if it would self-IPI.
Adding a irq_work_sync() to event_sched_in() would work for all hardare PMUs that properly use irq_work_run() but fails for software PMUs.
Instead encode the CPU number in @pending_disable, such that we can tell which CPU requested the disable. This then allows us to detect the above scenario and even redirect the IPI to make up for the failed queue.
--- kernel/events/core.c | 52 ++++++++++++++++++++++++++++++------- kernel/events/ring_buffer.c | 4 +-- 2 files changed, 45 insertions(+), 11 deletions(-)
kernel/events/core.c +43 -9
@@ -2007,8 +2007,8 @@ event_sched_out(struct perf_event *event, event->pmu->del (event,0 ); event->oncpu =-1 ; -if (event->pending_disable) { - event->pending_disable =0 ; +if (READ_ONCE (event->pending_disable) >=0 ) { +WRITE_ONCE (event->pending_disable,-1 ); state =PERF_EVENT_STATE_OFF ; }perf_event_set_state (event, state);
@@ -2196,7 +2196,8 @@ EXPORT_SYMBOL_GPL(perf_event_disable);void perf_event_disable_inatomic (struct perf_event *event) { - event->pending_disable =1 ; +WRITE_ONCE (event->pending_disable,smp_processor_id ()); +/* can fail, see perf_pending_event_disable() */ irq_work_queue (&event->pending); }
@@ -5803,10 +5804,45 @@ void perf_event_wakeup(struct perf_event *event) } } +static void perf_pending_event_disable (struct perf_event *event) +{ +int cpu =READ_ONCE (event->pending_disable); + +if (cpu <0 ) +return ; + +if (cpu ==smp_processor_id ()) { +WRITE_ONCE (event->pending_disable,-1 ); +perf_event_disable_local (event); +return ; + } + +/* +* CPU-A CPU-B +* +* perf_event_disable_inatomic() +* @pending_disable = CPU-A; +* irq_work_queue(); +* +* sched-out +* @pending_disable = -1; +* +* sched-in +* perf_event_disable_inatomic() +* @pending_disable = CPU-B; +* irq_work_queue(); // FAILS +* +* irq_work_run() +* perf_pending_event() +* +* But the event runs on CPU-B and wants disabling there. +*/ +irq_work_queue_on (&event->pending, cpu); +} +static void perf_pending_event (struct irq_work *entry) { -struct perf_event *event =container_of (entry, - struct perf_event, pending); + struct perf_event *event = container_of(entry, struct perf_event, pending);int rctx; rctx =perf_swevent_get_recursion_context ();
@@ -5815,10 +5851,7 @@ static void perf_pending_event(struct irq_work *entry)* and we won't recurse 'further'. */ -if (event->pending_disable) { - event->pending_disable =0 ; -perf_event_disable_local (event); - } +perf_pending_event_disable (event);if (event->pending_wakeup) { event->pending_wakeup =0 ;
@@ -9969,6 +10002,7 @@ perf_event_alloc(struct perf_event_attr *attr, int cpu,init_waitqueue_head (&event->waitq); + event->pending_disable =-1 ;init_irq_work (&event->pending, perf_pending_event);mutex_init (&event->mmap_mutex);
kernel/events/ring_buffer.c +2 -2
@@ -393,7 +393,7 @@ void *perf_aux_output_begin(struct perf_output_handle *handle,* store that will be enabled on successful return */ if (!handle->size) {/* A, matches D */ - event->pending_disable =1 ; + event->pending_disable =smp_processor_id ();perf_output_wakeup (handle);local_set (&rb->aux_nest,0 ); goto err_put;
@@ -471,7 +471,7 @@ void perf_aux_output_end(struct perf_output_handle *handle, unsigned long size)if (wakeup) {if (handle->aux_flags &PERF_AUX_FLAG_TRUNCATED ) - handle->event->pending_disable =1 ; + handle->event->pending_disable =smp_processor_id ();perf_output_wakeup (handle); }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 61/66 Bluetooth: hidp: fix buffer overflow
In reply to Greg Kroah-HartmanFrom: Young Xiao <[email protected]>
commit a1616a5ac99ede5d605047a9012481ce7ff18b16 upstream.
Struct ca is copied from userspace. It is not checked whether the "name" field is NULL terminated, which allows local users to obtain potentially sensitive information from kernel stack memory, via a HIDPCONNADD command.
This vulnerability is similar to CVE-2011-1079.
--- net/bluetooth/hidp/sock.c | 1 + 1 file changed, 1 insertion(+)
net/bluetooth/hidp/sock.c +1 -0
@@ -76,6 +76,7 @@ static int hidp_sock_ioctl(struct socketsockfd_put (csock);return err; } + ca.name[sizeof (ca.name)-1 ] =0 ; err =hidp_connection_add (&ca, csock, isock);if (!err &©_to_user (argp, &ca,sizeof (ca)))
Greg Kroah-Hartman
maintainerPATCH 59/66 scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines
In reply to Greg Kroah-HartmanFrom: Andrew Vasquez <[email protected]>
commit 5cbdae10bf11f96e30b4d14de7b08c8b490e903c upstream.
Commit e6f77540c067 ("scsi: qla2xxx: Fix an integer overflow in sysfs code") incorrectly set 'optrom_region_size' to 'start+size', which can overflow option-rom boundaries when 'start' is non-zero. Continue setting optrom_region_size to the proper adjusted value of 'size'.
--- drivers/scsi/qla2xxx/qla_attr.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/scsi/qla2xxx/qla_attr.c +2 -2
@@ -345,7 +345,7 @@ qla2x00_sysfs_write_optrom_ctl(struct fi } ha->optrom_region_start = start; - ha->optrom_region_size = start + size; + ha->optrom_region_size = size; ha->optrom_state =QLA_SREADING ; ha->optrom_buffer =vmalloc (ha->optrom_region_size);
@@ -418,7 +418,7 @@ qla2x00_sysfs_write_optrom_ctl(struct fi } ha->optrom_region_start = start; - ha->optrom_region_size = start + size; + ha->optrom_region_size = size; ha->optrom_state =QLA_SWRITING ; ha->optrom_buffer =vmalloc (ha->optrom_region_size);
Greg Kroah-Hartman
maintainerPATCH 57/66 soc: sunxi: Fix missing dependency on REGMAP_MMIO
In reply to Greg Kroah-HartmanFrom: Samuel Holland <[email protected]>
commit a84014e1db35d8e7af09878d0b4bf30804fb17d5 upstream.
When enabling ARCH_SUNXI from allnoconfig, SUNXI_SRAM is enabled, but not REGMAP_MMIO, so the kernel fails to link with an undefined reference to __devm_regmap_init_mmio_clk. Select REGMAP_MMIO, as suggested in drivers/base/regmap/Kconfig.
This creates the following dependency loop:
drivers/of/Kconfig:68: symbol OF_IRQ depends on IRQ_DOMAIN kernel/irq/Kconfig:63: symbol IRQ_DOMAIN is selected by REGMAP drivers/base/regmap/Kconfig:7: symbol REGMAP default is visible depending on REGMAP_MMIO drivers/base/regmap/Kconfig:39: symbol REGMAP_MMIO is selected by SUNXI_SRAM drivers/soc/sunxi/Kconfig:4: symbol SUNXI_SRAM is selected by USB_MUSB_SUNXI drivers/usb/musb/Kconfig:63: symbol USB_MUSB_SUNXI depends on GENERIC_PHY drivers/phy/Kconfig:7: symbol GENERIC_PHY is selected by PHY_BCM_NS_USB3 drivers/phy/broadcom/Kconfig:29: symbol PHY_BCM_NS_USB3 depends on MDIO_BUS drivers/net/phy/Kconfig:12: symbol MDIO_BUS default is visible depending on PHYLIB drivers/net/phy/Kconfig:181: symbol PHYLIB is selected by ARC_EMAC_CORE drivers/net/ethernet/arc/Kconfig:18: symbol ARC_EMAC_CORE is selected by ARC_EMAC drivers/net/ethernet/arc/Kconfig:24: symbol ARC_EMAC depends on OF_IRQ
To fix the circular dependency, make USB_MUSB_SUNXI select GENERIC_PHY instead of depending on it. This matches the use of GENERIC_PHY by all but two other drivers.
--- drivers/soc/sunxi/Kconfig | 1 + drivers/usb/musb/Kconfig | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-)
drivers/soc/sunxi/Kconfig +1 -0
@@ -4,6 +4,7 @@ config SUNXI_SRAM bool default ARCH_SUNXI + select REGMAP_MMIO help Say y here to enable the SRAM controller support. This device is responsible on mapping the SRAM in the sunXi SoCs
drivers/usb/musb/Kconfig +1 -1
@@ -66,7 +66,7 @@ config USB_MUSB_SUNXI depends on NOP_USB_XCEIV depends on PHY_SUN4I_USB depends on EXTCON - depends on GENERIC_PHY + select GENERIC_PHY select SUNXI_SRAM config USB_MUSB_DAVINCI
Greg Kroah-Hartman
maintainerPATCH 8/66 ASoC: hdmi-codec: fix S/PDIF DAI
In reply to Greg Kroah-Hartman[ Upstream commit 2e95f984aae4cf0608d0ba2189c756f2bd50b44a ]
When using the S/PDIF DAI, there is no requirement to call snd_soc_dai_set_fmt() as there is no DAI format definition that defines S/PDIF. In any case, S/PDIF does not have separate clocks, this is embedded into the data stream.
Consequently, when attempting to use TDA998x in S/PDIF mode, the attempt to configure TDA998x via the hw_params callback fails as the hdmi_codec_daifmt is left initialised to zero.
Since the S/PDIF DAI will only be used by S/PDIF, prepare the hdmi_codec_daifmt structure for this format.
--- sound/soc/codecs/hdmi-codec.c | 118 +++++++++++++++++----------------- 1 file changed, 59 insertions(+), 59 deletions(-)
sound/soc/codecs/hdmi-codec.c +59 -59
@@ -529,73 +529,71 @@ static int hdmi_codec_set_fmt(struct snd_soc_dai *dai, {struct hdmi_codec_priv *hcp =snd_soc_dai_get_drvdata (dai);struct hdmi_codec_daifmt cf = {0 }; -int ret =0 ;dev_dbg (dai->dev,"%s()\n" , __func__); -if (dai->id ==DAI_ID_SPDIF ) { - cf.fmt =HDMI_SPDIF ; - }else { -switch (fmt &SND_SOC_DAIFMT_MASTER_MASK ) { -case SND_SOC_DAIFMT_CBM_CFM : - cf.bit_clk_master =1 ; - cf.frame_clk_master =1 ; -break ; -case SND_SOC_DAIFMT_CBS_CFM : - cf.frame_clk_master =1 ; -break ; -case SND_SOC_DAIFMT_CBM_CFS : - cf.bit_clk_master =1 ; -break ; -case SND_SOC_DAIFMT_CBS_CFS : -break ; -default : -return -EINVAL ; - } +if (dai->id ==DAI_ID_SPDIF ) +return 0 ; + +switch (fmt &SND_SOC_DAIFMT_MASTER_MASK ) { +case SND_SOC_DAIFMT_CBM_CFM : + cf.bit_clk_master =1 ; + cf.frame_clk_master =1 ; +break ; +case SND_SOC_DAIFMT_CBS_CFM : + cf.frame_clk_master =1 ; +break ; +case SND_SOC_DAIFMT_CBM_CFS : + cf.bit_clk_master =1 ; +break ; +case SND_SOC_DAIFMT_CBS_CFS : +break ; +default : +return -EINVAL ; + } -switch (fmt &SND_SOC_DAIFMT_INV_MASK ) { -case SND_SOC_DAIFMT_NB_NF : -break ; -case SND_SOC_DAIFMT_NB_IF : - cf.frame_clk_inv =1 ; -break ; -case SND_SOC_DAIFMT_IB_NF : - cf.bit_clk_inv =1 ; -break ; -case SND_SOC_DAIFMT_IB_IF : - cf.frame_clk_inv =1 ; - cf.bit_clk_inv =1 ; -break ; - } +switch (fmt &SND_SOC_DAIFMT_INV_MASK ) { +case SND_SOC_DAIFMT_NB_NF : +break ; +case SND_SOC_DAIFMT_NB_IF : + cf.frame_clk_inv =1 ; +break ; +case SND_SOC_DAIFMT_IB_NF : + cf.bit_clk_inv =1 ; +break ; +case SND_SOC_DAIFMT_IB_IF : + cf.frame_clk_inv =1 ; + cf.bit_clk_inv =1 ; +break ; + } -switch (fmt &SND_SOC_DAIFMT_FORMAT_MASK ) { -case SND_SOC_DAIFMT_I2S : - cf.fmt =HDMI_I2S ; -break ; -case SND_SOC_DAIFMT_DSP_A : - cf.fmt =HDMI_DSP_A ; -break ; -case SND_SOC_DAIFMT_DSP_B : - cf.fmt =HDMI_DSP_B ; -break ; -case SND_SOC_DAIFMT_RIGHT_J : - cf.fmt =HDMI_RIGHT_J ; -break ; -case SND_SOC_DAIFMT_LEFT_J : - cf.fmt =HDMI_LEFT_J ; -break ; -case SND_SOC_DAIFMT_AC97 : - cf.fmt =HDMI_AC97 ; -break ; -default : -dev_err (dai->dev,"Invalid DAI interface format\n" ); -return -EINVAL ; - } +switch (fmt &SND_SOC_DAIFMT_FORMAT_MASK ) { +case SND_SOC_DAIFMT_I2S : + cf.fmt =HDMI_I2S ; +break ; +case SND_SOC_DAIFMT_DSP_A : + cf.fmt =HDMI_DSP_A ; +break ; +case SND_SOC_DAIFMT_DSP_B : + cf.fmt =HDMI_DSP_B ; +break ; +case SND_SOC_DAIFMT_RIGHT_J : + cf.fmt =HDMI_RIGHT_J ; +break ; +case SND_SOC_DAIFMT_LEFT_J : + cf.fmt =HDMI_LEFT_J ; +break ; +case SND_SOC_DAIFMT_AC97 : + cf.fmt =HDMI_AC97 ; +break ; +default : +dev_err (dai->dev,"Invalid DAI interface format\n" ); +return -EINVAL ; } hcp->daifmt[dai->id] = cf; -return ret; +return 0 ; }static int hdmi_codec_digital_mute (struct snd_soc_dai *dai,int mute)
@@ -792,8 +790,10 @@ static int hdmi_codec_probe(struct platform_device *pdev) i++; } -if (hcd->spdif) +if (hcd->spdif) { hcp->daidrv[i] = hdmi_spdif_dai; + hcp->daifmt[DAI_ID_SPDIF ].fmt =HDMI_SPDIF ; + }dev_set_drvdata (dev, hcp);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 15/66 ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate
In reply to Greg Kroah-Hartman[ Upstream commit 2b13bee3884926cba22061efa75bd315e871de24 ]
After commit fbeec965b8d1c ("ASoC: samsung: odroid: Fix 32000 sample rate handling") the audio root clock frequency is configured improperly for 44100 sample rate. Due to clock rate rounding it's 20070401 Hz instead of 22579000 Hz. This results in a too low value of the PSR clock divider in the CPU DAI driver and too fast actual sample rate for fs=44100. E.g. 1 kHz tone has actual 1780 Hz frequency (1 kHz * 20070401/22579000 * 2).
Fix this by increasing the correction passed to clk_set_rate() to take into account inaccuracy of the EPLL frequency properly.
--- sound/soc/samsung/odroid.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
sound/soc/samsung/odroid.c +2 -2
@@ -64,11 +64,11 @@ static int odroid_card_hw_params(struct snd_pcm_substream *substream,return ret;/* -* We add 1 to the rclk_freq value in order to avoid too low clock +* We add 2 to the rclk_freq value in order to avoid too low clock * frequency values due to the EPLL output frequency not being exact * multiple of the audio sampling rate. */ - rclk_freq =params_rate (params) * rfs +1 ; + rclk_freq =params_rate (params) * rfs +2 ; ret =clk_set_rate (priv->sclk_i2s, rclk_freq);if (ret <0 )
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 13/66 ASoC: nau8824: fix the issue of the widget with prefix name
In reply to Greg Kroah-Hartman[ Upstream commit 844a4a362dbec166b44d6b9b3dd45b08cb273703 ]
The driver has two issues when machine add prefix name for codec. (1)The stream name of DAI can't find the AIF widgets. (2)The drivr can enable/disalbe the MICBIAS and SAR widgets.
The patch will fix these issues caused by prefixed name added.
--- sound/soc/codecs/nau8824.c | 46 +++++++++++++++++++++++++++++++------- 1 file changed, 38 insertions(+), 8 deletions(-)
sound/soc/codecs/nau8824.c +38 -8
@@ -681,8 +681,8 @@ static const struct snd_soc_dapm_widget nau8824_dapm_widgets[] = {SND_SOC_DAPM_ADC ("ADCR" ,NULL ,NAU8824_REG_ANALOG_ADC_2 ,NAU8824_ADCR_EN_SFT ,0 ), -SND_SOC_DAPM_AIF_OUT ("AIFTX" ,"HiFi Capture" ,0 ,SND_SOC_NOPM ,0 ,0 ), -SND_SOC_DAPM_AIF_IN ("AIFRX" ,"HiFi Playback" ,0 ,SND_SOC_NOPM ,0 ,0 ), +SND_SOC_DAPM_AIF_OUT ("AIFTX" ,"Capture" ,0 ,SND_SOC_NOPM ,0 ,0 ), +SND_SOC_DAPM_AIF_IN ("AIFRX" ,"Playback" ,0 ,SND_SOC_NOPM ,0 ,0 ),SND_SOC_DAPM_DAC ("DACL" ,NULL ,NAU8824_REG_RDAC , NAU8824_DACL_EN_SFT, 0),
@@ -831,6 +831,36 @@ static void nau8824_int_status_clear_all(struct regmap *regmap) } } +static void nau8824_dapm_disable_pin (struct nau8824 *nau8824,const char *pin) +{ +struct snd_soc_dapm_context *dapm = nau8824->dapm; +const char *prefix = dapm->component->name_prefix; +char prefixed_pin[80 ]; + +if (prefix) { +snprintf (prefixed_pin,sizeof (prefixed_pin),"%s %s" , + prefix, pin); +snd_soc_dapm_disable_pin (dapm, prefixed_pin); + }else { +snd_soc_dapm_disable_pin (dapm, pin); + } +} + +static void nau8824_dapm_enable_pin (struct nau8824 *nau8824,const char *pin) +{ +struct snd_soc_dapm_context *dapm = nau8824->dapm; +const char *prefix = dapm->component->name_prefix; +char prefixed_pin[80 ]; + +if (prefix) { +snprintf (prefixed_pin,sizeof (prefixed_pin),"%s %s" , + prefix, pin); +snd_soc_dapm_force_enable_pin (dapm, prefixed_pin); + }else { +snd_soc_dapm_force_enable_pin (dapm, pin); + } +} +static void nau8824_eject_jack (struct nau8824 *nau8824) {struct snd_soc_dapm_context *dapm = nau8824->dapm;
@@ -839,8 +869,8 @@ static void nau8824_eject_jack(struct nau8824 *nau8824)/* Clear all interruption status */ nau8824_int_status_clear_all (regmap); -snd_soc_dapm_disable_pin (dapm,"SAR" ); -snd_soc_dapm_disable_pin (dapm,"MICBIAS" ); +nau8824_dapm_disable_pin (nau8824,"SAR" ); +nau8824_dapm_disable_pin (nau8824,"MICBIAS" );snd_soc_dapm_sync (dapm);/* Enable the insertion interruption, disable the ejection
@@ -870,8 +900,8 @@ static void nau8824_jdet_work(struct work_struct *work)struct regmap *regmap = nau8824->regmap;int adc_value, event =0 , event_mask =0 ; -snd_soc_dapm_force_enable_pin (dapm,"MICBIAS" ); -snd_soc_dapm_force_enable_pin (dapm,"SAR" ); +nau8824_dapm_enable_pin (nau8824,"MICBIAS" ); +nau8824_dapm_enable_pin (nau8824,"SAR" );snd_soc_dapm_sync (dapm);msleep (100 );
@@ -882,8 +912,8 @@ static void nau8824_jdet_work(struct work_struct *work)if (adc_value <HEADSET_SARADC_THD ) { event |=SND_JACK_HEADPHONE ; -snd_soc_dapm_disable_pin (dapm,"SAR" ); -snd_soc_dapm_disable_pin (dapm,"MICBIAS" ); +nau8824_dapm_disable_pin (nau8824,"SAR" ); +nau8824_dapm_disable_pin (nau8824,"MICBIAS" );snd_soc_dapm_sync (dapm); }else { event |=SND_JACK_HEADSET ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 40/66 RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove
In reply to Greg Kroah-Hartman[ Upstream commit ea7a5c706fa49273cf6d1d9def053ecb50db2076 ]
Make sure to free the DSR on pvrdma_pci_remove() to avoid the memory leak.
--- drivers/infiniband/hw/vmw_pvrdma/pvrdma_main.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/infiniband/hw/vmw_pvrdma/pvrdma_main.c +2 -0
@@ -1123,6 +1123,8 @@ static void pvrdma_pci_remove(struct pci_dev *pdev)pvrdma_page_dir_cleanup (dev, &dev->cq_pdir);pvrdma_page_dir_cleanup (dev, &dev->async_pdir);pvrdma_free_slots (dev); +dma_free_coherent (&pdev->dev,sizeof (*dev->dsr), dev->dsr, + dev->dsrbase);iounmap (dev->regs);kfree (dev->sgid_tbl);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 36/66 objtool: Add rewind_stack_do_exit() to the noreturn list
In reply to Greg Kroah-Hartman[ Upstream commit 4fa5ecda2bf96be7464eb406df8aba9d89260227 ]
This fixes the following warning seen on GCC 7.3:
arch/x86/kernel/dumpstack.o: warning: objtool: oops_end() falls through to next function show_regs()
--- tools/objtool/check.c | 1 + 1 file changed, 1 insertion(+)
tools/objtool/check.c +1 -0
@@ -165,6 +165,7 @@ static int __dead_end_function(struct objtool_file *file, struct symbol *func,"fortify_panic" ,"usercopy_abort" ,"machine_real_restart" , + "rewind_stack_do_exit", };if (func->bind ==STB_WEAK )
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 11/66 ASoC:soc-pcm:fix a codec fixup issue in TDM case
In reply to Greg Kroah-Hartman[ Upstream commit 570f18b6a8d1f0e60e8caf30e66161b6438dcc91 ]
On HDaudio platforms, if playback is started when capture is working, there is no audible output.
This can be root-caused to the use of the rx|tx_mask to store an HDaudio stream tag.
If capture is stared before playback, rx_mask would be non-zero on HDaudio platform, then the channel number of playback, which is in the same codec dai with the capture, would be changed by soc_pcm_codec_params_fixup based on the tx_mask at first, then overwritten by this function based on rx_mask at last.
According to the author of tx|rx_mask, tx_mask is for playback and rx_mask is for capture. And stream direction is checked at all other references of tx|rx_mask in ASoC, so here should be an error. This patch checks stream direction for tx|rx_mask for fixup function.
This issue would affect not only HDaudio+ASoC, but also I2S codecs if the channel number based on rx_mask is not equal to the one for tx_mask. It could be rarely reproduecd because most drivers in kernel set the same channel number to tx|rx_mask or rx_mask is zero.
Tested on all platforms using stream_tag & HDaudio and intel I2S platforms.
--- sound/soc/soc-pcm.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
sound/soc/soc-pcm.c +5 -2
@@ -957,10 +957,13 @@ static int soc_pcm_hw_params(struct snd_pcm_substream *substream, codec_params = *params;/* fixup params based on TDM slot masks */ -if (codec_dai->tx_mask) +if (substream->stream ==SNDRV_PCM_STREAM_PLAYBACK && + codec_dai->tx_mask)soc_pcm_codec_params_fixup (&codec_params, codec_dai->tx_mask); -if (codec_dai->rx_mask) + +if (substream->stream ==SNDRV_PCM_STREAM_CAPTURE && + codec_dai->rx_mask)soc_pcm_codec_params_fixup (&codec_params, codec_dai->rx_mask);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 31/66 linux/kernel.h: Use parentheses around argument in u64_to_user_ptr()
In reply to Greg Kroah-Hartman[ Upstream commit a0fe2c6479aab5723239b315ef1b552673f434a3 ]
Use parentheses around uses of the argument in u64_to_user_ptr() to ensure that the cast doesn't apply to part of the argument.
There are existing uses of the macro of the form
u64_to_user_ptr(A + B)
which expands to
(void __user *)(uintptr_t)A + B
(the cast applies to the first operand of the addition, the addition is a pointer addition). This happens to still work as intended, the semantic difference doesn't cause a difference in behavior.
But I want to use u64_to_user_ptr() with a ternary operator in the argument, like so:
u64_to_user_ptr(A ? B : C)
This currently doesn't work as intended.
--- include/linux/kernel.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
include/linux/kernel.h +2 -2
@@ -73,8 +73,8 @@#define u64_to_user_ptr (x) ( \ { \ - typecheck(u64, x); \ - (void __user *)(uintptr_t)x; \ + typecheck(u64, (x)); \ + (void __user *)(uintptr_t)(x); \ } \ )
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 28/66 drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata()
In reply to Greg Kroah-Hartman[ Upstream commit 2d85978341e6a32e7443d9f28639da254d53f400 ]
We don't want to overwrite "ret", it already holds the correct error code. The "regmap" variable might be a valid pointer as this point.
--- drivers/gpu/drm/mediatek/mtk_hdmi.c | 1 - 1 file changed, 1 deletion(-)
drivers/gpu/drm/mediatek/mtk_hdmi.c +0 -1
@@ -1473,7 +1473,6 @@ static int mtk_hdmi_dt_parse_pdata(struct mtk_hdmi *hdmi,if (IS_ERR (regmap)) ret =PTR_ERR (regmap);if (ret) { - ret =PTR_ERR (regmap);dev_err (dev,"Failed to get system configuration registers: %d\n" , ret);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 26/66 MIPS: KGDB: fix kgdb support for SMP platforms.
In reply to Greg Kroah-Hartman[ Upstream commit ab8a6d821179ab9bea1a9179f535ccba6330c1ed ]
KGDB_call_nmi_hook is called by other cpu through smp call. MIPS smp call is processed in ipi irq handler and regs is saved in
handle_int.
So kgdb_call_nmi_hook get regs by get_irq_regs and regs will be passed
to kgdb_cpu_enter.
--- arch/mips/kernel/kgdb.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/mips/kernel/kgdb.c +2 -1
@@ -33,6 +33,7 @@#include <asm/processor.h> #include <asm/sigcontext.h> #include <linux/uaccess.h> +#include <asm/irq_regs.h> static struct hard_trap_info { unsigned char tt; /* Trap type code for MIPS R3xxx and R4xxx */
@@ -214,7 +215,7 @@ static void kgdb_call_nmi_hook(void *ignored) old_fs =get_fs ();set_fs (get_ds ()); -kgdb_nmicallback (raw_smp_processor_id (),NULL ); +kgdb_nmicallback (raw_smp_processor_id (),get_irq_regs ());set_fs (old_fs); }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 21/66 ASoC: cs4270: Set auto-increment bit for register writes
In reply to Greg Kroah-Hartman[ Upstream commit f0f2338a9cfaf71db895fa989ea7234e8a9b471d ]
The CS4270 does not by default increment the register address on consecutive writes. During normal operation it doesn't matter as all register accesses are done individually. At resume time after suspend, however, the regcache code gathers the biggest possible block of registers to sync and sends them one on one go.
To fix this, set the INCR bit in all cases.
--- sound/soc/codecs/cs4270.c | 1 + 1 file changed, 1 insertion(+)
sound/soc/codecs/cs4270.c +1 -0
@@ -642,6 +642,7 @@ static const struct regmap_config cs4270_regmap = { .reg_defaults = cs4270_reg_defaults, .num_reg_defaults = ARRAY_SIZE(cs4270_reg_defaults), .cache_type = REGCACHE_RBTREE, + .write_flag_mask = CS4270_I2C_INCR, .readable_reg = cs4270_reg_is_readable, .volatile_reg = cs4270_reg_is_volatile,
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 19/66 ASoC: stm32: dfsdm: manage multiple prepare
In reply to Greg Kroah-Hartman[ Upstream commit 19441e35a43b616ea6afad91ed0d9e77268d8f6a ]
The DFSDM must be stopped when a new setting is applied. restart systematically DFSDM on multiple prepare calls, to apply changes.
--- sound/soc/stm/stm32_adfsdm.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-)
sound/soc/stm/stm32_adfsdm.c +16 -1
@@ -9,6 +9,7 @@#include <linux/clk.h> #include <linux/module.h> +#include <linux/mutex.h> #include <linux/platform_device.h> #include <linux/slab.h>
@@ -37,6 +38,8 @@ struct stm32_adfsdm_priv {/* PCM buffer */ unsigned char *pcm_buff;unsigned int pos; + +struct mutex lock;/* protect against race condition on iio state */ };static const struct snd_pcm_hardware stm32_adfsdm_pcm_hw = {
@@ -62,10 +65,12 @@ static void stm32_adfsdm_shutdown(struct snd_pcm_substream *substream, {struct stm32_adfsdm_priv *priv =snd_soc_dai_get_drvdata (dai); +mutex_lock (&priv->lock);if (priv->iio_active) {iio_channel_stop_all_cb (priv->iio_cb); priv->iio_active = false; } +mutex_unlock (&priv->lock); } static int stm32_adfsdm_dai_prepare(struct snd_pcm_substream *substream,
@@ -74,13 +79,19 @@ static int stm32_adfsdm_dai_prepare(struct snd_pcm_substream *substream,struct stm32_adfsdm_priv *priv =snd_soc_dai_get_drvdata (dai);int ret; +mutex_lock (&priv->lock); +if (priv->iio_active) { +iio_channel_stop_all_cb (priv->iio_cb); + priv->iio_active = false; + } + ret =iio_write_channel_attribute (priv->iio_ch, substream->runtime->rate,0 ,IIO_CHAN_INFO_SAMP_FREQ );if (ret <0 ) {dev_err (dai->dev,"%s: Failed to set %d sampling rate\n" , __func__, substream->runtime->rate); -return ret; + goto out; }if (!priv->iio_active) {
@@ -92,6 +103,9 @@ static int stm32_adfsdm_dai_prepare(struct snd_pcm_substream *substream, __func__, ret); } +out: +mutex_unlock (&priv->lock); +return ret; }
@@ -298,6 +312,7 @@ static int stm32_adfsdm_probe(struct platform_device *pdev) priv->dev = &pdev->dev; priv->dai_drv = stm32_adfsdm_dai; +mutex_init (&priv->lock);dev_set_drvdata (&pdev->dev, priv);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainercover 4.19.42-stable review
This is the start of the stable review cycle for the 4.19.42 release. There are 66 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 11 May 2019 06:11:18 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.42-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 4.19.42-rc1
Will Deacon <[email protected]>
arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP
Will Deacon <[email protected]>
locking/futex: Allow low-level atomic operations to return -EAGAIN
Ross Zwisler <[email protected]>
ASoC: Intel: avoid Oops if DMA setup fails
Oliver Neukum <[email protected]>
UAS: fix alignment of scatter/gather segments
Marcel Holtmann <[email protected]>
Bluetooth: Align minimum encryption key size for LE and BR/EDR connections
Young Xiao <[email protected]>
Bluetooth: hidp: fix buffer overflow
Quinn Tran <[email protected]>
scsi: qla2xxx: Fix device staying in blocked state
Andrew Vasquez <[email protected]>
scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines
Silvio Cesare <[email protected]>
scsi: lpfc: change snprintf to scnprintf for possible overflow
Samuel Holland <[email protected]>
soc: sunxi: Fix missing dependency on REGMAP_MMIO
Gregory CLEMENT <[email protected]>
cpufreq: armada-37xx: fix frequency calculation for opp
Alexander Shishkin <[email protected]>
intel_th: pci: Add Comet Lake support
Alan Stern <[email protected]>
usb-storage: Set virt_boundary_mask to avoid SG overflows
Johan Hovold <[email protected]>
USB: cdc-acm: fix unthrottle races
Ji-Ze Hong (Peter Hong) <[email protected]>
USB: serial: f81232: fix interrupt worker not stop
Thinh Nguyen <[email protected]>
usb: dwc3: Fix default lpm_nyet_threshold value
Prasad Sodagudi <[email protected]>
genirq: Prevent use-after-free and work list corruption
Joerg Roedel <[email protected]>
iommu/amd: Set exclusion range correctly
Peter Zijlstra <[email protected]>
perf/core: Fix perf_event_disable_inatomic() race
Stephen Boyd <[email protected]>
platform/x86: pmc_atom: Drop __initconst on dmi table
James Smart <[email protected]>
nvme-fc: correct csn initialization and increments on error
Dongli Zhang <[email protected]>
virtio-blk: limit number of hw queues by nr_cpu_ids
Tzung-Bi Shih <[email protected]>
ASoC: Intel: kbl: fix wrong number of channels
Wen Yang <[email protected]>
drm/mediatek: fix possible object reference leak
Varun Prakash <[email protected]>
scsi: csiostor: fix missing data copy in csio_scsi_err_handler()
Lijun Ou <[email protected]>
RDMA/hns: Fix bug that caused srq creation to fail
Kamal Heib <[email protected]>
RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove
Longpeng <[email protected]>
virtio_pci: fix a NULL pointer reference in vp_del_vqs
Ondrej Jirman <[email protected]>
drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind
Qian Cai <[email protected]>
slab: fix a crash by reading /proc/slab_allocators
Josh Poimboeuf <[email protected]>
objtool: Add rewind_stack_do_exit() to the noreturn list
Charles Keepax <[email protected]>
ASoC: cs35l35: Disable regulators on driver removal
tiancyin <[email protected]>
drm/amd/display: fix cursor black issue
Sugar Zhang <[email protected]>
ASoC: rockchip: pdm: fix regmap_ops hang issue
Max Filippov <[email protected]>
xtensa: fix initialization of pt_regs::syscall in start_thread
Jann Horn <[email protected]>
linux/kernel.h: Use parentheses around argument in u64_to_user_ptr()
Peter Zijlstra <[email protected]>
perf/x86/intel: Initialize TFA MSR
Stephane Eranian <[email protected]>
perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS
Dan Carpenter <[email protected]>
drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata()
Annaliese McDermond <[email protected]>
ASoC: tlv320aic32x4: Fix Common Pins
Chong Qiao <[email protected]>
MIPS: KGDB: fix kgdb support for SMP platforms.
Kaike Wan <[email protected]>
IB/hfi1: Fix the allocation of RSM table
Kaike Wan <[email protected]>
IB/hfi1: Eliminate opcode tests on mr deref
Tony Lindgren <[email protected]>
drm/omap: hdmi4_cec: Fix CEC clock handling for PM
Pankaj Bharadiya <[email protected]>
ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol
Daniel Mack <[email protected]>
ASoC: cs4270: Set auto-increment bit for register writes
Olivier Moysan <[email protected]>
ASoC: stm32: dfsdm: fix debugfs warnings on entry creation
Olivier Moysan <[email protected]>
ASoC: stm32: dfsdm: manage multiple prepare
Maxime Jourdan <[email protected]>
clk: meson-gxbb: round the vdec dividers to closest
Charles Keepax <[email protected]>
ASoC: wm_adsp: Add locking to wm_adsp2_bus_error
Shuming Fan <[email protected]>
ASoC: rt5682: recording has no sound after booting
Sylwester Nawrocki <[email protected]>
ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate
John Hsu <[email protected]>
ASoC: nau8810: fix the issue of widget with prefixed name
John Hsu <[email protected]>
ASoC: nau8824: fix the issue of the widget with prefix name
Rander Wang <[email protected]>
ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform
Rander Wang <[email protected]>
ASoC:soc-pcm:fix a codec fixup issue in TDM case
Olivier Moysan <[email protected]>
ASoC: stm32: sai: fix exposed capabilities in spdif mode
Olivier Moysan <[email protected]>
ASoC: stm32: sai: fix iec958 controls indexation
Russell King <[email protected]>
ASoC: hdmi-codec: fix S/PDIF DAI
Philipp Puschmann <[email protected]>
ASoC: tlv320aic3x: fix reset gpio reference counting
Suresh Udipi <[email protected]>
staging: most: cdev: fix chrdev_region leak in mod_exit
Johan Hovold <[email protected]>
staging: greybus: power_supply: fix prop-descriptor request size
Andrey Ryabinin <[email protected]>
ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings
Dexuan Cui <[email protected]>
Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup()
Jason Yan <[email protected]>
scsi: libsas: fix a race condition when smp task timeout
YueHaibing <[email protected]>
net: stmmac: Use bfsize1 in ndesc_init_rx_desc
-------------
Diffstat:
Makefile | 4 +- arch/arm64/include/asm/futex.h | 55 ++- arch/mips/kernel/kgdb.c | 3 +- arch/x86/events/intel/core.c | 8 +- arch/xtensa/include/asm/processor.h | 21 +- drivers/block/virtio_blk.c | 2 + drivers/clk/meson/gxbb.c | 2 + drivers/cpufreq/armada-37xx-cpufreq.c | 22 +- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 1 + drivers/gpu/drm/mediatek/mtk_hdmi.c | 2 +- drivers/gpu/drm/omapdrm/dss/hdmi4_cec.c | 26 +- drivers/gpu/drm/sun4i/sun8i_tcon_top.c | 5 +- drivers/hv/hv.c | 1 - drivers/hwtracing/intel_th/pci.c | 5 + drivers/infiniband/hw/hfi1/chip.c | 26 +- drivers/infiniband/hw/hfi1/rc.c | 4 +- drivers/infiniband/hw/hns/hns_roce_hem.c | 6 +- drivers/infiniband/hw/hns/hns_roce_mr.c | 4 +- drivers/infiniband/hw/vmw_pvrdma/pvrdma_main.c | 2 + drivers/iommu/amd_iommu_init.c | 2 +- drivers/net/ethernet/stmicro/stmmac/norm_desc.c | 2 +- drivers/nvme/host/fc.c | 20 +- drivers/platform/x86/pmc_atom.c | 2 +- drivers/scsi/csiostor/csio_scsi.c | 5 +- drivers/scsi/libsas/sas_expander.c | 9 +- drivers/scsi/lpfc/lpfc_attr.c | 180 ++++---- drivers/scsi/lpfc/lpfc_ct.c | 12 +- drivers/scsi/lpfc/lpfc_debugfs.c | 453 +++++++++++---------- drivers/scsi/lpfc/lpfc_debugfs.h | 6 +- drivers/scsi/qla2xxx/qla_attr.c | 4 +- drivers/scsi/qla2xxx/qla_target.c | 4 +- drivers/soc/sunxi/Kconfig | 1 + drivers/staging/greybus/power_supply.c | 2 +- drivers/staging/most/cdev/cdev.c | 2 +- drivers/usb/class/cdc-acm.c | 32 +- drivers/usb/dwc3/core.c | 2 +- drivers/usb/musb/Kconfig | 2 +- drivers/usb/serial/f81232.c | 39 ++ drivers/usb/storage/scsiglue.c | 26 +- drivers/usb/storage/uas.c | 35 +- drivers/virtio/virtio_pci_common.c | 8 +- include/linux/kernel.h | 4 +- include/net/bluetooth/hci_core.h | 3 + kernel/events/core.c | 52 ++- kernel/events/ring_buffer.c | 4 +- kernel/futex.c | 188 +++++---- kernel/irq/manage.c | 4 +- lib/ubsan.c | 49 ++- mm/slab.c | 3 +- net/bluetooth/hci_conn.c | 8 + net/bluetooth/hidp/sock.c | 1 + sound/soc/codecs/cs35l35.c | 11 + sound/soc/codecs/cs4270.c | 1 + sound/soc/codecs/hdmi-codec.c | 118 +++--- sound/soc/codecs/nau8810.c | 4 +- sound/soc/codecs/nau8824.c | 46 ++- sound/soc/codecs/rt5682.c | 14 +- sound/soc/codecs/tlv320aic32x4.c | 2 + sound/soc/codecs/tlv320aic3x.c | 5 +- sound/soc/codecs/wm_adsp.c | 11 +- .../soc/intel/boards/kbl_rt5663_rt5514_max98927.c | 2 +- sound/soc/intel/common/sst-firmware.c | 8 +- sound/soc/intel/skylake/skl-pcm.c | 19 +- sound/soc/rockchip/rockchip_pdm.c | 2 + sound/soc/samsung/odroid.c | 4 +- sound/soc/soc-dapm.c | 4 + sound/soc/soc-pcm.c | 7 +- sound/soc/stm/stm32_adfsdm.c | 38 +- sound/soc/stm/stm32_sai_sub.c | 15 +- tools/objtool/check.c | 1 + 70 files changed, 1019 insertions(+), 656 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 2/66 scsi: libsas: fix a race condition when smp task timeout
From: Jason Yan <[email protected]>
commit b90cd6f2b905905fb42671009dc0e27c310a16ae upstream.
When the lldd is processing the complete sas task in interrupt and set the task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be triggered at the same time. And smp_task_timedout() will complete the task wheter the SAS_TASK_STATE_DONE is set or not. Then the sas task may freed before lldd end the interrupt process. Thus a use-after-free will happen.
Fix this by calling the complete() only when SAS_TASK_STATE_DONE is not set. And remove the check of the return value of the del_timer(). Once the LLDD sets DONE, it must call task->done(), which will call smp_task_done()->complete() and the task will be completed and freed correctly.
--- drivers/scsi/libsas/sas_expander.c | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-)
drivers/scsi/libsas/sas_expander.c +4 -5
@@ -48,17 +48,16 @@ static void smp_task_timedout(struct timunsigned long flags;spin_lock_irqsave (&task->task_state_lock, flags); -if (!(task->task_state_flags &SAS_TASK_STATE_DONE )) +if (!(task->task_state_flags &SAS_TASK_STATE_DONE )) { task->task_state_flags |=SAS_TASK_STATE_ABORTED ; +complete (&task->slow_task->completion); + }spin_unlock_irqrestore (&task->task_state_lock, flags); - -complete (&task->slow_task->completion); }static void smp_task_done (struct sas_task *task) { -if (!del_timer (&task->slow_task->timer)) -return ; +del_timer (&task->slow_task->timer);complete (&task->slow_task->completion); }
Greg Kroah-Hartman
maintainerPATCH 1/66 net: stmmac: Use bfsize1 in ndesc_init_rx_desc
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
commit f87db4dbd52f2f8a170a2b51cb0926221ca7c9e2 upstream.
gcc warn this:
drivers/net/ethernet/stmicro/stmmac/norm_desc.c: In function ndesc_init_rx_desc:drivers/net/ethernet/stmicro/stmmac/norm_desc.c:138:6: warning: variable 'bfsize1' set but not used [-Wunused-but-set-variable]
Like enh_desc_init_rx_desc, we should use bfsize1 in ndesc_init_rx_desc to calculate 'p->des1'
--- drivers/net/ethernet/stmicro/stmmac/norm_desc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/stmicro/stmmac/norm_desc.c +1 -1
@@ -140,7 +140,7 @@ static void ndesc_init_rx_desc(struct dm p->des0 |=cpu_to_le32 (RDES0_OWN ); bfsize1 =min (bfsize, BUF_SIZE_2KiB -1 ); - p->des1 |=cpu_to_le32 (bfsize &RDES1_BUFFER1_SIZE_MASK ); + p->des1 |=cpu_to_le32 (bfsize1 &RDES1_BUFFER1_SIZE_MASK );if (mode ==STMMAC_CHAIN_MODE )ndesc_rx_set_on_chain (p, end);
RE: [EXT] [PATCH 4.19 60/66] scsi: qla2xxx: Fix device staying in blocked state
In reply to Greg Kroah-HartmanHi All,
Please, remove Quoc Tran ([email protected]) from this email. I think the correct contact is Quinn Tran ([email protected])
Thanks
Quoc
-----Original Message-----
From: Greg Kroah-Hartman <[email protected]>
Sent: Thursday, May 9, 2019 11:43 AM
To: [email protected]
Cc: Greg Kroah-Hartman <[email protected]>; [email protected]; Quoc Tran <[email protected]>; Himanshu Madhani <[email protected]>; Ewan D. Milne <[email protected]>; Martin K. Petersen <[email protected]>
Subject: [EXT] [PATCH 4.19 60/66] scsi: qla2xxx: Fix device staying in blocked state
External Email
----------------------------------------------------------------------
From: Quinn Tran <[email protected]>
commit 2137490f2147a8d0799b72b9a1023efb012d40c7 upstream.
This patch fixes issue reported by some of the customers, who discovered that after cable pull scenario the devices disappear and path seems to remain in blocked state. Once the device reappears, driver does not seem to update path to online. This issue appears because of the defer flag creating race condition where the same session reappears. This patch fixes this issue by indicating SCSI-ML of device lost when qlt_free_session_done() is called from qlt_unreg_sess().
--- drivers/scsi/qla2xxx/qla_target.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/scsi/qla2xxx/qla_target.c +2 -2
@@ -981,6 +981,8 @@ void qlt_free_session_done(struct work_s sess->send_els_logo);if (!IS_SW_RESV_ADDR (sess->d_id)) { +qla2x00_mark_device_lost (vha, sess,0 ,0 ); +if (sess->send_els_logo) {qlt_port_logo_t logo;
@@ -1161,8 +1163,6 @@ void qlt_unreg_sess(struct fc_port *sessif (sess->se_sess) vha->hw->tgt.tgt_ops->clear_nacl_from_fcport_map (sess); -qla2x00_mark_device_lost (vha, sess,0 ,0 ); - sess->deleted =QLA_SESS_DELETION_IN_PROGRESS ; sess->disc_state =DSC_DELETE_PEND ; sess->last_rscn_gen = sess->rscn_gen;
stable-rc/linux-4.19.y boot: 135 boots: 1 failed, 132 passed with 2 conflicts (v4.19.41-67-g82fd2fd59cff)
stable-rc/linux-4.19.y boot: 135 boots: 1 failed, 132 passed with 2 conflicts (v4.19.41-67-g82fd2fd59cff)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.41-67-g82fd2fd59cff/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.41-67-g82fd2fd59cff/
Tree: stable-rc
Branch: linux-4.19.y
Git Describe: v4.19.41-67-g82fd2fd59cff
Git Commit: 82fd2fd59cffa3045f205da555c0defe8bb35912
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 71 unique boards, 25 SoC families, 15 builds out of 206
Boot Regressions Detected:
arm:
omap2plus_defconfig:
gcc-8:
omap4-panda:
lab-baylibre: failing since 1 day (last pass: v4.19.40-100-gf897c76a347c - first fail: v4.19.41)x86_64:
x86_64_defconfig:
gcc-8:
qemu:
lab-collabora: new failure (last pass: v4.19.41-56-g487b15502665)Boot Failure Detected:
arm:
multi_v7_defconfig:
gcc-8:
stih410-b2120: 1 failed labConflicting Boot Failures Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
x86_64:
x86_64_defconfig:
qemu:
lab-baylibre: PASS (gcc-8)
lab-mhart: PASS (gcc-8)
lab-drue: PASS (gcc-8)
lab-collabora: FAIL (gcc-8)arm:
omap2plus_defconfig:
omap4-panda:
lab-baylibre: FAIL (gcc-8)
lab-baylibre-seattle: PASS (gcc-8)
---
For more info write to <[email protected]>
Greg Kroah-Hartman
maintainerRe: [EXT] [PATCH 4.19 60/66] scsi: qla2xxx: Fix device staying in blocked state
In reply to Quoc TranQuoted 3 lines · Quoc Tran
Hi All,
Please, remove Quoc Tran ([email protected]) from this email. I think the correct contact is Quinn Tran ([email protected])
I can't go back and rewrite git history, sorry.
greg k-h
Greg Kroah-Hartman
maintainerRe: [PATCH 4.19 32/66] xtensa: fix initialization of pt_regs::syscall in start_thread
In reply to Max FilippovQuoted 11 lines · Max Filippov
Hello,
Quoted 7 lines · Greg Kroah-Hartman
[ Upstream commit
2663147dc7465cb29040a05cc4286fdd839978b5]New
pt_regsshould indicate that there's no syscall, not that there's syscall #0. While at it wrap macro body in do/while and parenthesize macro arguments.
Quoted 8 lines
Quoted 5 lines
Signed-off-by Max Filippov <[email protected]>Signed-off-by Sasha Levin <[email protected]>--- arch/xtensa/include/asm/processor.h | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)This patch should not be taken to any of the stable trees, except maybe 5.0.y, because
NO_SYSCALLwas introduced toarch/xtensain 5.0.
Now dropped from everywhere except 5.0.y, thanks.
Quoted 2 lines
This patch doesn't have any cc:stable tags, I'm curious why was it chosen for stable and what can I do to prevent that in the future?
Sasha's tools picked this up and you should have been cc:ed on it when it was selected a few weeks ago.
thanks,
greg k-h
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.42 release. There are 66 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 11 May 2019 06:11:18 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.42-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.19.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Summary
------------------------------------------------------------------------
kernel: 4.19.42-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.19.y
git commit: 82fd2fd59cffa3045f205da555c0defe8bb35912
git describe: v4.19.41-67-g82fd2fd59cff
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.41-67-g82fd2fd59cff
No regressions (compared to build v4.19.41)
No fixes (compared to build v4.19.41)
Ran 24988 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c - arm64
- hi6220-hikey - arm64
- i386
- juno-r2 - arm64
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15 - arm
- x86_64
Test Suites
-----------
* build
* install-android-platform-tools-r2600
* kselftest
* libgpiod
* libhugetlbfs
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-cpuhotplug-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-timers-tests
* perf
* spectre-meltdown-checker-test
* v4l2-compliance
* ltp-open-posix-tests
* prep-tmp-disk
* kvm-unit-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Jon Hunter
maintainerQuoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.42 release. There are 66 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 11 May 2019 06:11:18 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.42-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.19.y
and the diffstat can be found below.thanks,
greg k-h
All tests are passing for Tegra ...
Test results for stable-v4.19:
12 builds: 12 pass, 0 fail
22 boots: 22 pass, 0 fail
32 tests: 32 pass, 0 failLinux version: 4.19.42-rc1-g82fd2fd
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana, tegra210,
tegra210-p2371-2180, tegra30-cardhu-a04Cheers
Jon
Signature · 1 line
nvpublic
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.42 release. There are 66 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Sat 11 May 2019 06:11:18 PM UTC. Anything received after that time might be too late.
Build results:
total: 156 pass: 156 fail: 0 Qemu test results: total: 349 pass: 349 fail: 0
Guenter
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.42 release. There are 66 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.
Quoted 9 lines
Responses should be made by Sat 11 May 2019 06:11:18 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.42-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.19.y
and the diffstat can be found below.
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Hi!
Quoted 5 lines
This is the start of the stable review cycle for the 4.19.42 release. There are 66 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.
Quoted 8 lines
Responses should be made by Sat 11 May 2019 06:11:18 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.42-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.19.y
and the diffstat can be found below.
I reviewed these patches and found them ok:
/- commit in linux-stable-rc.git linux-4.19.
| /- mainline commit it references.
a | c9849e7b0d19 03110a5cb216 | arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP a | 7f70094a664c 0efa3334d65b | ASoC: Intel: avoid Oops if DMA setup fails a diff has whitespace problems | b47e4bc2c6bf 3ae62a42090f | UAS: fix alignment of scatter/gather segments a | d93b3794e11d a1616a5ac99e | Bluetooth: hidp: fix buffer overflow a | 390fb51f14ed 2137490f2147 | scsi: qla2xxx: Fix device staying in blocked state a | 648efce413c9 5cbdae10bf11 | scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines a | de4ed47623d2 a84014e1db35 | soc: sunxi: Fix missing dependency on REGMAP_MMIO a | cfccebbba945 8db82563451f | cpufreq: armada-37xx: fix frequency calculation for opp a | a747d98ffde8 e60e9a4b231a | intel_th: pci: Add Comet Lake support a | 79c5c7d9ce07 747668dbc061 | usb-storage: Set virt_boundary_mask to avoid SG overflows a | 841f47e3548c 764478f41130 | USB: cdc-acm: fix unthrottle races a | 14fa060959b0 8d791929b2fb | usb: dwc3: Fix default lpm_nyet_threshold value a | 3b34dc57f585 59c39840f5ab | genirq: Prevent use-after-free and work list corruption a | 2b02d3a95527 b995dcca7cf1 | platform/x86: pmc_atom: Drop __initconst on dmi table a | 997718a02d82 d6ba3f815bc5 | ASoC: Intel: kbl: fix wrong number of channels a | 1483cfcf3c9f 4772e03d2394 | RDMA/hns: Fix bug that caused srq creation to fail a | 506a0e6862e1 6a8aae68c873 | virtio_pci: fix a NULL pointer reference in vp_del_vqs a | 02fd02c489cc 1a07a94b47b1 | drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind a | 71ad65f5bb67 fcf88917dd43 | slab: fix a crash by reading /proc/slab_allocators a | b5d7ac566868 c85064435fe7 | ASoC: rockchip: pdm: fix regmap_ops hang issue a | eaa1d16862ee d7262457e35d | perf/x86/intel: Initialize TFA MSR a | 378151a25204 583feb08e7f7 | perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS a | 0c56a7078088 2d85978341e6 | drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() a | adbf3d1f3ed8 c63adb28f6d9 | ASoC: tlv320aic32x4: Fix Common Pins a | b9cdb2937e9a ab8a6d821179 | MIPS: KGDB: fix kgdb support for SMP platforms. a | de583e633e02 a8639a79e85c | IB/hfi1: Eliminate opcode tests on mr deref
a typo: inaudile | b13ae59295e9 c899df3e9b0b | ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform
a | 3161876cbf97 570f18b6a8d1 | ASoC:soc-pcm:fix a codec fixup issue in TDM case
a wrong reference counting, not terribly serious; noone unloads these anyway | d978c80542e6 af708900e9a4 | ee3b6ffe3302 82ad759143ed | ASoC: tlv320aic3x: fix reset gpio reference counting a "))" in changelog | e275c9a0765b 47830c1127ef | staging: greybus: power_supply: fix prop-descriptor request size
a | c211648a4906 a0033bd1eae4 | Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() a | 97aec5cea4fa b90cd6f2b905 | scsi: libsas: fix a race condition when smp task timeout a | bf78d2cb30eb f87db4dbd52f | net: stmmac: Use bfsize1 in ndesc_init_rx_desc
A lot of the autosel patches do not seem to match stable criteria to me. It would be good to synchronize documentation with actual practice here.
Best regards,
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html