5.0.11-stable review
Subsystems (8)
Greg Kroah-Hartman
maintainerPATCH 1/89 netfilter: nf_tables: bogus EBUSY when deleting set after flush
In reply to Greg Kroah-Hartman[ Upstream commit 273fe3f1006ea5ebc63d6729e43e8e45e32b256a ]
Set deletion after flush coming in the same batch results in EBUSY. Add set use counter to track the number of references to this set from rules. We cannot rely on the list of bindings for this since such list is still populated from the preparation phase.
--- include/net/netfilter/nf_tables.h | 6 ++++++ net/netfilter/nf_tables_api.c | 28 +++++++++++++++++++++++++++- net/netfilter/nft_dynset.c | 13 +++++++++---- net/netfilter/nft_lookup.c | 13 +++++++++---- net/netfilter/nft_objref.c | 13 +++++++++---- 5 files changed, 60 insertions(+), 13 deletions(-)
include/net/netfilter/nf_tables.h +6 -0
@@ -382,6 +382,7 @@ void nft_unregister_set(struct nft_set_type *type);* @dtype: data type (verdict or numeric type defined by userspace) * @objtype: object type (see NFT_OBJECT_* definitions) * @size: maximum set size +* @use: number of rules references to this set * @nelems: number of elements * @ndeact: number of deactivated elements queued for removal * @timeout: default timeout value in jiffies
@@ -407,6 +408,7 @@ struct nft_set {u32 dtype;u32 objtype;u32 size; +u32 use;atomic_t nelems;u32 ndeact;u64 timeout;
@@ -467,6 +469,10 @@ struct nft_set_binding {u32 flags; }; +enum nft_trans_phase ; +void nf_tables_deactivate_set (const struct nft_ctx *ctx,struct nft_set *set, +struct nft_set_binding *binding, +enum nft_trans_phase phase);int nf_tables_bind_set (const struct nft_ctx *ctx,struct nft_set *set,struct nft_set_binding *binding); void nf_tables_unbind_set(const struct nft_ctx *ctx, struct nft_set *set,
net/netfilter/nf_tables_api.c +27 -1
@@ -3624,6 +3624,9 @@ err1:static void nft_set_destroy (struct nft_set *set) { +if (WARN_ON (set->use >0 )) +return ; + set->ops->destroy (set);module_put (to_set_type (set->ops)->owner);kfree (set->name);
@@ -3664,7 +3667,7 @@ static int nf_tables_delset(struct net *net, struct sock *nlsk,NL_SET_BAD_ATTR (extack, attr);return PTR_ERR (set); } -if (!list_empty (&set->bindings) || +if (set->use || (nlh->nlmsg_flags &NLM_F_NONREC &&atomic_read (&set->nelems) >0 )) {NL_SET_BAD_ATTR (extack, attr);return -EBUSY ;
@@ -3694,6 +3697,9 @@ int nf_tables_bind_set(const struct nft_ctx *ctx, struct nft_set *set,struct nft_set_binding *i;struct nft_set_iter iter; +if (set->use ==UINT_MAX ) +return -EOVERFLOW ; +if (!list_empty (&set->bindings) &&nft_set_is_anonymous (set))return -EBUSY ;
@@ -3721,6 +3727,7 @@ bind: binding->chain = ctx->chain;list_add_tail_rcu (&binding->list, &set->bindings);nft_set_trans_bind (ctx, set); + set->use++;return 0 ; }
@@ -3740,6 +3747,25 @@ void nf_tables_unbind_set(const struct nft_ctx *ctx, struct nft_set *set, }EXPORT_SYMBOL_GPL (nf_tables_unbind_set); +void nf_tables_deactivate_set (const struct nft_ctx *ctx,struct nft_set *set, +struct nft_set_binding *binding, +enum nft_trans_phase phase) +{ +switch (phase) { +case NFT_TRANS_PREPARE : + set->use--; +return ; +case NFT_TRANS_ABORT : +case NFT_TRANS_RELEASE : + set->use--; +/* fall through */ +default : +nf_tables_unbind_set (ctx, set, binding, + phase ==NFT_TRANS_COMMIT ); + } +} +EXPORT_SYMBOL_GPL (nf_tables_deactivate_set); +void nf_tables_destroy_set (const struct nft_ctx *ctx,struct nft_set *set) {if (list_empty (&set->bindings) &&nft_set_is_anonymous (set))
net/netfilter/nft_dynset.c +9 -4
@@ -241,11 +241,15 @@ static void nft_dynset_deactivate(const struct nft_ctx *ctx, {struct nft_dynset *priv =nft_expr_priv (expr); -if (phase ==NFT_TRANS_PREPARE ) -return ; +nf_tables_deactivate_set (ctx, priv->set, &priv->binding, phase); +} + +static void nft_dynset_activate (const struct nft_ctx *ctx, +const struct nft_expr *expr) +{ +struct nft_dynset *priv =nft_expr_priv (expr); -nf_tables_unbind_set (ctx, priv->set, &priv->binding, - phase ==NFT_TRANS_COMMIT ); + priv->set->use++; } static void nft_dynset_destroy(const struct nft_ctx *ctx,
@@ -293,6 +297,7 @@ static const struct nft_expr_ops nft_dynset_ops = { .eval = nft_dynset_eval, .init = nft_dynset_init, .destroy = nft_dynset_destroy, + .activate = nft_dynset_activate, .deactivate = nft_dynset_deactivate, .dump = nft_dynset_dump, };
net/netfilter/nft_lookup.c +9 -4
@@ -127,11 +127,15 @@ static void nft_lookup_deactivate(const struct nft_ctx *ctx, {struct nft_lookup *priv =nft_expr_priv (expr); -if (phase ==NFT_TRANS_PREPARE ) -return ; +nf_tables_deactivate_set (ctx, priv->set, &priv->binding, phase); +} + +static void nft_lookup_activate (const struct nft_ctx *ctx, +const struct nft_expr *expr) +{ +struct nft_lookup *priv =nft_expr_priv (expr); -nf_tables_unbind_set (ctx, priv->set, &priv->binding, - phase ==NFT_TRANS_COMMIT ); + priv->set->use++; } static void nft_lookup_destroy(const struct nft_ctx *ctx,
@@ -222,6 +226,7 @@ static const struct nft_expr_ops nft_lookup_ops = { .size = NFT_EXPR_SIZE(sizeof(struct nft_lookup)), .eval = nft_lookup_eval, .init = nft_lookup_init, + .activate = nft_lookup_activate, .deactivate = nft_lookup_deactivate, .destroy = nft_lookup_destroy, .dump = nft_lookup_dump,
net/netfilter/nft_objref.c +9 -4
@@ -161,11 +161,15 @@ static void nft_objref_map_deactivate(const struct nft_ctx *ctx, {struct nft_objref_map *priv =nft_expr_priv (expr); -if (phase ==NFT_TRANS_PREPARE ) -return ; +nf_tables_deactivate_set (ctx, priv->set, &priv->binding, phase); +} + +static void nft_objref_map_activate (const struct nft_ctx *ctx, +const struct nft_expr *expr) +{ +struct nft_objref_map *priv =nft_expr_priv (expr); -nf_tables_unbind_set (ctx, priv->set, &priv->binding, - phase ==NFT_TRANS_COMMIT ); + priv->set->use++; } static void nft_objref_map_destroy(const struct nft_ctx *ctx,
@@ -182,6 +186,7 @@ static const struct nft_expr_ops nft_objref_map_ops = { .size = NFT_EXPR_SIZE(sizeof(struct nft_objref_map)), .eval = nft_objref_map_eval, .init = nft_objref_map_init, + .activate = nft_objref_map_activate, .deactivate = nft_objref_map_deactivate, .destroy = nft_objref_map_destroy, .dump = nft_objref_map_dump,
Signature · 1 line
2.19.1
Greg Kroah-Hartman
maintainerPATCH 5/89 ALSA: hda/realtek - Move to ACT_INIT state
In reply to Greg Kroah-Hartman[ Upstream commit 8983eb602af511fc5822f5ff4a82074c68816fd9 ]
It will be lose Mic JD state when Chrome OS boot and headset was plugged. Just Implement of reset combo jack JD verb for ACT_PRE_PROBE state. Intel test result was also failed.
It test passed until changed the initial state to ACT_INIT. Mic JD will show every time.
This patch also changed the model name as 'alc-chrome-book' for application of Chrome OS.
--- sound/pci/hda/patch_realtek.c | 41 +++++++++++++++++++++++++---------- 1 file changed, 29 insertions(+), 12 deletions(-)
sound/pci/hda/patch_realtek.c +29 -12
@@ -5490,7 +5490,7 @@ static void alc_headset_btn_callback(struct hda_codec *codec, jack->jack->button_state = report; } -static void alc295_fixup_chromebook (struct hda_codec *codec, +static void alc_fixup_headset_jack (struct hda_codec *codec,const struct hda_fixup *fix,int action) {
@@ -5500,16 +5500,6 @@ static void alc295_fixup_chromebook(struct hda_codec *codec, alc_headset_btn_callback);snd_hda_jack_add_kctl (codec,0x55 ,"Headset Jack" , false,SND_JACK_HEADSET , alc_headset_btn_keymap); -switch (codec->core.vendor_id) { -case 0x10ec0295 : -alc_update_coef_idx (codec,0x4a ,0x8000 ,1 <<15 );/* Reset HP JD */ -alc_update_coef_idx (codec,0x4a ,0x8000 ,0 <<15 ); -break ; -case 0x10ec0236 : -alc_update_coef_idx (codec,0x1b ,0x8000 ,1 <<15 );/* Reset HP JD */ -alc_update_coef_idx (codec,0x1b ,0x8000 ,0 <<15 ); -break ; - }break ;case HDA_FIXUP_ACT_INIT :switch (codec->core.vendor_id) {
@@ -5530,6 +5520,25 @@ static void alc295_fixup_chromebook(struct hda_codec *codec, } } +static void alc295_fixup_chromebook (struct hda_codec *codec, +const struct hda_fixup *fix,int action) +{ +switch (action) { +case HDA_FIXUP_ACT_INIT : +switch (codec->core.vendor_id) { +case 0x10ec0295 : +alc_update_coef_idx (codec,0x4a ,0x8000 ,1 <<15 );/* Reset HP JD */ +alc_update_coef_idx (codec,0x4a ,0x8000 ,0 <<15 ); +break ; +case 0x10ec0236 : +alc_update_coef_idx (codec,0x1b ,0x8000 ,1 <<15 );/* Reset HP JD */ +alc_update_coef_idx (codec,0x1b ,0x8000 ,0 <<15 ); +break ; + } +break ; + } +} +static void alc_fixup_disable_mic_vref (struct hda_codec *codec,const struct hda_fixup *fix,int action) {
@@ -5684,6 +5693,7 @@ enum {ALC285_FIXUP_LENOVO_PC_BEEP_IN_NOISE ,ALC255_FIXUP_ACER_HEADSET_MIC ,ALC295_FIXUP_CHROME_BOOK , +ALC225_FIXUP_HEADSET_JACK ,ALC225_FIXUP_DELL_WYSE_AIO_MIC_NO_PRESENCE ,ALC225_FIXUP_WYSE_AUTO_MUTE , ALC225_FIXUP_WYSE_DISABLE_MIC_VREF,
@@ -6645,6 +6655,12 @@ static const struct hda_fixup alc269_fixups[] = { [ALC295_FIXUP_CHROME_BOOK] = { .type = HDA_FIXUP_FUNC, .v.func = alc295_fixup_chromebook, + .chained = true, + .chain_id =ALC225_FIXUP_HEADSET_JACK + }, + [ALC225_FIXUP_HEADSET_JACK] = { + .type = HDA_FIXUP_FUNC, + .v.func = alc_fixup_headset_jack, }, [ALC293_FIXUP_SYSTEM76_MIC_NO_PRESENCE] = { .type = HDA_FIXUP_PINS,
@@ -7143,7 +7159,8 @@ static const struct hda_model_fixup alc269_fixup_models[] = { {.id = ALC255_FIXUP_DUMMY_LINEOUT_VERB, .name = "alc255-dummy-lineout"}, {.id = ALC255_FIXUP_DELL_HEADSET_MIC, .name = "alc255-dell-headset"}, {.id = ALC295_FIXUP_HP_X360, .name = "alc295-hp-x360"}, - {.id = ALC295_FIXUP_CHROME_BOOK, .name = "alc-sense-combo"}, + {.id = ALC225_FIXUP_HEADSET_JACK, .name = "alc-headset-jack"}, + {.id = ALC295_FIXUP_CHROME_BOOK, .name = "alc-chrome-book"}, {.id = ALC299_FIXUP_PREDATOR_SPK, .name = "predator-spk"}, {} };
Signature · 1 line
2.19.1
Greg Kroah-Hartman
maintainerPATCH 6/89 fs/proc/proc_sysctl.c: Fix a NULL pointer dereference
In reply to Greg Kroah-Hartman[ Upstream commit 89189557b47b35683a27c80ee78aef18248eefb4 ]
Syzkaller report this:
sysctl could not get directory: /net//bridge -12
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN PTI
CPU: 1 PID: 7027 Comm: syz-executor.0 Tainted: G C 5.1.0-rc3+ #8
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014
RIP: 0010:__write_once_size include/linux/compiler.h:220 [inline]
RIP: 0010:__rb_change_child include/linux/rbtree_augmented.h:144 [inline]
RIP: 0010:__rb_erase_augmented include/linux/rbtree_augmented.h:186 [inline]
RIP: 0010:rb_erase+0x5f4/0x19f0 lib/rbtree.c:459
Code: 00 0f 85 60 13 00 00 48 89 1a 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 89 f2 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 75 0c 00 00 4d 85 ed 4c 89 2e 74 ce 4c 89 ea 48
RSP: 0018:ffff8881bb507778 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: ffff8881f224b5b8 RCX: ffffffff818f3f6a
RDX: 000000000000000a RSI: 0000000000000050 RDI: ffff8881f224b568
RBP: 0000000000000000 R08: ffffed10376a0ef4 R09: ffffed10376a0ef4
R10: 0000000000000001 R11: ffffed10376a0ef4 R12: ffff8881f224b558
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 00007f3e7ce13700(0000) GS:ffff8881f7300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd60fbe9398 CR3: 00000001cb55c001 CR4: 00000000007606e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
PKRU: 55555554
Call Trace:
erase_entry fs/proc/proc_sysctl.c:178 [inline]
erase_header+0xe3/0x160 fs/proc/proc_sysctl.c:207
start_unregistering fs/proc/proc_sysctl.c:331 [inline]
drop_sysctl_table+0x558/0x880 fs/proc/proc_sysctl.c:1631
get_subdir fs/proc/proc_sysctl.c:1022 [inline]
__register_sysctl_table+0xd65/0x1090 fs/proc/proc_sysctl.c:1335
br_netfilter_init+0x68/0x1000 [br_netfilter]
do_one_initcall+0xbc/0x47d init/main.c:901
do_init_module+0x1b5/0x547 kernel/module.c:3456
load_module+0x6405/0x8c10 kernel/module.c:3804
__do_sys_finit_module+0x162/0x190 kernel/module.c:3898
do_syscall_64+0x9f/0x450 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
Modules linked in: br_netfilter(+) backlight comedi(C) hid_sensor_hub max3100 ti_ads8688 udc_core fddi snd_mona leds_gpio rc_streamzap mtd pata_netcell nf_log_common rc_winfast udp_tunnel snd_usbmidi_lib snd_usb_toneport snd_usb_line6 snd_rawmidi snd_seq_device snd_hwdep videobuf2_v4l2 videobuf2_common videodev media videobuf2_vmalloc videobuf2_memops rc_gadmei_rm008z 8250_of smm665 hid_tmff hid_saitek hwmon_vid rc_ati_tv_wonder_hd_600 rc_core pata_pdc202xx_old dn_rtmsg as3722 ad714x_i2c ad714x snd_soc_cs4265 hid_kensington panel_ilitek_ili9322 drm drm_panel_orientation_quirks ipack cdc_phonet usbcore phonet hid_jabra hid extcon_arizona can_dev industrialio_triggered_buffer kfifo_buf industrialio adm1031 i2c_mux_ltc4306 i2c_mux ipmi_msghandler mlxsw_core snd_soc_cs35l34 snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer ac97_bus snd_compress snd soundcore gpio_da9055 uio ecdh_generic mdio_thunder of_mdio fixed_phy libphy mdio_cavium iptable_security iptable_raw iptable_mangle
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip6_vti ip_vti ip_gre ipip sit tunnel4 ip_tunnel hsr veth netdevsim vxcan batman_adv cfg80211 rfkill chnl_net caif nlmon dummy team bonding vcan bridge stp llc ip6_gre gre ip6_tunnel tunnel6 tun joydev mousedev ppdev tpm kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel ide_pci_generic piix aes_x86_64 crypto_simd cryptd ide_core glue_helper input_leds psmouse intel_agp intel_gtt serio_raw ata_generic i2c_piix4 agpgart pata_acpi parport_pc parport floppy rtc_cmos sch_fq_codel ip_tables x_tables sha1_ssse3 sha1_generic ipv6 [last unloaded: br_netfilter]
Dumping ftrace buffer:
(ftrace buffer empty)
---[ end trace 68741688d5fbfe85 ]---commit 23da9588037e ("fs/proc/proc_sysctl.c: fix NULL pointer dereference in put_links") forgot to handle start_unregistering() case, while header->parent is NULL, it calls erase_header() and as seen in the above syzkaller call trace, accessing &header->parent->root will trigger a NULL pointer dereference.
As that commit explained, there is also no need to call start_unregistering() if header->parent is NULL.
--- fs/proc/proc_sysctl.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
fs/proc/proc_sysctl.c +4 -2
@@ -1626,9 +1626,11 @@ static void drop_sysctl_table(struct ctl_table_header *header)if (--header->nreg)return ; -if (parent) +if (parent) {put_links (header); -start_unregistering (header); +start_unregistering (header); + } +if (!--header->count)kfree_rcu (header, rcu);
Signature · 1 line
2.19.1
Greg Kroah-Hartman
maintainerPATCH 8/89 cifs: fix memory leak in SMB2_read
In reply to Greg Kroah-Hartman[ Upstream commit 05fd5c2c61732152a6bddc318aae62d7e436629b ]
Commit 088aaf17aa79300cab14dbee2569c58cfafd7d6e introduced a leak where if SMB2_read() returned an error we would return without freeing the request buffer.
--- fs/cifs/smb2pdu.c | 1 + 1 file changed, 1 insertion(+)
fs/cifs/smb2pdu.c +1 -0
@@ -3402,6 +3402,7 @@ SMB2_read(const unsigned int xid, struct cifs_io_parms *io_parms, rc); }free_rsp_buf (resp_buftype, rsp_iov.iov_base); +cifs_small_buf_release (req);return rc == -ENODATA ?0 : rc; }else trace_smb3_read_done(xid, req->PersistentFileId,
Signature · 1 line
2.19.1
Greg Kroah-Hartman
maintainerPATCH 9/89 cifs: fix page reference leak with readv/writev
In reply to Greg Kroah-HartmanFrom: Jérôme Glisse <[email protected]>
commit 13f5938d8264b5501368523c4513ff26608a33e8 upstream.
CIFS can leak pages reference gotten through GUP (get_user_pages*() through iov_iter_get_pages()). This happen if cifs_send_async_read() or cifs_write_from_iter() calls fail from within __cifs_readv() and __cifs_writev() respectively. This patch move page unreference to cifs_aio_ctx_release() which will happens on all code paths this is all simpler to follow for correctness.
--- fs/cifs/file.c | 15 +-------------- fs/cifs/misc.c | 23 ++++++++++++++++++++++- 2 files changed, 23 insertions(+), 15 deletions(-)
fs/cifs/file.c +1 -14
@@ -2796,7 +2796,6 @@ static void collect_uncached_write_data(struct cifs_tcon *tcon;struct cifs_sb_info *cifs_sb;struct dentry *dentry = ctx->cfile->dentry; -unsigned int i;int rc; tcon =tlink_tcon (ctx->cfile->tlink);
@@ -2860,10 +2859,6 @@ restart_loop:kref_put (&wdata->refcount, cifs_uncached_writedata_release); } -if (!ctx->direct_io) -for (i =0 ; i < ctx->npages; i++) -put_page (ctx->bv[i].bv_page); -cifs_stats_bytes_written (tcon, ctx->total_len);set_bit (CIFS_INO_INVALID_MAPPING , &CIFS_I (dentry->d_inode)->flags);
@@ -3472,7 +3467,6 @@ collect_uncached_read_data(struct cifs_astruct iov_iter *to = &ctx->iter;struct cifs_sb_info *cifs_sb;struct cifs_tcon *tcon; -unsigned int i;int rc; tcon =tlink_tcon (ctx->cfile->tlink);
@@ -3556,15 +3550,8 @@ again:kref_put (&rdata->refcount, cifs_uncached_readdata_release); } -if (!ctx->direct_io) { -for (i =0 ; i < ctx->npages; i++) { -if (ctx->should_dirty) -set_page_dirty (ctx->bv[i].bv_page); -put_page (ctx->bv[i].bv_page); - } - +if (!ctx->direct_io) ctx->total_len = ctx->len -iov_iter_count (to); - }cifs_stats_bytes_read (tcon, ctx->total_len);
fs/cifs/misc.c +22 -1
@@ -789,6 +789,11 @@ cifs_aio_ctx_alloc(void) {struct cifs_aio_ctx *ctx; +/* +* Must use kzalloc to initialize ctx->bv to NULL and ctx->direct_io +* to false so that we know when we have to unreference pages within +* cifs_aio_ctx_release() +*/ ctx =kzalloc (sizeof (struct cifs_aio_ctx ),GFP_KERNEL );if (!ctx)return NULL ;
@@ -807,7 +812,23 @@ cifs_aio_ctx_release(struct kref *refcou struct cifs_aio_ctx, refcount);cifsFileInfo_put (ctx->cfile); -kvfree (ctx->bv); + +/* +* ctx->bv is only set if setup_aio_ctx_iter() was call successfuly +* which means that iov_iter_get_pages() was a success and thus that +* we have taken reference on pages. +*/ +if (ctx->bv) { +unsigned i; + +for (i =0 ; i < ctx->npages; i++) { +if (ctx->should_dirty) +set_page_dirty (ctx->bv[i].bv_page); +put_page (ctx->bv[i].bv_page); + } +kvfree (ctx->bv); + } +kfree (ctx); }
Greg Kroah-Hartman
maintainercover 5.0.11-stable review
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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 Thu 02 May 2019 11:35:03 AM 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/v5.x/stable-review/patch-5.0.11-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-5.0.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 5.0.11-rc1
Jakub Kicinski <[email protected]>
net/tls: don't leak IV and record seq when offload fails
Jakub Kicinski <[email protected]>
net/tls: avoid potential deadlock in tls_set_device_offload_rx()
Maxim Mikityanskiy <[email protected]>
net/mlx5e: Fix use-after-free after xdp_return_frame
Maxim Mikityanskiy <[email protected]>
net/mlx5e: Fix the max MTU check in case of XDP
Petr Machata <[email protected]>
mlxsw: spectrum: Put MC TCs into DWRR mode
Ido Schimmel <[email protected]>
mlxsw: pci: Reincrease PCI reset timeout
Tao Ren <[email protected]>
net/ncsi: handle overflow when incrementing mac address
Ilias Apalodimas <[email protected]>
net: socionext: replace napi_alloc_frag with the netdev variant on init
Hangbin Liu <[email protected]>
team: fix possible recursive locking when add slaves
Su Bao Cheng <[email protected]>
stmmac: pci: Adjust IOT2000 matching
Jakub Kicinski <[email protected]>
net/tls: fix refcount adjustment in fallback
Vinod Koul <[email protected]>
net: stmmac: move stmmac_check_ether_addr() to driver probe
Eric Dumazet <[email protected]>
net/rose: fix unbound loop in rose_loopback_timer()
Zhu Yanjun <[email protected]>
net: rds: exchange of 8K and 1M pool
Erez Alfasi <[email protected]>
net/mlx5e: ethtool, Remove unsupported SFP EEPROM high pages query
Amit Cohen <[email protected]>
mlxsw: spectrum: Fix autoneg status in ethtool
ZhangXiaoxu <[email protected]>
ipv4: set the tcp_min_rtt_wlen range from 0 to one day
Eric Dumazet <[email protected]>
ipv4: add sanity checks in ipv4_link_failure()
Linus Torvalds <[email protected]>
rdma: fix build errors on s390 and MIPS due to bad ZERO_PAGE use
Daniel Borkmann <[email protected]>
x86/retpolines: Disable switch jump tables when retpolines are enabled
Daniel Borkmann <[email protected]>
x86, retpolines: Raise limit for generating indirect calls from switch-case
Al Viro <[email protected]>
Fix aio_poll() races
Al Viro <[email protected]>
aio: store event at final iocb_put()
Al Viro <[email protected]>
aio: keep io_event in aio_kiocb
Al Viro <[email protected]>
aio: fold lookup_kiocb() into its sole caller
Linus Torvalds <[email protected]>
pin iocb through aio.
Eric Dumazet <[email protected]>
rxrpc: fix race condition in rxrpc_input_packet()
Tetsuo Handa <[email protected]>
net/rds: Check address length before reading address family
YueHaibing <[email protected]>
net: netrom: Fix error cleanup path of nr_proto_init
Xin Long <[email protected]>
tipc: check link name with right length in tipc_nl_compat_link_set
Xin Long <[email protected]>
tipc: check bearer name with right length in tipc_nl_compat_bearer_enable
Yue Haibing <[email protected]>
fm10k: Fix a potential NULL pointer dereference
Florian Westphal <[email protected]>
netfilter: ebtables: CONFIG_COMPAT: drop a bogus WARN_ON
Tetsuo Handa <[email protected]>
NFS: Forbid setting AF_INET6 to "struct sockaddr_in"->sin_family.
Johannes Berg <[email protected]>
mac80211_hwsim: calculate if_combination.max_interfaces
luca abeni <[email protected]>
sched/deadline: Correctly handle active 0-lag timers
Todd Kjos <[email protected]>
binder: fix handling of misaligned binder object
Tetsuo Handa <[email protected]>
workqueue: Try to catch flush_work() without INIT_WORK().
Linus Torvalds <[email protected]>
slip: make slhc_free() silently accept an error pointer
Xin Long <[email protected]>
tipc: handle the err returned from cmd header function
Dongli Zhang <[email protected]>
loop: do not print warn message if partition scan is successful
Dan Carpenter <[email protected]>
ext4: fix some error pointer dereferences
Kai-Heng Feng <[email protected]>
USB: Consolidate LPM checks to avoid enabling LPM twice
Kai-Heng Feng <[email protected]>
USB: Add new USB LPM helpers
Maarten Lankhorst <[email protected]>
drm/vc4: Fix compilation error reported by kbuild test bot
Dave Airlie <[email protected]>
Revert "drm/i915/fbdev: Actually configure untiled displays"
Christian König <[email protected]>
drm/ttm: fix re-init of global structures
Maarten Lankhorst <[email protected]>
drm/vc4: Fix memory leak during gpu reset.
Michael Ellerman <[email protected]>
powerpc/mm/radix: Make Radix require HUGETLB_PAGE
Ard Biesheuvel <[email protected]>
ARM: 8857/1: efi: enable CP15 DMB instructions before cleaning the cache
Shun-Chih Yu <[email protected]>
dmaengine: mediatek-cqdma: fix wrong register usage in mtk_cqdma_start
Achim Dahlhoff <[email protected]>
dmaengine: sh: rcar-dmac: Fix glitch in dmaengine_tx_status
Dirk Behme <[email protected]>
dmaengine: sh: rcar-dmac: With cyclic DMA residue 0 is valid
Alex Williamson <[email protected]>
vfio/type1: Limit DMA mappings per container
Lucas Stach <[email protected]>
Input: synaptics-rmi4 - write config register values to the right offset
Harry Pan <[email protected]>
perf/x86/intel: Update KBL Package C-state events to also include PC8/PC9/PC10 counters
NeilBrown <[email protected]>
sunrpc: don't mark uninitialised items as VALID.
Jeff Layton <[email protected]>
nfsd: wake blocked file lock waiters before sending callback
Jeff Layton <[email protected]>
nfsd: wake waiters blocked on file_lock before deleting it
Trond Myklebust <[email protected]>
nfsd: Don't release the callback slot unless it was actually held
Yan, Zheng <[email protected]>
ceph: fix ci->i_head_snapc leak
Jeff Layton <[email protected]>
ceph: ensure d_name stability in ceph_dentry_hash()
Jeff Layton <[email protected]>
ceph: only use d_name directly when parent is locked
Xie XiuQi <[email protected]>
sched/numa: Fix a possible divide-by-zero
Jason Gunthorpe <[email protected]>
RDMA/ucontext: Fix regression with disassociate
Jason Gunthorpe <[email protected]>
RDMA/mlx5: Use rdma_user_map_io for mapping BAR pages
Jason Gunthorpe <[email protected]>
RDMA/mlx5: Do not allow the user to write to the clock page
Josh Collier <[email protected]>
IB/rdmavt: Fix frwr memory registration
Bjorn Andersson <[email protected]>
arm64: mm: Ensure tail of unaligned initrd is reserved
Mel Gorman <[email protected]>
mm: do not boost watermarks to avoid fragmentation for the DISCONTIG memory model
Peter Zijlstra <[email protected]>
trace: Fix preempt_enable_no_resched() abuse
Aurelien Jarno <[email protected]>
MIPS: scall64-o32: Fix indirect syscall number load
YueHaibing <[email protected]>
lib/Kconfig.debug: fix build error without CONFIG_BLOCK
Jérôme Glisse <[email protected]>
zram: pass down the bvec we need to read into in the work struct
Baolin Wang <[email protected]>
gpio: eic: sprd: Fix incorrect irq type setting for the sync EIC
Herbert Xu <[email protected]>
crypto: lrw - Fix atomic sleep when walking skcipher
Herbert Xu <[email protected]>
crypto: xts - Fix atomic sleep when walking skcipher
Jann Horn <[email protected]>
tracing: Fix buffer_ref pipe ops
Wenwen Wang <[email protected]>
tracing: Fix a memory leak by early error exit in trace_pid_write()
Frank Sorenson <[email protected]>
cifs: do not attempt cifs operation on smb2+ rename error
Jérôme Glisse <[email protected]>
cifs: fix page reference leak with readv/writev
Ronnie Sahlberg <[email protected]>
cifs: fix memory leak in SMB2_read
Paolo Valente <[email protected]>
block, bfq: fix use after free in bfq_bfqq_expire
YueHaibing <[email protected]>
fs/proc/proc_sysctl.c: Fix a NULL pointer dereference
Kailang Yang <[email protected]>
ALSA: hda/realtek - Move to ACT_INIT state
Christophe Leroy <[email protected]>
powerpc/vdso32: fix CLOCK_MONOTONIC on PPC64
Alexander Shishkin <[email protected]>
intel_th: gth: Fix an off-by-one in output unassigning
Pablo Neira Ayuso <[email protected]>
netfilter: nf_tables: bogus EBUSY in helper removal from transaction
Pablo Neira Ayuso <[email protected]>
netfilter: nf_tables: bogus EBUSY when deleting set after flush
-------------
Diffstat:
Documentation/networking/ip-sysctl.txt | 1 + Documentation/sysctl/vm.txt | 16 +- Makefile | 4 +- arch/arm/boot/compressed/head.S | 16 +- arch/arm64/mm/init.c | 2 +- arch/mips/kernel/scall64-o32.S | 2 +- arch/powerpc/configs/skiroot_defconfig | 1 + arch/powerpc/kernel/vdso32/gettimeofday.S | 2 +- arch/powerpc/platforms/Kconfig.cputype | 2 +- arch/x86/Makefile | 9 + arch/x86/events/intel/cstate.c | 10 +- block/bfq-iosched.c | 15 +- block/bfq-iosched.h | 2 +- block/bfq-wf2q.c | 17 +- crypto/lrw.c | 6 +- crypto/xts.c | 6 +- drivers/android/binder_alloc.c | 18 +- drivers/block/loop.c | 5 +- drivers/block/zram/zram_drv.c | 5 +- drivers/dma/mediatek/mtk-cqdma.c | 2 +- drivers/dma/sh/rcar-dmac.c | 30 +++- drivers/gpio/gpio-eic-sprd.c | 1 + drivers/gpu/drm/i915/intel_fbdev.c | 12 +- drivers/gpu/drm/ttm/ttm_bo.c | 10 +- drivers/gpu/drm/ttm/ttm_memory.c | 5 +- drivers/gpu/drm/vc4/vc4_crtc.c | 2 +- drivers/hwtracing/intel_th/gth.c | 2 +- drivers/infiniband/core/uverbs.h | 1 + drivers/infiniband/core/uverbs_main.c | 52 +++++- drivers/infiniband/hw/mlx5/main.c | 10 +- drivers/infiniband/sw/rdmavt/mr.c | 17 +- drivers/input/rmi4/rmi_f11.c | 2 +- drivers/net/ethernet/intel/fm10k/fm10k_main.c | 2 + drivers/net/ethernet/mellanox/mlx5/core/en/xdp.c | 24 ++- drivers/net/ethernet/mellanox/mlx5/core/en/xdp.h | 3 +- .../net/ethernet/mellanox/mlx5/core/en_ethtool.c | 2 +- drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 5 +- drivers/net/ethernet/mellanox/mlx5/core/port.c | 4 - drivers/net/ethernet/mellanox/mlxsw/pci_hw.h | 2 +- drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 6 +- drivers/net/ethernet/socionext/netsec.c | 11 +- drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 4 +- drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c | 8 +- drivers/net/slip/slhc.c | 2 +- drivers/net/team/team.c | 7 + drivers/net/wireless/mac80211_hwsim.c | 19 +- drivers/usb/core/driver.c | 23 ++- drivers/usb/core/hub.c | 16 +- drivers/usb/core/message.c | 3 +- drivers/usb/core/sysfs.c | 5 +- drivers/usb/core/usb.h | 10 +- drivers/vfio/vfio_iommu_type1.c | 14 ++ fs/aio.c | 200 +++++++++------------ fs/ceph/dir.c | 6 +- fs/ceph/mds_client.c | 70 ++++++-- fs/ceph/snap.c | 7 +- fs/cifs/file.c | 15 +- fs/cifs/inode.c | 4 + fs/cifs/misc.c | 23 ++- fs/cifs/smb2pdu.c | 1 + fs/ext4/xattr.c | 3 + fs/nfs/super.c | 3 +- fs/nfsd/nfs4callback.c | 8 +- fs/nfsd/nfs4state.c | 12 +- fs/nfsd/state.h | 1 + fs/proc/proc_sysctl.c | 6 +- fs/splice.c | 4 +- include/drm/ttm/ttm_bo_driver.h | 1 - include/linux/etherdevice.h | 12 ++ include/linux/pipe_fs_i.h | 1 + include/net/netfilter/nf_tables.h | 6 + include/net/netrom.h | 2 +- kernel/sched/deadline.c | 3 +- kernel/sched/fair.c | 4 + kernel/trace/ring_buffer.c | 2 +- kernel/trace/trace.c | 33 ++-- kernel/workqueue.c | 3 + lib/Kconfig.debug | 1 + mm/page_alloc.c | 13 ++ net/bridge/netfilter/ebtables.c | 3 +- net/ipv4/route.c | 32 +++- net/ipv4/sysctl_net_ipv4.c | 5 +- net/ncsi/ncsi-rsp.c | 6 +- net/netfilter/nf_tables_api.c | 28 ++- net/netfilter/nft_dynset.c | 13 +- net/netfilter/nft_lookup.c | 13 +- net/netfilter/nft_objref.c | 32 +++- net/netrom/af_netrom.c | 76 +++++--- net/netrom/nr_loopback.c | 2 +- net/netrom/nr_route.c | 2 +- net/netrom/sysctl_net_netrom.c | 5 +- net/rds/af_rds.c | 3 + net/rds/bind.c | 2 + net/rds/ib_fmr.c | 11 ++ net/rds/ib_rdma.c | 3 - net/rose/rose_loopback.c | 27 +-- net/rxrpc/input.c | 12 +- net/rxrpc/local_object.c | 3 +- net/sunrpc/cache.c | 3 + net/tipc/netlink_compat.c | 24 ++- net/tls/tls_device.c | 4 +- net/tls/tls_device_fallback.c | 13 +- net/tls/tls_main.c | 5 +- net/tls/tls_sw.c | 3 + sound/pci/hda/patch_realtek.c | 41 +++-- 105 files changed, 874 insertions(+), 396 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 20/89 mm: do not boost watermarks to avoid fragmentation for the DISCONTIG memory model
From: Mel Gorman <[email protected]>
commit 24512228b7a3f412b5a51f189df302616b021c33 upstream.
Mikulas Patocka reported that commit 1c30844d2dfe ("mm: reclaim small amounts of memory when an external fragmentation event occurs") "broke" memory management on parisc.
The machine is not NUMA but the DISCONTIG model creates three pgdats even though it's a UMA machine for the following ranges
0) Start 0x0000000000000000 End 0x000000003fffffff Size 1024 MB
1) Start 0x0000000100000000 End 0x00000001bfdfffff Size 3070 MB
2) Start 0x0000004040000000 End 0x00000040ffffffff Size 3072 MBMikulas reported:
With the patch 1c30844d2, the kernel will incorrectly reclaim the first zone when it fills up, ignoring the fact that there are two completely free zones. Basiscally, it limits cache size to 1GiB.
For example, if I run:
# dd if=/dev/sda of=/dev/null bs=1M count=2048
- with the proper kernel, there should be "Buffers - 2GiB" when this command finishes. With the patch 1c30844d2, buffers will consume just 1GiB or slightly more, because the kernel was incorrectly reclaiming them.
The page allocator and reclaim makes assumptions that pgdats really represent NUMA nodes and zones represent ranges and makes decisions on that basis. Watermark boosting for small pgdats leads to unexpected results even though this would have behaved reasonably on SPARSEMEM.
DISCONTIG is essentially deprecated and even parisc plans to move to SPARSEMEM so there is no need to be fancy, this patch simply disables watermark boosting by default on DISCONTIGMEM.
--- Documentation/sysctl/vm.txt | 16 ++++++++-------- mm/page_alloc.c | 13 +++++++++++++ 2 files changed, 21 insertions(+), 8 deletions(-)
Documentation/sysctl/vm.txt +8 -8
@@ -866,14 +866,14 @@ The intent is that compaction has less w increase the success rate of future high-order allocations such as SLUB allocations, THP and hugetlbfs pages. -To make it sensible with respect to the watermark_scale_factor parameter, -the unit is in fractions of 10,000. The default value of 15,000 means -that up to 150% of the high watermark will be reclaimed in the event of -a pageblock being mixed due to fragmentation. The level of reclaim is -determined by the number of fragmentation events that occurred in the -recent past. If this value is smaller than a pageblock then a pageblocks -worth of pages will be reclaimed (e.g. 2MB on 64-bit x86). A boost factor -of 0 will disable the feature. +To make it sensible with respect to the watermark_scale_factor +parameter, the unit is in fractions of 10,000. The default value of +15,000 on !DISCONTIGMEM configurations means that up to 150% of the high +watermark will be reclaimed in the event of a pageblock being mixed due +to fragmentation. The level of reclaim is determined by the number of +fragmentation events that occurred in the recent past. If this value is +smaller than a pageblock then a pageblocks worth of pages will be reclaimed +(e.g. 2MB on 64-bit x86). A boost factor of 0 will disable the feature. =============================================================
mm/page_alloc.c +13 -0
@@ -266,7 +266,20 @@ compound_page_dtor * const compound_pageint min_free_kbytes =1024 ;int user_min_free_kbytes =-1 ; +#ifdef CONFIG_DISCONTIGMEM +/* +* DiscontigMem defines memory ranges as separate pg_data_t even if the ranges +* are not on separate NUMA nodes. Functionally this works but with +* watermark_boost_factor, it can reclaim prematurely as the ranges can be +* quite small. By default, do not boost watermarks on discontigmem as in +* many cases very high-order allocations like THP are likely to be +* unsupported and the premature reclaim offsets the advantage of long-term +* fragmentation avoidance. +*/ +int watermark_boost_factor__read_mostly ; +#else int watermark_boost_factor__read_mostly =15000 ; +#endif int watermark_scale_factor =10 ;static unsigned long nr_kernel_pages__initdata ;
Greg Kroah-Hartman
maintainerPATCH 22/89 IB/rdmavt: Fix frwr memory registration
In reply to Greg Kroah-HartmanFrom: Josh Collier <[email protected]>
commit 7c39f7f671d2acc0a1f39ebbbee4303ad499bbfa upstream.
Current implementation was not properly handling frwr memory registrations. This was uncovered by commit 27f26cec761das ("xprtrdma:
Plant XID in on-the-wire RDMA offset (FRWR)") in which xprtrdma, which is used for NFS over RDMA, started failing as it was the first ULP to modify the ib_mr iova resulting in the NFS server getting REMOTE ACCESS ERROR when attempting to perform RDMA Writes to the client.
The fix is to properly capture the true iova, offset, and length in the call to ib_map_mr_sg, and then update the iova when processing the IB_WR_REG_MEM on the send queue.
--- drivers/infiniband/sw/rdmavt/mr.c | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-)
drivers/infiniband/sw/rdmavt/mr.c +10 -7
@@ -611,11 +611,6 @@ static int rvt_set_page(struct ib_mr *ibif (unlikely (mapped_segs == mr->mr.max_segs))return -ENOMEM ; -if (mr->mr.length ==0 ) { - mr->mr.user_base = addr; - mr->mr.iova = addr; - } - m = mapped_segs /RVT_SEGSZ ; n = mapped_segs %RVT_SEGSZ ; mr->mr.map[m]->segs[n].vaddr = (void *)addr;
@@ -633,17 +628,24 @@ static int rvt_set_page(struct ib_mr *ib* @sg_nents: number of entries in sg * @sg_offset: offset in bytes into sg * +* Overwrite rvt_mr length with mr length calculated by ib_sg_to_pages. +* * Return: number of sg elements mapped to the memory region */ int rvt_map_mr_sg (struct ib_mr *ibmr,struct scatterlist *sg,int sg_nents,unsigned int *sg_offset) {struct rvt_mr *mr =to_imr (ibmr); +int ret; mr->mr.length =0 ; mr->mr.page_shift =PAGE_SHIFT ; -return ib_sg_to_pages (ibmr, sg, sg_nents, sg_offset, - rvt_set_page); + ret =ib_sg_to_pages (ibmr, sg, sg_nents, sg_offset, rvt_set_page); + mr->mr.user_base = ibmr->iova; + mr->mr.iova = ibmr->iova; + mr->mr.offset = ibmr->iova - (u64 )mr->mr.map[0 ]->segs[0 ].vaddr; + mr->mr.length = (size_t )ibmr->length; +return ret; }/**
@@ -674,6 +676,7 @@ int rvt_fast_reg_mr(struct rvt_qp *qp, s ibmr->rkey = key; mr->mr.lkey = key; mr->mr.access_flags = access; + mr->mr.iova = ibmr->iova;atomic_set (&mr->mr.lkey_invalid,0 );return 0 ;
Greg Kroah-Hartman
maintainerPATCH 11/89 tracing: Fix a memory leak by early error exit in trace_pid_write()
In reply to Greg Kroah-HartmanFrom: Wenwen Wang <[email protected]>
commit 91862cc7867bba4ee5c8fcf0ca2f1d30427b6129 upstream.
In trace_pid_write(), the buffer for trace parser is allocated through kmalloc() in trace_parser_get_init(). Later on, after the buffer is used, it is then freed through kfree() in trace_parser_put(). However, it is possible that trace_pid_write() is terminated due to unexpected errors, e.g., ENOMEM. In that case, the allocated buffer will not be freed, which is a memory leak bug.
To fix this issue, free the allocated buffer when an error is encountered.
--- kernel/trace/trace.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
kernel/trace/trace.c +4 -1
@@ -496,8 +496,10 @@ int trace_pid_write(struct trace_pid_lis* not modified. */ pid_list =kmalloc (sizeof (*pid_list),GFP_KERNEL ); -if (!pid_list) +if (!pid_list) { +trace_parser_put (&parser);return -ENOMEM ; + } pid_list->pid_max =READ_ONCE (pid_max);
@@ -507,6 +509,7 @@ int trace_pid_write(struct trace_pid_lis pid_list->pids =vzalloc ((pid_list->pid_max +7 ) >>3 );if (!pid_list->pids) { +trace_parser_put (&parser);kfree (pid_list);return -ENOMEM ; }
Greg Kroah-Hartman
maintainerPATCH 24/89 RDMA/mlx5: Use rdma_user_map_io for mapping BAR pages
In reply to Greg Kroah-HartmanFrom: Jason Gunthorpe <[email protected]>
commit d5e560d3f72382ac4e3bfe4e0f0420e6a220b039 upstream.
Since mlx5 supports device disassociate it must use this API for all BAR page mmaps, otherwise the pages can remain mapped after the device is unplugged causing a system crash.
--- drivers/infiniband/hw/mlx5/main.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)
drivers/infiniband/hw/mlx5/main.c +3 -5
@@ -2154,14 +2154,12 @@ static int mlx5_ib_mmap(struct ib_uconteif (PAGE_SIZE >4096 )return -EOPNOTSUPP ; - vma->vm_page_prot =pgprot_noncached (vma->vm_page_prot); pfn = (dev->mdev->iseg_base + offsetof(struct mlx5_init_seg , internal_timer_h)) >>PAGE_SHIFT ; -if (io_remap_pfn_range (vma, vma->vm_start, pfn, -PAGE_SIZE , vma->vm_page_prot)) -return -EAGAIN ; -break ; +return rdma_user_mmap_io (&context->ibucontext, vma, pfn, +PAGE_SIZE , +pgprot_noncached (vma->vm_page_prot));case MLX5_IB_MMAP_CLOCK_INFO :return mlx5_ib_mmap_clock_info_page (dev, vma, context);
Greg Kroah-Hartman
maintainerPATCH 26/89 sched/numa: Fix a possible divide-by-zero
In reply to Greg Kroah-HartmanFrom: Xie XiuQi <[email protected]>
commit a860fa7b96e1a1c974556327aa1aee852d434c21 upstream.
sched_clock_cpu() may not be consistent between CPUs. If a task migrates to another CPU, then se.exec_start is set to that CPU's rq_clock_task() by update_stats_curr_start(). Specifically, the new value might be before the old value due to clock skew.
So then if in numa_get_avg_runtime() the expression:
'now - p->last_task_numa_placement'
ends up as -1, then the divider '*period + 1' in task_numa_placement() is 0 and things go bang. Similar to update_curr(), check if time goes backwards to avoid this.
[ peterz: Wrote new changelog. ]
[ mingo: Tweaked the code comment. ]
--- kernel/sched/fair.c | 4 ++++ 1 file changed, 4 insertions(+)
kernel/sched/fair.c +4 -0
@@ -1994,6 +1994,10 @@ static u64 numa_get_avg_runtime(struct tif (p->last_task_numa_placement) { delta = runtime - p->last_sum_exec_runtime; *period = now - p->last_task_numa_placement; + +/* Avoid time going backwards, prevent potential divide error: */ +if (unlikely ((s64)*period <0 )) + *period =0 ; }else { delta = p->se.avg.load_sum; *period =LOAD_AVG_MAX ;
Greg Kroah-Hartman
maintainerPATCH 27/89 ceph: only use d_name directly when parent is locked
In reply to Greg Kroah-HartmanFrom: Jeff Layton <[email protected]>
commit 1bcb344086f3ecf8d6705f6d708441baa823beb3 upstream.
Ben reported tripping the BUG_ON in create_request_message during some performance testing. Analysis of the vmcore showed that the length of the r_dentry->d_name string changed after we allocated the buffer, but before we encoded it.
build_dentry_path returns pointers to d_name in the common case of non-snapped dentries, but this optimization isn't safe unless the parent directory is locked. When it isn't, have the code make a copy of the d_name while holding the d_lock.
--- fs/ceph/mds_client.c | 61 +++++++++++++++++++++++++++++++++++++++++---------- 1 file changed, 50 insertions(+), 11 deletions(-)
fs/ceph/mds_client.c +50 -11
@@ -1958,10 +1958,39 @@ retry:return path; } +/* Duplicate the dentry->d_name.name safely */ +static int clone_dentry_name (struct dentry *dentry,const char **ppath, +int *ppathlen) +{ +u32 len; +char *name; + +retry: + len =READ_ONCE (dentry->d_name.len); + name =kmalloc (len +1 ,GFP_NOFS ); +if (!name) +return -ENOMEM ; + +spin_lock (&dentry->d_lock); +if (dentry->d_name.len != len) { +spin_unlock (&dentry->d_lock); +kfree (name); + goto retry; + } +memcpy (name, dentry->d_name.name, len); +spin_unlock (&dentry->d_lock); + + name[len] ='\0' ; + *ppath = name; + *ppathlen = len; +return 0 ; +} +static int build_dentry_path (struct dentry *dentry,struct inode *dir,const char **ppath,int *ppathlen,u64 *pino, -int *pfreepath) +bool *pfreepath,bool parent_locked) { +int ret;char *path;rcu_read_lock ();
@@ -1970,8 +1999,15 @@ static int build_dentry_path(struct dentif (dir &&ceph_snap (dir) ==CEPH_NOSNAP ) { *pino =ceph_ino (dir);rcu_read_unlock (); - *ppath = dentry->d_name.name; - *ppathlen = dentry->d_name.len; +if (parent_locked) { + *ppath = dentry->d_name.name; + *ppathlen = dentry->d_name.len; + }else { + ret =clone_dentry_name (dentry, ppath, ppathlen); +if (ret) +return ret; + *pfreepath = true; + }return 0 ; }rcu_read_unlock ();
@@ -1979,13 +2015,13 @@ static int build_dentry_path(struct dentif (IS_ERR (path))return PTR_ERR (path); *ppath = path; - *pfreepath =1 ; + *pfreepath = true;return 0 ; }static int build_inode_path (struct inode *inode,const char **ppath,int *ppathlen,u64 *pino, -int *pfreepath) +bool *pfreepath) {struct dentry *dentry;char *path;
@@ -2001,7 +2037,7 @@ static int build_inode_path(struct inodeif (IS_ERR (path))return PTR_ERR (path); *ppath = path; - *pfreepath =1 ; + *pfreepath = true;return 0 ; }
@@ -2012,7 +2048,7 @@ static int build_inode_path(struct inodestatic int set_request_path_attr (struct inode *rinode,struct dentry *rdentry,struct inode *rdiri,const char *rpath,u64 rino,const char **ppath,int *pathlen, -u64 *ino,int *freepath) +u64 *ino,bool *freepath,bool parent_locked) {int r =0 ;
@@ -2022,7 +2058,7 @@ static int set_request_path_attr(struct ceph_snap(rinode)); }else if (rdentry) { r =build_dentry_path (rdentry, rdiri, ppath, pathlen, ino, - freepath); + freepath, parent_locked);dout (" dentry %p %llx/%.*s\n" , rdentry, *ino, *pathlen, *ppath); }else if (rpath || rino) {
@@ -2048,7 +2084,7 @@ static struct ceph_msg *create_request_mconst char *path2 =NULL ;u64 ino1 =0 , ino2 =0 ;int pathlen1 =0 , pathlen2 =0 ; -int freepath1 =0 , freepath2 =0 ; +bool freepath1 = false, freepath2 = false;int len;u16 releases;void *p, *end;
@@ -2056,16 +2092,19 @@ static struct ceph_msg *create_request_m ret =set_request_path_attr (req->r_inode, req->r_dentry, req->r_parent, req->r_path1, req->r_ino1.ino, - &path1, &pathlen1, &ino1, &freepath1); + &path1, &pathlen1, &ino1, &freepath1, +test_bit (CEPH_MDS_R_PARENT_LOCKED , + &req->r_req_flags));if (ret <0 ) { msg =ERR_PTR (ret); goto out; } +/* If r_old_dentry is set, then assume that its parent is locked */ ret =set_request_path_attr (NULL , req->r_old_dentry, req->r_old_dentry_dir, req->r_path2, req->r_ino2.ino, - &path2, &pathlen2, &ino2, &freepath2); + &path2, &pathlen2, &ino2, &freepath2, true);if (ret <0 ) { msg =ERR_PTR (ret); goto out_free1;
Greg Kroah-Hartman
maintainerPATCH 28/89 ceph: ensure d_name stability in ceph_dentry_hash()
In reply to Greg Kroah-HartmanFrom: Jeff Layton <[email protected]>
commit 76a495d666e5043ffc315695f8241f5e94a98849 upstream.
Take the d_lock here to ensure that d_name doesn't change.
--- fs/ceph/dir.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
fs/ceph/dir.c +5 -1
@@ -1470,6 +1470,7 @@ void ceph_dentry_lru_del(struct dentry *unsigned ceph_dentry_hash (struct inode *dir,struct dentry *dn) {struct ceph_inode_info *dci =ceph_inode (dir); +unsigned hash;switch (dci->i_dir_layout.dl_dir_hash) {case 0 :/* for backward compat */
@@ -1477,8 +1478,11 @@ unsigned ceph_dentry_hash(struct inode *return dn->d_name.hash;default : -return ceph_str_hash (dci->i_dir_layout.dl_dir_hash, +spin_lock (&dn->d_lock); + hash =ceph_str_hash (dci->i_dir_layout.dl_dir_hash, dn->d_name.name, dn->d_name.len); +spin_unlock (&dn->d_lock); +return hash; } }
Greg Kroah-Hartman
maintainerPATCH 31/89 nfsd: wake waiters blocked on file_lock before deleting it
In reply to Greg Kroah-HartmanFrom: Jeff Layton <[email protected]>
commit 6aaafc43a4ecc5bc8a3f6a2811d5eddc996a97f3 upstream.
After a blocked nfsd file_lock request is deleted, knfsd will send a callback to the client and then free the request. Commit 16306a61d3b7 ("fs/locks: always delete_block after waiting.") changed it such that locks_delete_block is always called on a request after it is awoken, but that patch missed fixing up blocked nfsd request handling.
Call locks_delete_block on the block to wake up any locks still blocked on the nfsd lock request before freeing it. Some of its callers already do this however, so just remove those calls.
URL: https://bugzilla.kernel.org/show_bug.cgi?id=203363
--- fs/nfsd/nfs4state.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
fs/nfsd/nfs4state.c +1 -2
@@ -265,6 +265,7 @@ find_or_allocate_block(struct nfs4_lockostatic void free_blocked_lock (struct nfsd4_blocked_lock *nbl) { +locks_delete_block (&nbl->nbl_lock);locks_release_private (&nbl->nbl_lock);kfree (nbl); }
@@ -293,7 +294,6 @@ remove_blocked_locks(struct nfs4_lockown nbl = list_first_entry(&reaplist, struct nfsd4_blocked_lock, nbl_lru);list_del_init (&nbl->nbl_lru); -locks_delete_block (&nbl->nbl_lock);free_blocked_lock (nbl); } }
@@ -4863,7 +4863,6 @@ nfs4_laundromat(struct nfsd_net *nn) nbl =list_first_entry (&reaplist, struct nfsd4_blocked_lock, nbl_lru);list_del_init (&nbl->nbl_lru); -locks_delete_block (&nbl->nbl_lock);free_blocked_lock (nbl); } out:
Greg Kroah-Hartman
maintainerPATCH 32/89 nfsd: wake blocked file lock waiters before sending callback
In reply to Greg Kroah-HartmanFrom: Jeff Layton <[email protected]>
commit f456458e4d25a8962d0946891617c76cc3ff5fb9 upstream.
When a blocked NFS lock is "awoken" we send a callback to the server and then wake any hosts waiting on it. If a client attempts to get a lock and then drops off the net, we could end up waiting for a long time until we end up waking locks blocked on that request.
So, wake any other waiting lock requests before sending the callback. Do this by calling locks_delete_block in a new "prepare" phase for CB_NOTIFY_LOCK callbacks.
URL: https://bugzilla.kernel.org/show_bug.cgi?id=203363
--- fs/nfsd/nfs4state.c | 9 +++++++++ 1 file changed, 9 insertions(+)
fs/nfsd/nfs4state.c +9 -0
@@ -298,6 +298,14 @@ remove_blocked_locks(struct nfs4_lockown } } +static void +nfsd4_cb_notify_lock_prepare (struct nfsd4_callback *cb) +{ +struct nfsd4_blocked_lock *nbl =container_of (cb, + struct nfsd4_blocked_lock, nbl_cb); +locks_delete_block (&nbl->nbl_lock); +} +static int nfsd4_cb_notify_lock_done (struct nfsd4_callback *cb,struct rpc_task *task) {
@@ -325,6 +333,7 @@ nfsd4_cb_notify_lock_release(struct nfsd }static const struct nfsd4_callback_ops nfsd4_cb_notify_lock_ops = { + .prepare = nfsd4_cb_notify_lock_prepare, .done = nfsd4_cb_notify_lock_done, .release = nfsd4_cb_notify_lock_release, };
Greg Kroah-Hartman
maintainerPATCH 34/89 perf/x86/intel: Update KBL Package C-state events to also include PC8/PC9/PC10 counters
In reply to Greg Kroah-HartmanFrom: Harry Pan <[email protected]>
commit 82c99f7a81f28f8c1be5f701c8377d14c4075b10 upstream.
Kaby Lake (and Coffee Lake) has PC8/PC9/PC10 residency counters.
This patch updates the list of Kaby/Coffee Lake PMU event counters from the snb_cstates[] list of events to the hswult_cstates[] list of events, which keeps all previously supported events and also adds the PKG_C8, PKG_C9 and PKG_C10 residency counters.
This allows user space tools to profile them through the perf interface.
--- arch/x86/events/intel/cstate.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
arch/x86/events/intel/cstate.c +5 -5
@@ -76,15 +76,15 @@* Scope: Package (physical package) * MSR_PKG_C8_RESIDENCY: Package C8 Residency Counter. * perf code: 0x04 -* Available model: HSW ULT,CNL +* Available model: HSW ULT,KBL,CNL * Scope: Package (physical package) * MSR_PKG_C9_RESIDENCY: Package C9 Residency Counter. * perf code: 0x05 -* Available model: HSW ULT,CNL +* Available model: HSW ULT,KBL,CNL * Scope: Package (physical package) * MSR_PKG_C10_RESIDENCY: Package C10 Residency Counter. * perf code: 0x06 -* Available model: HSW ULT,GLM,CNL +* Available model: HSW ULT,KBL,GLM,CNL * Scope: Package (physical package) * */
@@ -572,8 +572,8 @@ static const struct x86_cpu_id intel_cstX86_CSTATES_MODEL (INTEL_FAM6_SKYLAKE_DESKTOP , snb_cstates),X86_CSTATES_MODEL (INTEL_FAM6_SKYLAKE_X , snb_cstates), -X86_CSTATES_MODEL (INTEL_FAM6_KABYLAKE_MOBILE , snb_cstates), -X86_CSTATES_MODEL (INTEL_FAM6_KABYLAKE_DESKTOP , snb_cstates), +X86_CSTATES_MODEL (INTEL_FAM6_KABYLAKE_MOBILE , hswult_cstates), +X86_CSTATES_MODEL (INTEL_FAM6_KABYLAKE_DESKTOP , hswult_cstates), X86_CSTATES_MODEL(INTEL_FAM6_CANNONLAKE_MOBILE, cnl_cstates),
Greg Kroah-Hartman
maintainerPATCH 36/89 vfio/type1: Limit DMA mappings per container
In reply to Greg Kroah-HartmanFrom: Alex Williamson <[email protected]>
commit 492855939bdb59c6f947b0b5b44af9ad82b7e38c upstream.
Memory backed DMA mappings are accounted against a user's locked memory limit, including multiple mappings of the same memory. This accounting bounds the number of such mappings that a user can create. However, DMA mappings that are not backed by memory, such as DMA mappings of device MMIO via mmaps, do not make use of page pinning and therefore do not count against the user's locked memory limit. These mappings still consume memory, but the memory is not well associated to the process for the purpose of oom killing a task.
To add bounding on this use case, we introduce a limit to the total number of concurrent DMA mappings that a user is allowed to create. This limit is exposed as a tunable module option where the default value of 64K is expected to be well in excess of any reasonable use case (a large virtual machine configuration would typically only make use of tens of concurrent mappings).
This fixes CVE-2019-3882.
--- drivers/vfio/vfio_iommu_type1.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
drivers/vfio/vfio_iommu_type1.c +14 -0
@@ -58,12 +58,18 @@ module_param_named(disable_hugepages,MODULE_PARM_DESC (disable_hugepages,"Disable VFIO IOMMU support for IOMMU hugepages." ); +static unsigned int dma_entry_limit__read_mostly =U16_MAX ; +module_param_named (dma_entry_limit, dma_entry_limit, uint,0644 ); +MODULE_PARM_DESC (dma_entry_limit, +"Maximum number of user DMA mappings per container (65535)." ); +struct vfio_iommu {struct list_head domain_list;struct vfio_domain *external_domain;/* domain for external user */ struct mutex lock;struct rb_root dma_list;struct blocking_notifier_head notifier; +unsigned int dma_avail;bool v2;bool nesting; };
@@ -836,6 +842,7 @@ static void vfio_remove_dma(struct vfio_vfio_unlink_dma (iommu, dma);put_task_struct (dma->task);kfree (dma); + iommu->dma_avail++; }static unsigned long vfio_pgsize_bitmap (struct vfio_iommu *iommu)
@@ -1081,12 +1088,18 @@ static int vfio_dma_do_map(struct vfio_i goto out_unlock; } +if (!iommu->dma_avail) { + ret = -ENOSPC ; + goto out_unlock; + } + dma =kzalloc (sizeof (*dma),GFP_KERNEL );if (!dma) { ret = -ENOMEM ; goto out_unlock; } + iommu->dma_avail--; dma->iova = iova; dma->vaddr = vaddr; dma->prot = prot;
@@ -1583,6 +1596,7 @@ static void *vfio_iommu_type1_open(unsigINIT_LIST_HEAD (&iommu->domain_list); iommu->dma_list =RB_ROOT ; + iommu->dma_avail = dma_entry_limit;mutex_init (&iommu->lock);BLOCKING_INIT_NOTIFIER_HEAD (&iommu->notifier);
Greg Kroah-Hartman
maintainerPATCH 37/89 dmaengine: sh: rcar-dmac: With cyclic DMA residue 0 is valid
In reply to Greg Kroah-HartmanFrom: Dirk Behme <[email protected]>
commit 907bd68a2edc491849e2fdcfe52c4596627bca94 upstream.
Having a cyclic DMA, a residue 0 is not an indication of a completed DMA. In case of cyclic DMA make sure that dma_set_residue() is called and with this a residue of 0 is forwarded correctly to the caller.
--- drivers/dma/sh/rcar-dmac.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/dma/sh/rcar-dmac.c +3 -1
@@ -1368,6 +1368,7 @@ static enum dma_status rcar_dmac_tx_statenum dma_status status;unsigned long flags;unsigned int residue; +bool cyclic; status =dma_cookie_status (chan, cookie, txstate);if (status ==DMA_COMPLETE || !txstate)
@@ -1375,10 +1376,11 @@ static enum dma_status rcar_dmac_tx_statspin_lock_irqsave (&rchan->lock, flags); residue =rcar_dmac_chan_get_residue (rchan, cookie); + cyclic = rchan->desc.running ? rchan->desc.running->cyclic : false;spin_unlock_irqrestore (&rchan->lock, flags);/* if there's no residue, the cookie is complete */ -if (!residue) +if (!residue && !cyclic)return DMA_COMPLETE ;dma_set_residue (txstate, residue);
Greg Kroah-Hartman
maintainerPATCH 39/89 dmaengine: mediatek-cqdma: fix wrong register usage in mtk_cqdma_start
In reply to Greg Kroah-HartmanFrom: Shun-Chih Yu <[email protected]>
commit 5bb5c3a3ac102158b799bf5eda871223aa5e9c25 upstream.
This patch fixes wrong register usage in the mtk_cqdma_start. The destination register should be MTK_CQDMA_DST2 instead.
--- drivers/dma/mediatek/mtk-cqdma.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/dma/mediatek/mtk-cqdma.c +1 -1
@@ -253,7 +253,7 @@ static void mtk_cqdma_start(struct mtk_c#ifdef CONFIG_ARCH_DMA_ADDR_T_64BIT mtk_dma_set (pc,MTK_CQDMA_DST2 , cvd->dest >>MTK_CQDMA_ADDR2_SHFIT );#else -mtk_dma_set (pc,MTK_CQDMA_SRC2 ,0 ); +mtk_dma_set (pc,MTK_CQDMA_DST2 ,0 );#endif /* setup the length */
Greg Kroah-Hartman
maintainerPATCH 40/89 ARM: 8857/1: efi: enable CP15 DMB instructions before cleaning the cache
In reply to Greg Kroah-HartmanFrom: Ard Biesheuvel <[email protected]>
commit e17b1af96b2afc38e684aa2f1033387e2ed10029 upstream.
The EFI stub is entered with the caches and MMU enabled by the firmware, and once the stub is ready to hand over to the decompressor, we clean and disable the caches.
The cache clean routines use CP15 barrier instructions, which can be disabled via SCTLR. Normally, when using the provided cache handling routines to enable the caches and MMU, this bit is enabled as well. However, but since we entered the stub with the caches already enabled, this routine is not executed before we call the cache clean routines, resulting in undefined instruction exceptions if the firmware never enabled this bit.
So set the bit explicitly in the EFI entry code, but do so in a way that guarantees that the resulting code can still run on v6 cores as well (which are guaranteed to have CP15 barriers enabled)
--- arch/arm/boot/compressed/head.S | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-)
arch/arm/boot/compressed/head.S +15 -1
@@ -1438,7 +1438,21 @@ ENTRY(efi_stub_entry) @ Preserve return value of efi_entry() in r4 mov r4, r0 - bl cache_clean_flush + + @ our cache maintenance code relies on CP15 barrier instructions + @ but since we arrived here with the MMU and caches configured + @ by UEFI, we must check that the CP15BEN bit is set in SCTLR. + @ Note that this bit is RAO/WI on v6 and earlier, so the ISB in + @ the enable path will be executed on v7+ only. + mrc p15, 0, r1, c1, c0, 0 @ read SCTLR + tst r1, #(1 << 5) @ CP15BEN bit set? + bne 0f + orr r1, r1, #(1 << 5) @ CP15 barrier instructions + mcr p15, 0, r1, c1, c0, 0 @ write SCTLR + ARM( .inst 0xf57ff06f @ v7+ isb ) + THUMB( isb ) + +0: bl cache_clean_flush bl cache_off @ Set parameters for booting zImage according to boot protocol
Greg Kroah-Hartman
maintainerPATCH 42/89 drm/vc4: Fix memory leak during gpu reset.
In reply to Greg Kroah-HartmanFrom: Maarten Lankhorst <[email protected]>
commit d08106796a78a4273e39e1bbdf538dc4334b2635 upstream.
__drm_atomic_helper_crtc_destroy_state does not free memory, it only cleans it up. Fix this by calling the functions own destroy function.
--- drivers/gpu/drm/vc4/vc4_crtc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/vc4/vc4_crtc.c +1 -1
@@ -999,7 +999,7 @@ static void vc4_crtc_reset(struct drm_crtc *crtc) {if (crtc->state) -__drm_atomic_helper_crtc_destroy_state (crtc->state); +vc4_crtc_destroy_state (crtc->state); crtc->state =kzalloc (sizeof (struct vc4_crtc_state ),GFP_KERNEL );if (crtc->state)
Greg Kroah-Hartman
maintainerPATCH 44/89 Revert "drm/i915/fbdev: Actually configure untiled displays"
In reply to Greg Kroah-HartmanFrom: Dave Airlie <[email protected]>
commit 9fa246256e09dc30820524401cdbeeaadee94025 upstream.
This reverts commit d179b88deb3bf6fed4991a31fd6f0f2cad21fab5.
This commit is documented to break userspace X.org modesetting driver in certain configurations.
The X.org modesetting userspace driver is broken. No fixes are available yet. In order for this patch to be applied it either needs a config option or a workaround developed.
This has been reported a few times, saying it's a userspace problem is clearly against the regression rules.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109806
--- drivers/gpu/drm/i915/intel_fbdev.c | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-)
drivers/gpu/drm/i915/intel_fbdev.c +5 -7
@@ -336,8 +336,8 @@ static bool intel_fb_initial_config(stru bool *enabled, int width, int height) { struct drm_i915_private *dev_priv = to_i915(fb_helper->dev); +unsigned long conn_configured, conn_seq, mask;unsigned int count =min (fb_helper->connector_count,BITS_PER_LONG ); -unsigned long conn_configured, conn_seq;int i, j;bool *save_enabled;bool fallback = true, ret = true;
@@ -355,9 +355,10 @@ static bool intel_fb_initial_config(strudrm_modeset_backoff (&ctx);memcpy (save_enabled, enabled, count); - conn_seq =GENMASK (count -1 ,0 ); + mask =GENMASK (count -1 ,0 ); conn_configured =0 ; retry: + conn_seq = conn_configured;for (i =0 ; i < count; i++) {struct drm_fb_helper_connector *fb_conn;struct drm_connector *connector;
@@ -370,8 +371,7 @@ retry:if (conn_configured &BIT (i))continue ; -/* First pass, only consider tiled connectors */ -if (conn_seq ==GENMASK (count -1 ,0 ) && !connector->has_tile) +if (conn_seq ==0 && !connector->has_tile)continue ;if (connector->status == connector_status_connected)
@@ -475,10 +475,8 @@ retry: conn_configured |=BIT (i); } -if (conn_configured != conn_seq) {/* repeat until no more are found */ - conn_seq = conn_configured; +if ((conn_configured & mask) != mask && conn_configured != conn_seq) goto retry; - }/* * If the BIOS didn't enable everything it could, fall back to have the
Greg Kroah-Hartman
maintainerPATCH 14/89 crypto: lrw - Fix atomic sleep when walking skcipher
In reply to Greg Kroah-HartmanFrom: Herbert Xu <[email protected]>
commit b257b48cd5830c5b1d0c347eb281f9c28056f881 upstream.
When we perform a walk in the completion function, we need to ensure that it is atomic.
--- crypto/lrw.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
crypto/lrw.c +5 -1
@@ -212,8 +212,12 @@ static void crypt_done(struct crypto_asy {struct skcipher_request *req = areq->data; -if (!err) +if (!err) { +struct rctx *rctx =skcipher_request_ctx (req); + + rctx->subreq.base.flags &= ~CRYPTO_TFM_REQ_MAY_SLEEP ; err =xor_tweak_post (req); + }skcipher_request_complete (req, err); }
Greg Kroah-Hartman
maintainerPATCH 15/89 gpio: eic: sprd: Fix incorrect irq type setting for the sync EIC
In reply to Greg Kroah-HartmanFrom: Baolin Wang <[email protected]>
commit 102bbe34b31c9159e714432afd64458f6f3876d7 upstream.
When setting sync EIC as IRQ_TYPE_EDGE_BOTH type, we missed to set the SPRD_EIC_SYNC_INTMODE register to 0, which means detecting edge signals.
Thus this patch fixes the issue.
--- drivers/gpio/gpio-eic-sprd.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpio/gpio-eic-sprd.c +1 -0
@@ -414,6 +414,7 @@ static int sprd_eic_irq_set_type(structirq_set_handler_locked (data, handle_edge_irq);break ;case IRQ_TYPE_EDGE_BOTH : +sprd_eic_update (chip, offset,SPRD_EIC_SYNC_INTMODE ,0 );sprd_eic_update (chip, offset,SPRD_EIC_SYNC_INTBOTH ,1 );irq_set_handler_locked (data, handle_edge_irq);break ;
Greg Kroah-Hartman
maintainerPATCH 16/89 zram: pass down the bvec we need to read into in the work struct
In reply to Greg Kroah-HartmanFrom: Jérôme Glisse <[email protected]>
commit e153abc0739ff77bd89c9ba1688cdb963464af97 upstream.
When scheduling work item to read page we need to pass down the proper bvec struct which points to the page to read into. Before this patch it uses a randomly initialized bvec (only if PAGE_SIZE != 4096) which is wrong.
Note that without this patch on arch/kernel where PAGE_SIZE != 4096 userspace could read random memory through a zram block device (thought userspace probably would have no control on the address being read).
--- drivers/block/zram/zram_drv.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/block/zram/zram_drv.c +3 -2
@@ -774,18 +774,18 @@ struct zram_work {struct zram *zram;unsigned long entry;struct bio *bio; +struct bio_vec bvec; };#if PAGE_SIZE !=4096 static void zram_sync_read (struct work_struct *work) { -struct bio_vec bvec; struct zram_work *zw = container_of(work, struct zram_work, work);struct zram *zram = zw->zram;unsigned long entry = zw->entry;struct bio *bio = zw->bio; -read_from_bdev_async (zram, &bvec, entry, bio); +read_from_bdev_async (zram, &zw->bvec, entry, bio); }/*
@@ -798,6 +798,7 @@ static int read_from_bdev_sync(struct zr {struct zram_work work; + work.bvec = *bvec; work.zram = zram; work.entry = entry; work.bio = bio;
Greg Kroah-Hartman
maintainerPATCH 17/89 lib/Kconfig.debug: fix build error without CONFIG_BLOCK
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
commit ae3d6a323347940f0548bbb4b17f0bb2e9164169 upstream.
If CONFIG_TEST_KMOD is set to M, while CONFIG_BLOCK is not set, XFS and BTRFS can not be compiled successly.
--- lib/Kconfig.debug | 1 + 1 file changed, 1 insertion(+)
lib/Kconfig.debug +1 -0
@@ -1952,6 +1952,7 @@ config TEST_KMOD depends on m depends on BLOCK && (64BIT || LBDAF) # for XFS, BTRFS depends on NETDEVICES && NET_CORE && INET # for TUN + depends on BLOCK select TEST_LKM select XFS_FS select TUN
Greg Kroah-Hartman
maintainerPATCH 18/89 MIPS: scall64-o32: Fix indirect syscall number load
In reply to Greg Kroah-HartmanFrom: Aurelien Jarno <[email protected]>
commit 79b4a9cf0e2ea8203ce777c8d5cfa86c71eae86e upstream.
Commit 4c21b8fd8f14 (MIPS: seccomp: Handle indirect system calls (o32)) added indirect syscall detection for O32 processes running on MIPS64, but it did not work correctly for big endian kernel/processes. The reason is that the syscall number is loaded from ARG1 using the lw instruction while this is a 64-bit value, so zero is loaded instead of the syscall number.
Fix the code by using the ld instruction instead. When running a 32-bit processes on a 64 bit CPU, the values are properly sign-extended, so it ensures the value passed to syscall_trace_enter is correct.
Recent systemd versions with seccomp enabled whitelist the getpid syscall for their internal processes (e.g. systemd-journald), but call it through syscall(SYS_getpid). This fix therefore allows O32 big endian systems with a 64-bit kernel to run recent systemd versions.
--- arch/mips/kernel/scall64-o32.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/mips/kernel/scall64-o32.S +1 -1
@@ -125,7 +125,7 @@ trace_a_syscall: subu t1, v0, __NR_O32_Linux move a1, v0 bnez t1, 1f /* __NR_syscall at offset 0 */ - lw a1, PT_R4(sp) /* Arg1 for __NR_syscall case */ + ld a1, PT_R4(sp) /* Arg1 for __NR_syscall case */ .set pop 1: jal syscall_trace_enter
Greg Kroah-Hartman
maintainerPATCH 19/89 trace: Fix preempt_enable_no_resched() abuse
In reply to Greg Kroah-HartmanFrom: Peter Zijlstra <[email protected]>
commit d6097c9e4454adf1f8f2c9547c2fa6060d55d952 upstream.
Unless the very next line is schedule(), or implies it, one must not use preempt_enable_no_resched(). It can cause a preemption to go missing and thereby cause arbitrary delays, breaking the PREEMPT=y invariant.
--- kernel/trace/ring_buffer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/ring_buffer.c +1 -1
@@ -776,7 +776,7 @@ u64 ring_buffer_time_stamp(struct ring_bpreempt_disable_notrace (); time =rb_time_stamp (buffer); -preempt_enable_no_resched_notrace (); +preempt_enable_notrace ();return time; }
Greg Kroah-Hartman
maintainerPATCH 10/89 cifs: do not attempt cifs operation on smb2+ rename error
In reply to Greg Kroah-HartmanFrom: Frank Sorenson <[email protected]>
commit 652727bbe1b17993636346716ae5867627793647 upstream.
A path-based rename returning EBUSY will incorrectly try opening the file with a cifs (NT Create AndX) operation on an smb2+ mount, which causes the server to force a session close.
If the mount is smb2+, skip the fallback.
--- fs/cifs/inode.c | 4 ++++ 1 file changed, 4 insertions(+)
fs/cifs/inode.c +4 -0
@@ -1735,6 +1735,10 @@ cifs_do_rename(const unsigned int xid, sif (rc ==0 || rc != -EBUSY ) goto do_rename_exit; +/* Don't fall back to using SMB on SMB 2+ mount */ +if (server->vals->protocol_id !=0 ) + goto do_rename_exit; +/* open-file renames don't work across directories */ if (to_dentry->d_parent != from_dentry->d_parent) goto do_rename_exit;
Greg Kroah-Hartman
maintainerPATCH 48/89 ext4: fix some error pointer dereferences
In reply to Greg Kroah-HartmanFrom: Dan Carpenter <[email protected]>
commit 7159a986b4202343f6cca3bb8079ecace5816fd6 upstream.
We can't pass error pointers to brelse().
--- fs/ext4/xattr.c | 3 +++ 1 file changed, 3 insertions(+)
fs/ext4/xattr.c +3 -0
@@ -829,6 +829,7 @@ int ext4_get_inode_usage(struct inode *i bh =ext4_sb_bread (inode->i_sb,EXT4_I (inode)->i_file_acl,REQ_PRIO );if (IS_ERR (bh)) { ret =PTR_ERR (bh); + bh =NULL ; goto out; }
@@ -2903,6 +2904,7 @@ int ext4_xattr_delete_inode(handle_t *haif (error == -EIO )EXT4_ERROR_INODE (inode,"block %llu read error" ,EXT4_I (inode)->i_file_acl); + bh =NULL ; goto cleanup; } error =ext4_xattr_check_block (inode, bh);
@@ -3059,6 +3061,7 @@ ext4_xattr_block_cache_find(struct inodeif (IS_ERR (bh)) {if (PTR_ERR (bh) == -ENOMEM )return NULL ; + bh =NULL ;EXT4_ERROR_INODE (inode,"block %lu read error" , (unsigned long )ce->e_value); }else if (ext4_xattr_cmp (header,BHDR (bh)) ==0 ) {
Greg Kroah-Hartman
maintainerPATCH 57/89 netfilter: ebtables: CONFIG_COMPAT: drop a bogus WARN_ON
In reply to Greg Kroah-HartmanFrom: Florian Westphal <[email protected]>
commit 7caa56f006e9d712b44f27b32520c66420d5cbc6 upstream.
It means userspace gave us a ruleset where there is some other data after the ebtables target but before the beginning of the next rule.
--- net/bridge/netfilter/ebtables.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/bridge/netfilter/ebtables.c +2 -1
@@ -2032,7 +2032,8 @@ static int ebt_size_mwt(struct compat_ebif (match_kern) match_kern->match_size = ret; -if (WARN_ON (type ==EBT_COMPAT_TARGET && size_left)) +/* rule should have no remaining data after target */ +if (type ==EBT_COMPAT_TARGET && size_left)return -EINVAL ; match32 = (struct compat_ebt_entry_mwt *) buf;
Greg Kroah-Hartman
maintainerPATCH 58/89 fm10k: Fix a potential NULL pointer dereference
In reply to Greg Kroah-HartmanFrom: Yue Haibing <[email protected]>
commit 01ca667133d019edc9f0a1f70a272447c84ec41f upstream.
Syzkaller report this:
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN PTI CPU: 0 PID: 4378 Comm: syz-executor.0 Tainted: G C 5.0.0+ #5 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:__lock_acquire+0x95b/0x3200 kernel/locking/lockdep.c:3573 Code: 00 0f 85 28 1e 00 00 48 81 c4 08 01 00 00 5b 5d 41 5c 41 5d 41 5e 41 5f c3 4c 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 cc 24 00 00 49 81 7d 00 e0 de 03 a6 41 bc 00 00 RSP: 0018:ffff8881e3c07a40 EFLAGS: 00010002 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000010 RSI: 0000000000000000 RDI: 0000000000000080 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: ffff8881e3c07d98 R11: ffff8881c7f21f80 R12: 0000000000000001 R13: 0000000000000080 R14: 0000000000000000 R15: 0000000000000001 FS: 00007fce2252e700(0000) GS:ffff8881f2400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fffc7eb0228 CR3: 00000001e5bea002 CR4: 00000000007606f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: lock_acquire+0xff/0x2c0 kernel/locking/lockdep.c:4211 __mutex_lock_common kernel/locking/mutex.c:925 [inline] __mutex_lock+0xdf/0x1050 kernel/locking/mutex.c:1072 drain_workqueue+0x24/0x3f0 kernel/workqueue.c:2934 destroy_workqueue+0x23/0x630 kernel/workqueue.c:4319 __do_sys_delete_module kernel/module.c:1018 [inline] __se_sys_delete_module kernel/module.c:961 [inline] __x64_sys_delete_module+0x30c/0x480 kernel/module.c:961 do_syscall_64+0x9f/0x450 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x462e99 Code: f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fce2252dc58 EFLAGS: 00000246 ORIG_RAX: 00000000000000b0 RAX: ffffffffffffffda RBX: 000000000073bf00 RCX: 0000000000462e99 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000140 RBP: 0000000000000002 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fce2252e6bc R13: 00000000004bcca9 R14: 00000000006f6b48 R15: 00000000ffffffff
If alloc_workqueue fails, it should return -ENOMEM, otherwise may trigger this NULL pointer dereference while unloading drivers.
--- drivers/net/ethernet/intel/fm10k/fm10k_main.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/ethernet/intel/fm10k/fm10k_main.c +2 -0
@@ -41,6 +41,8 @@ static int __init fm10k_init_module(void/* create driver workqueue */ fm10k_workqueue =alloc_workqueue ("%s" ,WQ_MEM_RECLAIM ,0 , fm10k_driver_name); +if (!fm10k_workqueue) +return -ENOMEM ;fm10k_dbg_init ();
Greg Kroah-Hartman
maintainerPATCH 59/89 tipc: check bearer name with right length in tipc_nl_compat_bearer_enable
In reply to Greg Kroah-HartmanFrom: Xin Long <[email protected]>
commit 6f07e5f06c8712acc423485f657799fc8e11e56c upstream.
Syzbot reported the following crash:
BUG: KMSAN: uninit-value in memchr+0xce/0x110 lib/string.c:961 memchr+0xce/0x110 lib/string.c:961 string_is_valid net/tipc/netlink_compat.c:176 [inline] tipc_nl_compat_bearer_enable+0x2c4/0x910 net/tipc/netlink_compat.c:401 __tipc_nl_compat_doit net/tipc/netlink_compat.c:321 [inline] tipc_nl_compat_doit+0x3aa/0xaf0 net/tipc/netlink_compat.c:354 tipc_nl_compat_handle net/tipc/netlink_compat.c:1162 [inline] tipc_nl_compat_recv+0x1ae7/0x2750 net/tipc/netlink_compat.c:1265 genl_family_rcv_msg net/netlink/genetlink.c:601 [inline] genl_rcv_msg+0x185f/0x1a60 net/netlink/genetlink.c:626 netlink_rcv_skb+0x431/0x620 net/netlink/af_netlink.c:2477 genl_rcv+0x63/0x80 net/netlink/genetlink.c:637 netlink_unicast_kernel net/netlink/af_netlink.c:1310 [inline] netlink_unicast+0xf3e/0x1020 net/netlink/af_netlink.c:1336 netlink_sendmsg+0x127f/0x1300 net/netlink/af_netlink.c:1917 sock_sendmsg_nosec net/socket.c:622 [inline] sock_sendmsg net/socket.c:632 [inline]
Uninit was created at:
__alloc_skb+0x309/0xa20 net/core/skbuff.c:208 alloc_skb include/linux/skbuff.h:1012 [inline] netlink_alloc_large_skb net/netlink/af_netlink.c:1182 [inline] netlink_sendmsg+0xb82/0x1300 net/netlink/af_netlink.c:1892 sock_sendmsg_nosec net/socket.c:622 [inline] sock_sendmsg net/socket.c:632 [inline]
It was triggered when the bearer name size < TIPC_MAX_BEARER_NAME, it would check with a wrong len/TLV_GET_DATA_LEN(msg->req), which also includes priority and disc_domain length.
This patch is to fix it by checking it with a right length:
'TLV_GET_DATA_LEN(msg->req) - offsetof(struct tipc_bearer_config, name)'.
--- net/tipc/netlink_compat.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
net/tipc/netlink_compat.c +6 -1
@@ -403,7 +403,12 @@ static int tipc_nl_compat_bearer_enable(if (!bearer)return -EMSGSIZE ; - len =min_t (int,TLV_GET_DATA_LEN (msg->req),TIPC_MAX_BEARER_NAME ); + len =TLV_GET_DATA_LEN (msg->req); + len -= offsetof(struct tipc_bearer_config , name); +if (len <=0 ) +return -EINVAL ; + + len =min_t (int, len,TIPC_MAX_BEARER_NAME );if (!string_is_valid (b->name, len))return -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 61/89 net: netrom: Fix error cleanup path of nr_proto_init
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
commit d3706566ae3d92677b932dd156157fd6c72534b1 upstream.
Syzkaller report this:
BUG: unable to handle kernel paging request at fffffbfff830524b PGD 237fe8067 P4D 237fe8067 PUD 237e64067 PMD 1c9716067 PTE 0 Oops: 0000 [#1] SMP KASAN PTI CPU: 1 PID: 4465 Comm: syz-executor.0 Not tainted 5.0.0+ #5 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:__list_add_valid+0x21/0xe0 lib/list_debug.c:23 Code: 8b 0c 24 e9 17 fd ff ff 90 55 48 89 fd 48 8d 7a 08 53 48 89 d3 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 48 83 ec 08 <80> 3c 02 00 0f 85 8b 00 00 00 48 8b 53 08 48 39 f2 75 35 48 89 f2 RSP: 0018:ffff8881ea2278d0 EFLAGS: 00010282 RAX: dffffc0000000000 RBX: ffffffffc1829250 RCX: 1ffff1103d444ef4 RDX: 1ffffffff830524b RSI: ffffffff85659300 RDI: ffffffffc1829258 RBP: ffffffffc1879250 R08: fffffbfff0acb269 R09: fffffbfff0acb269 R10: ffff8881ea2278f0 R11: fffffbfff0acb268 R12: ffffffffc1829250 R13: dffffc0000000000 R14: 0000000000000008 R15: ffffffffc187c830 FS: 00007fe0361df700(0000) GS:ffff8881f7300000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffbfff830524b CR3: 00000001eb39a001 CR4: 00000000007606e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: __list_add include/linux/list.h:60 [inline] list_add include/linux/list.h:79 [inline] proto_register+0x444/0x8f0 net/core/sock.c:3375 nr_proto_init+0x73/0x4b3 [netrom] ? 0xffffffffc1628000 ? 0xffffffffc1628000 do_one_initcall+0xbc/0x47d init/main.c:887 do_init_module+0x1b5/0x547 kernel/module.c:3456 load_module+0x6405/0x8c10 kernel/module.c:3804 __do_sys_finit_module+0x162/0x190 kernel/module.c:3898 do_syscall_64+0x9f/0x450 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x462e99 Code: f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fe0361dec58 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 RAX: ffffffffffffffda RBX: 000000000073bf00 RCX: 0000000000462e99 RDX: 0000000000000000 RSI: 0000000020000100 RDI: 0000000000000003 RBP: 00007fe0361dec70 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fe0361df6bc R13: 00000000004bcefa R14: 00000000006f6fb0 R15: 0000000000000004 Modules linked in: netrom(+) ax25 fcrypt pcbc af_alg arizona_ldo1 v4l2_common videodev media v4l2_dv_timings hdlc ide_cd_mod snd_soc_sigmadsp_regmap snd_soc_sigmadsp intel_spi_platform intel_spi mtd spi_nor snd_usbmidi_lib usbcore lcd ti_ads7950 hi6421_regulator snd_soc_kbl_rt5663_max98927 snd_soc_hdac_hdmi snd_hda_ext_core snd_hda_core snd_soc_rt5663 snd_soc_core snd_pcm_dmaengine snd_compress snd_soc_rl6231 mac80211 rtc_rc5t583 spi_slave_time leds_pwm hid_gt683r hid industrialio_triggered_buffer kfifo_buf industrialio ir_kbd_i2c rc_core led_class_flash dwc_xlgmac snd_ymfpci gameport snd_mpu401_uart snd_rawmidi snd_ac97_codec snd_pcm ac97_bus snd_opl3_lib snd_timer snd_seq_device snd_hwdep snd soundcore iptable_security iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip6_vti ip_vti ip_gre ipip sit tunnel4 ip_tunnel hsr veth netdevsim vxcan batman_adv cfg80211 rfkill chnl_net caif nlmon dummy team bonding vcan bridge stp llc ip6_gre gre ip6_tunnel tunnel6 tun joydev mousedev ppdev tpm kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ide_pci_generic piix aesni_intel aes_x86_64 crypto_simd cryptd glue_helper ide_core psmouse input_leds i2c_piix4 serio_raw intel_agp intel_gtt ata_generic agpgart pata_acpi parport_pc rtc_cmos parport floppy sch_fq_codel ip_tables x_tables sha1_ssse3 sha1_generic ipv6 [last unloaded: rxrpc] Dumping ftrace buffer: (ftrace buffer empty) CR2: fffffbfff830524b ---[ end trace 039ab24b305c4b19 ]---
If nr_proto_init failed, it may forget to call proto_unregister, tiggering this issue.This patch rearrange code of nr_proto_init to avoid such issues.
--- include/net/netrom.h | 2 - net/netrom/af_netrom.c | 76 +++++++++++++++++++++++++++++------------ net/netrom/nr_loopback.c | 2 - net/netrom/nr_route.c | 2 - net/netrom/sysctl_net_netrom.c | 5 ++ 5 files changed, 61 insertions(+), 26 deletions(-)
include/net/netrom.h +1 -1
@@ -266,7 +266,7 @@ void nr_stop_idletimer(struct sock *);int nr_t1timer_running (struct sock *);/* sysctl_net_netrom.c */ -void nr_register_sysctl (void ); +int nr_register_sysctl (void );void nr_unregister_sysctl (void );#endif
net/netrom/af_netrom.c +54 -22
121 lines not on this page · raw message
net/netrom/nr_loopback.c +1 -1
@@ -70,7 +70,7 @@ static void nr_loopback_timer(struct tim } } -void __exit nr_loopback_clear(void) +void nr_loopback_clear (void ) {del_timer_sync (&loopback_timer);skb_queue_purge (&loopback_queue);
net/netrom/nr_route.c +1 -1
@@ -953,7 +953,7 @@ const struct seq_operations nr_neigh_seq/* * Free all memory associated with the nodes and routes lists. */ -void __exit nr_rt_free(void) +void nr_rt_free (void ) {struct nr_neigh *s =NULL ;struct nr_node *t =NULL ;
net/netrom/sysctl_net_netrom.c +4 -1
@@ -146,9 +146,12 @@ static struct ctl_table nr_table[] = { { } }; -void __init nr_register_sysctl (void ) +int __init nr_register_sysctl (void ) { nr_table_header =register_net_sysctl (&init_net,"net/netrom" , nr_table); +if (!nr_table_header) +return -ENOMEM ; +return 0 ; }void nr_unregister_sysctl (void )
Greg Kroah-Hartman
maintainerPATCH 63/89 rxrpc: fix race condition in rxrpc_input_packet()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
commit 032be5f19a94de51093851757089133dcc1e92aa upstream.
After commit 5271953cad31 ("rxrpc: Use the UDP encap_rcv hook"), rxrpc_input_packet() is directly called from lockless UDP receive path, under rcu_read_lock() protection.
It must therefore use RCU rules :
- udp_sk->sk_user_data can be cleared at any point in this function. rcu_dereference_sk_user_data() is what we need here.
- Also, since sk_user_data might have been set in rxrpc_open_socket() we must observe a proper RCU grace period before kfree(local) in rxrpc_lookup_local()
v4: @local can be NULL in xrpc_lookup_local() as reported by kbuild test robot <[email protected]>
and Julia Lawall <[email protected]>, thanks !
v3,v2 : addressed David Howells feedback, thanks !
syzbot reported :
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 19236 Comm: syz-executor703 Not tainted 5.1.0-rc6 #79 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__lock_acquire+0xbef/0x3fb0 kernel/locking/lockdep.c:3573 Code: 00 0f 85 a5 1f 00 00 48 81 c4 10 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 48 b8 00 00 00 00 00 fc ff df 4c 89 ea 48 c1 ea 03 <80> 3c 02 00 0f 85 4a 21 00 00 49 81 7d 00 20 54 9c 89 0f 84 cf f4 RSP: 0018:ffff88809d7aef58 EFLAGS: 00010002 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000026 RSI: 0000000000000000 RDI: 0000000000000001 RBP: ffff88809d7af090 R08: 0000000000000001 R09: 0000000000000001 R10: ffffed1015d05bc7 R11: ffff888089428600 R12: 0000000000000000 R13: 0000000000000130 R14: 0000000000000001 R15: 0000000000000001 FS: 00007f059044d700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000004b6040 CR3: 00000000955ca000 CR4: 00000000001406f0 Call Trace: lock_acquire+0x16f/0x3f0 kernel/locking/lockdep.c:4211 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x95/0xcd kernel/locking/spinlock.c:152 skb_queue_tail+0x26/0x150 net/core/skbuff.c:2972 rxrpc_reject_packet net/rxrpc/input.c:1126 [inline] rxrpc_input_packet+0x4a0/0x5536 net/rxrpc/input.c:1414 udp_queue_rcv_one_skb+0xaf2/0x1780 net/ipv4/udp.c:2011 udp_queue_rcv_skb+0x128/0x730 net/ipv4/udp.c:2085 udp_unicast_rcv_skb.isra.0+0xb9/0x360 net/ipv4/udp.c:2245 __udp4_lib_rcv+0x701/0x2ca0 net/ipv4/udp.c:2301 udp_rcv+0x22/0x30 net/ipv4/udp.c:2482 ip_protocol_deliver_rcu+0x60/0x8f0 net/ipv4/ip_input.c:208 ip_local_deliver_finish+0x23b/0x390 net/ipv4/ip_input.c:234 NF_HOOK include/linux/netfilter.h:289 [inline] NF_HOOK include/linux/netfilter.h:283 [inline] ip_local_deliver+0x1e9/0x520 net/ipv4/ip_input.c:255 dst_input include/net/dst.h:450 [inline] ip_rcv_finish+0x1e1/0x300 net/ipv4/ip_input.c:413 NF_HOOK include/linux/netfilter.h:289 [inline] NF_HOOK include/linux/netfilter.h:283 [inline] ip_rcv+0xe8/0x3f0 net/ipv4/ip_input.c:523 __netif_receive_skb_one_core+0x115/0x1a0 net/core/dev.c:4987 __netif_receive_skb+0x2c/0x1c0 net/core/dev.c:5099 netif_receive_skb_internal+0x117/0x660 net/core/dev.c:5202 napi_frags_finish net/core/dev.c:5769 [inline] napi_gro_frags+0xade/0xd10 net/core/dev.c:5843 tun_get_user+0x2f24/0x3fb0 drivers/net/tun.c:1981 tun_chr_write_iter+0xbd/0x156 drivers/net/tun.c:2027 call_write_iter include/linux/fs.h:1866 [inline] do_iter_readv_writev+0x5e1/0x8e0 fs/read_write.c:681 do_iter_write fs/read_write.c:957 [inline] do_iter_write+0x184/0x610 fs/read_write.c:938 vfs_writev+0x1b3/0x2f0 fs/read_write.c:1002 do_writev+0x15e/0x370 fs/read_write.c:1037 __do_sys_writev fs/read_write.c:1110 [inline] __se_sys_writev fs/read_write.c:1107 [inline] __x64_sys_writev+0x75/0xb0 fs/read_write.c:1107 do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe
--- net/rxrpc/input.c | 12 ++++++++---- net/rxrpc/local_object.c | 3 ++- 2 files changed, 10 insertions(+), 5 deletions(-)
net/rxrpc/input.c +8 -4
@@ -1155,19 +1155,19 @@ int rxrpc_extract_header(struct rxrpc_sk* handle data received on the local endpoint * - may be called in interrupt context * -* The socket is locked by the caller and this prevents the socket from being -* shut down and the local endpoint from going away, thus sk_user_data will not -* be cleared until this function returns. +* [!] Note that as this is called from the encap_rcv hook, the socket is not +* held locked by the caller and nothing prevents sk_user_data on the UDP from +* being cleared in the middle of processing this function. * * Called with the RCU read lock held from the IP layer via UDP. */ int rxrpc_input_packet (struct sock *udp_sk,struct sk_buff *skb) { +struct rxrpc_local *local =rcu_dereference_sk_user_data (udp_sk);struct rxrpc_connection *conn;struct rxrpc_channel *chan;struct rxrpc_call *call =NULL ;struct rxrpc_skb_priv *sp; -struct rxrpc_local *local = udp_sk->sk_user_data;struct rxrpc_peer *peer =NULL ;struct rxrpc_sock *rx =NULL ;unsigned int channel;
@@ -1175,6 +1175,10 @@ int rxrpc_input_packet(struct sock *udp__enter ("%p" , udp_sk); +if (unlikely (!local)) { +kfree_skb (skb); +return 0 ; + }if (skb->tstamp ==0 ) skb->tstamp =ktime_get_real ();
net/rxrpc/local_object.c +2 -1
@@ -304,7 +304,8 @@ nomem: ret = -ENOMEM ; sock_error:mutex_unlock (&rxnet->local_mutex); -kfree (local); +if (local) +call_rcu (&local->rcu, rxrpc_local_rcu);_leave (" = %d" , ret);return ERR_PTR (ret);
Greg Kroah-Hartman
maintainerPATCH 64/89 pin iocb through aio.
In reply to Greg Kroah-HartmanFrom: Linus Torvalds <[email protected]>
commit b53119f13a04879c3bf502828d99d13726639ead upstream.
aio_poll() is not the only case that needs file pinned; worse, while aio_read()/aio_write() can live without pinning iocb itself, the proof is rather brittle and can easily break on later changes.
--- fs/aio.c | 37 +++++++++++++++++++++---------------- 1 file changed, 21 insertions(+), 16 deletions(-)
fs/aio.c +21 -16
@@ -1022,6 +1022,9 @@ static bool get_reqs_available(struct ki/* aio_get_req * Allocate a slot for an aio request. * Returns NULL if no requests are free. +* +* The refcount is initialized to 2 - one for the async op completion, +* one for the synchronous code that does this. */ static inline struct aio_kiocb *aio_get_req (struct kioctx *ctx) {
@@ -1034,7 +1037,7 @@ static inline struct aio_kiocb *aio_get_percpu_ref_get (&ctx->reqs); req->ki_ctx = ctx;INIT_LIST_HEAD (&req->ki_list); -refcount_set (&req->ki_refcnt,0 ); +refcount_set (&req->ki_refcnt,2 ); req->ki_eventfd =NULL ;return req; }
@@ -1067,15 +1070,18 @@ out:return ret; } +static inline void iocb_destroy (struct aio_kiocb *iocb) +{ +if (iocb->ki_filp) +fput (iocb->ki_filp); +percpu_ref_put (&iocb->ki_ctx->reqs); +kmem_cache_free (kiocb_cachep, iocb); +} +static inline void iocb_put (struct aio_kiocb *iocb) { -if (refcount_read (&iocb->ki_refcnt) ==0 || -refcount_dec_and_test (&iocb->ki_refcnt)) { -if (iocb->ki_filp) -fput (iocb->ki_filp); -percpu_ref_put (&iocb->ki_ctx->reqs); -kmem_cache_free (kiocb_cachep, iocb); - } +if (refcount_dec_and_test (&iocb->ki_refcnt)) +iocb_destroy (iocb); } static void aio_fill_event(struct io_event *ev, struct aio_kiocb *iocb,
@@ -1749,9 +1755,6 @@ static ssize_t aio_poll(struct aio_kiocbINIT_LIST_HEAD (&req->wait.entry);init_waitqueue_func_entry (&req->wait, aio_poll_wake); -/* one for removal from waitqueue, one for this function */ -refcount_set (&aiocb->ki_refcnt,2 ); - mask =vfs_poll (req->file, &apt.pt) & req->events;if (unlikely (!req->head)) {/* we did not manage to set up a waitqueue, done */
@@ -1782,7 +1785,6 @@ out:if (mask)aio_poll_complete (aiocb, mask); -iocb_put (aiocb);return 0 ; }
@@ -1873,18 +1875,21 @@ static int __io_submit_one(struct kioctxbreak ; } +/* Done with the synchronous reference */ +iocb_put (req); +/* * If ret is 0, we'd either done aio_complete() ourselves or have * arranged for that to be done asynchronously. Anything non-zero * means that we need to destroy req ourselves. */ -if (ret) - goto out_put_req; -return 0 ; +if (!ret) +return 0 ; + out_put_req:if (req->ki_eventfd)eventfd_ctx_put (req->ki_eventfd); -iocb_put (req); +iocb_destroy (req); out_put_reqs_available:put_reqs_available (ctx,1 );return ret;
Greg Kroah-Hartman
maintainerPATCH 65/89 aio: fold lookup_kiocb() into its sole caller
In reply to Greg Kroah-HartmanFrom: Al Viro <[email protected]>
commit 833f4154ed560232120bc475935ee1d6a20e159f upstream.
--- fs/aio.c | 29 +++++++---------------------- 1 file changed, 7 insertions(+), 22 deletions(-)
fs/aio.c +7 -22
@@ -2002,24 +2002,6 @@ COMPAT_SYSCALL_DEFINE3(io_submit, compat }#endif -/* lookup_kiocb -* Finds a given iocb for cancellation. -*/ -static struct aio_kiocb * -lookup_kiocb (struct kioctx *ctx,struct iocb __user *iocb) -{ -struct aio_kiocb *kiocb; - -assert_spin_locked (&ctx->ctx_lock); - -/* TODO: use a hash or array, this sucks. */ -list_for_each_entry (kiocb, &ctx->active_reqs, ki_list) { -if (kiocb->ki_user_iocb == iocb) -return kiocb; - } -return NULL ; -} -/* sys_io_cancel: * Attempts to cancel an iocb previously passed to io_submit. If * the operation is successfully cancelled, the resulting event is
@@ -2048,10 +2030,13 @@ SYSCALL_DEFINE3(io_cancel, aio_context_treturn -EINVAL ;spin_lock_irq (&ctx->ctx_lock); - kiocb =lookup_kiocb (ctx, iocb); -if (kiocb) { - ret = kiocb->ki_cancel (&kiocb->rw); -list_del_init (&kiocb->ki_list); +/* TODO: use a hash or array, this sucks. */ +list_for_each_entry (kiocb, &ctx->active_reqs, ki_list) { +if (kiocb->ki_user_iocb == iocb) { + ret = kiocb->ki_cancel (&kiocb->rw); +list_del_init (&kiocb->ki_list); +break ; + } }spin_unlock_irq (&ctx->ctx_lock);
Greg Kroah-Hartman
maintainerPATCH 67/89 aio: store event at final iocb_put()
In reply to Greg Kroah-HartmanFrom: Al Viro <[email protected]>
commit 2bb874c0d873d13bd9b9b9c6d7b7c4edab18c8b4 upstream.
Instead of having aio_complete() set ->ki_res.{res,res2}, do that explicitly in its callers, drop the reference (as aio_complete() used to do) and delay the rest until the final iocb_put().
--- fs/aio.c | 33 +++++++++++++++++---------------- 1 file changed, 17 insertions(+), 16 deletions(-)
fs/aio.c +17 -16
@@ -1077,16 +1077,10 @@ static inline void iocb_destroy(struct akmem_cache_free (kiocb_cachep, iocb); } -static inline void iocb_put (struct aio_kiocb *iocb) -{ -if (refcount_dec_and_test (&iocb->ki_refcnt)) -iocb_destroy (iocb); -} -/* aio_complete * Called when the io request on the given iocb is complete. */ -static void aio_complete (struct aio_kiocb *iocb,long res,long res2) +static void aio_complete (struct aio_kiocb *iocb) {struct kioctx *ctx = iocb->ki_ctx;struct aio_ring *ring;
@@ -1094,8 +1088,6 @@ static void aio_complete(struct aio_kiocunsigned tail, pos, head;unsigned long flags; - iocb->ki_res.res = res; - iocb->ki_res.res2 = res2;/* * Add a completion event to the ring buffer. Must be done holding * ctx->completion_lock to prevent other code from messing with the tail
@@ -1161,7 +1153,14 @@ static void aio_complete(struct aio_kiocif (waitqueue_active (&ctx->wait))wake_up (&ctx->wait); -iocb_put (iocb); +} + +static inline void iocb_put (struct aio_kiocb *iocb) +{ +if (refcount_dec_and_test (&iocb->ki_refcnt)) { +aio_complete (iocb); +iocb_destroy (iocb); + } }/* aio_read_events_ring
@@ -1435,7 +1434,9 @@ static void aio_complete_rw(struct kiocbfile_end_write (kiocb->ki_filp); } -aio_complete (iocb, res, res2); + iocb->ki_res.res = res; + iocb->ki_res.res2 = res2; +iocb_put (iocb); }static int aio_prep_rw (struct kiocb *req,const struct iocb *iocb)
@@ -1583,11 +1584,10 @@ static ssize_t aio_write(struct kiocb *rstatic void aio_fsync_work (struct work_struct *work) { - struct fsync_iocb *req = container_of(work, struct fsync_iocb, work); -int ret; + struct aio_kiocb *iocb = container_of(work, struct aio_kiocb, fsync.work); - ret =vfs_fsync (req->file, req->datasync); - aio_complete(container_of(req, struct aio_kiocb, fsync), ret, 0); + iocb->ki_res.res =vfs_fsync (iocb->fsync.file, iocb->fsync.datasync); +iocb_put (iocb); } static int aio_fsync(struct fsync_iocb *req, const struct iocb *iocb,
@@ -1608,7 +1608,8 @@ static int aio_fsync(struct fsync_iocb *static inline void aio_poll_complete (struct aio_kiocb *iocb,__poll_t mask) { -aio_complete (iocb,mangle_poll (mask),0 ); + iocb->ki_res.res =mangle_poll (mask); +iocb_put (iocb); }static void aio_poll_complete_work (struct work_struct *work)
Greg Kroah-Hartman
maintainerPATCH 49/89 loop: do not print warn message if partition scan is successful
In reply to Greg Kroah-HartmanFrom: Dongli Zhang <[email protected]>
commit 40853d6fc619a6fd3d3177c3973a2eac9b598a80 upstream.
Do not print warn message when the partition scan returns 0.
--- drivers/block/loop.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/block/loop.c +3 -2
@@ -1111,8 +1111,9 @@ out_unlock: err =__blkdev_reread_part (bdev); else err =blkdev_reread_part (bdev); -pr_warn ("%s: partition scan of loop%d failed (rc=%d)\n" , - __func__, lo_number, err); +if (err) +pr_warn ("%s: partition scan of loop%d failed (rc=%d)\n" , + __func__, lo_number, err);/* Device is gone, no point in returning error */ err =0 ; }
Greg Kroah-Hartman
maintainerPATCH 69/89 x86, retpolines: Raise limit for generating indirect calls from switch-case
In reply to Greg Kroah-HartmanFrom: Daniel Borkmann <[email protected]>
commit ce02ef06fcf7a399a6276adb83f37373d10cbbe1 upstream.
Quoted 1 line
From networking side, there are numerous attempts to get rid of indirect
calls in fast-path wherever feasible in order to avoid the cost of retpolines, for example, just to name a few:
* 283c16a2dfd3 ("indirect call wrappers: helpers to speed-up indirect calls of builtin")
* aaa5d90b395a ("net: use indirect call wrappers at GRO network layer")
* 028e0a476684 ("net: use indirect call wrappers at GRO transport layer")
* 356da6d0cde3 ("dma-mapping: bypass indirect calls for dma-direct")
* 09772d92cd5a ("bpf: avoid retpoline for lookup/update/delete calls on maps")
* 10870dd89e95 ("netfilter: nf_tables: add direct calls for all builtin expressions") [...]
Recent work on XDP from Björn and Magnus additionally found that manually transforming the XDP return code switch statement with more than 5 cases into if-else combination would result in a considerable speedup in XDP layer due to avoidance of indirect calls in CONFIG_RETPOLINE enabled builds. On i40e driver with XDP prog attached, a 20-26% speedup has been observed [0]. Aside from XDP, there are many other places later in the networking stack's critical path with similar switch-case processing. Rather than fixing every XDP-enabled driver and locations in stack by hand, it would be good to instead raise the limit where gcc would emit expensive indirect calls from the switch under retpolines and stick with the default as-is in case of !retpoline configured kernels. This would also have the advantage that for archs where this is not necessary, we let compiler select the underlying target optimization for these constructs and avoid potential slow-downs by if-else hand-rewrite.
In case of gcc, this setting is controlled by case-values-threshold which has an architecture global default that selects 4 or 5 (latter if target does not have a case insn that compares the bounds) where some arch back ends like arm64 or s390 override it with their own target hooks, for example, in gcc commit db7a90aa0de5 ("S/390: Disable prediction of indirect branches") the threshold pretty much disables jump tables by limit of 20 under retpoline builds. Comparing gcc's and clang's default code generation on x86-64 under O2 level with retpoline build results in the following outcome for 5 switch cases:
* gcc with -mindirect-branch=thunk-inline -mindirect-branch-register:
# gdb -batch -ex 'disassemble dispatch' ./c-switch Dump of assembler code for function dispatch: 0x0000000000400be0 <+0>: cmp $0x4,%edi 0x0000000000400be3 <+3>: ja 0x400c35 <dispatch+85> 0x0000000000400be5 <+5>: lea 0x915f8(%rip),%rdx # 0x4921e4 0x0000000000400bec <+12>: mov %edi,%edi 0x0000000000400bee <+14>: movslq (%rdx,%rdi,4),%rax 0x0000000000400bf2 <+18>: add %rdx,%rax 0x0000000000400bf5 <+21>: callq 0x400c01 <dispatch+33> 0x0000000000400bfa <+26>: pause 0x0000000000400bfc <+28>: lfence 0x0000000000400bff <+31>: jmp 0x400bfa <dispatch+26> 0x0000000000400c01 <+33>: mov %rax,(%rsp) 0x0000000000400c05 <+37>: retq 0x0000000000400c06 <+38>: nopw %cs:0x0(%rax,%rax,1) 0x0000000000400c10 <+48>: jmpq 0x400c90 <fn_3> 0x0000000000400c15 <+53>: nopl (%rax) 0x0000000000400c18 <+56>: jmpq 0x400c70 <fn_2> 0x0000000000400c1d <+61>: nopl (%rax) 0x0000000000400c20 <+64>: jmpq 0x400c50 <fn_1> 0x0000000000400c25 <+69>: nopl (%rax) 0x0000000000400c28 <+72>: jmpq 0x400c40 <fn_0> 0x0000000000400c2d <+77>: nopl (%rax) 0x0000000000400c30 <+80>: jmpq 0x400cb0 <fn_4> 0x0000000000400c35 <+85>: push %rax 0x0000000000400c36 <+86>: callq 0x40dd80 <abort> End of assembler dump.
* clang with -mretpoline emitting search tree:
# gdb -batch -ex 'disassemble dispatch' ./c-switch Dump of assembler code for function dispatch: 0x0000000000400b30 <+0>: cmp $0x1,%edi 0x0000000000400b33 <+3>: jle 0x400b44 <dispatch+20> 0x0000000000400b35 <+5>: cmp $0x2,%edi 0x0000000000400b38 <+8>: je 0x400b4d <dispatch+29> 0x0000000000400b3a <+10>: cmp $0x3,%edi 0x0000000000400b3d <+13>: jne 0x400b52 <dispatch+34> 0x0000000000400b3f <+15>: jmpq 0x400c50 <fn_3> 0x0000000000400b44 <+20>: test %edi,%edi 0x0000000000400b46 <+22>: jne 0x400b5c <dispatch+44> 0x0000000000400b48 <+24>: jmpq 0x400c20 <fn_0> 0x0000000000400b4d <+29>: jmpq 0x400c40 <fn_2> 0x0000000000400b52 <+34>: cmp $0x4,%edi 0x0000000000400b55 <+37>: jne 0x400b66 <dispatch+54> 0x0000000000400b57 <+39>: jmpq 0x400c60 <fn_4> 0x0000000000400b5c <+44>: cmp $0x1,%edi 0x0000000000400b5f <+47>: jne 0x400b66 <dispatch+54> 0x0000000000400b61 <+49>: jmpq 0x400c30 <fn_1> 0x0000000000400b66 <+54>: push %rax 0x0000000000400b67 <+55>: callq 0x40dd20 <abort> End of assembler dump.
For sake of comparison, clang without -mretpoline:
# gdb -batch -ex 'disassemble dispatch' ./c-switch Dump of assembler code for function dispatch: 0x0000000000400b30 <+0>: cmp $0x4,%edi 0x0000000000400b33 <+3>: ja 0x400b57 <dispatch+39> 0x0000000000400b35 <+5>: mov %edi,%eax 0x0000000000400b37 <+7>: jmpq *0x492148(,%rax,8) 0x0000000000400b3e <+14>: jmpq 0x400bf0 <fn_0> 0x0000000000400b43 <+19>: jmpq 0x400c30 <fn_4> 0x0000000000400b48 <+24>: jmpq 0x400c10 <fn_2> 0x0000000000400b4d <+29>: jmpq 0x400c20 <fn_3> 0x0000000000400b52 <+34>: jmpq 0x400c00 <fn_1> 0x0000000000400b57 <+39>: push %rax 0x0000000000400b58 <+40>: callq 0x40dcf0 <abort> End of assembler dump.
Raising the cases to a high number (e.g. 100) will still result in similar code generation pattern with clang and gcc as above, in other words clang generally turns off jump table emission by having an extra expansion pass under retpoline build to turn indirectbr instructions from their IR into switch instructions as a built-in -mno-jump-table lowering of a switch (in this case, even if IR input already contained an indirect branch).
For gcc, adding --param=case-values-threshold=20 as in similar fashion as s390 in order to raise the limit for x86 retpoline enabled builds results in a small vmlinux size increase of only 0.13% (before=18,027,528 after=18,051,192). For clang this option is ignored due to i) not being needed as mentioned and ii) not having above cmdline parameter. Non-retpoline-enabled builds with gcc continue to use the default case-values-threshold setting, so nothing changes here.
[0] https://lore.kernel.org/netdev/[email protected]/
and "The Path to DPDK Speeds for AF_XDP", LPC 2018, networking track:
- http://vger.kernel.org/lpc_net2018_talks/lpc18_pres_af_xdp_perf-v3.pdf
- http://vger.kernel.org/lpc_net2018_talks/lpc18_paper_af_xdp_perf-v2.pdf
--- arch/x86/Makefile | 5 +++++ 1 file changed, 5 insertions(+)
arch/x86/Makefile +5 -0
@@ -217,6 +217,11 @@ KBUILD_CFLAGS += -fno-asynchronous-unwin # Avoid indirect branches in kernel to deal with Spectre ifdef CONFIG_RETPOLINE KBUILD_CFLAGS += $(RETPOLINE_CFLAGS) + # Additionally, avoid generating expensive indirect jumps which + # are subject to retpolines for small number of switch cases. + # clang turns off jump table generation by default when under + # retpoline builds, however, gcc does not for x86. + KBUILD_CFLAGS += $(call cc-option,--param=case-values-threshold=20) endif archscripts: scripts_basic
Greg Kroah-Hartman
maintainerPATCH 70/89 x86/retpolines: Disable switch jump tables when retpolines are enabled
In reply to Greg Kroah-HartmanFrom: Daniel Borkmann <[email protected]>
commit a9d57ef15cbe327fe54416dd194ee0ea66ae53a4 upstream.
Commit ce02ef06fcf7 ("x86, retpolines: Raise limit for generating indirect calls from switch-case") raised the limit under retpolines to 20 switch cases where gcc would only then start to emit jump tables, and therefore effectively disabling the emission of slow indirect calls in this area.
After this has been brought to attention to gcc folks [0], Martin Liska has then fixed gcc to align with clang by avoiding to generate switch jump tables entirely under retpolines. This is taking effect in gcc starting from stable version 8.4.0. Given kernel supports compilation with older versions of gcc where the fix is not being available or backported anymore, we need to keep the extra KBUILD_CFLAGS around for some time and generally set the -fno-jump-tables to align with what more recent gcc is doing automatically today.
More than 20 switch cases are not expected to be fast-path critical, but it would still be good to align with gcc behavior for versions < 8.4.0 in order to have consistency across supported gcc versions. vmlinux size is slightly growing by 0.27% for older gcc. This flag is only set to work around affected gcc, no change for clang.
[0] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86952
--- arch/x86/Makefile | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
arch/x86/Makefile +6 -2
@@ -220,8 +220,12 @@ ifdef CONFIG_RETPOLINE # Additionally, avoid generating expensive indirect jumps which # are subject to retpolines for small number of switch cases. # clang turns off jump table generation by default when under - # retpoline builds, however, gcc does not for x86. - KBUILD_CFLAGS += $(call cc-option,--param=case-values-threshold=20) + # retpoline builds, however, gcc does not for x86. This has + # only been fixed starting from gcc stable version 8.4.0 and + # onwards, but not for older ones. See gcc bug #86952. + ifndef CONFIG_CC_IS_CLANG + KBUILD_CFLAGS += $(call cc-option,-fno-jump-tables) + endif endif archscripts: scripts_basic
Greg Kroah-Hartman
maintainerPATCH 71/89 rdma: fix build errors on s390 and MIPS due to bad ZERO_PAGE use
In reply to Greg Kroah-HartmanFrom: Linus Torvalds <[email protected]>
commit 6a5c5d26c4c6c3cc486fef0bf04ff9551132611b upstream.
The parameter to ZERO_PAGE() was wrong, but since all architectures except for MIPS and s390 ignore it, it wasn't noticed until 0-day reported the build error.
--- drivers/infiniband/core/uverbs_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/infiniband/core/uverbs_main.c +1 -1
@@ -894,7 +894,7 @@ static vm_fault_t rdma_umap_fault(struct/* Read only pages can just use the system zero page. */ if (!(vmf->vma->vm_flags & (VM_WRITE |VM_MAYWRITE ))) { - vmf->page =ZERO_PAGE (vmf->vm_start); + vmf->page =ZERO_PAGE (vmf->address);get_page (vmf->page);return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 72/89 ipv4: add sanity checks in ipv4_link_failure()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit 20ff83f10f113c88d0bb74589389b05250994c16 ]
Before calling __ip_options_compile(), we need to ensure the network header is a an IPv4 one, and that it is already pulled in skb->head.
RAW sockets going through a tunnel can end up calling ipv4_link_failure() with total garbage in the skb, or arbitrary lengthes.
syzbot report :
BUG: KASAN: stack-out-of-bounds in memcpy include/linux/string.h:355 [inline]
BUG: KASAN: stack-out-of-bounds in __ip_options_echo+0x294/0x1120 net/ipv4/ip_options.c:123
Write of size 69 at addr ffff888096abf068 by task syz-executor.4/9204
CPU: 0 PID: 9204 Comm: syz-executor.4 Not tainted 5.1.0-rc5+ #77
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
print_address_description.cold+0x7c/0x20d mm/kasan/report.c:187
kasan_report.cold+0x1b/0x40 mm/kasan/report.c:317
check_memory_region_inline mm/kasan/generic.c:185 [inline]
check_memory_region+0x123/0x190 mm/kasan/generic.c:191
memcpy+0x38/0x50 mm/kasan/common.c:133
memcpy include/linux/string.h:355 [inline]
__ip_options_echo+0x294/0x1120 net/ipv4/ip_options.c:123
__icmp_send+0x725/0x1400 net/ipv4/icmp.c:695
ipv4_link_failure+0x29f/0x550 net/ipv4/route.c:1204
dst_link_failure include/net/dst.h:427 [inline]
vti6_xmit net/ipv6/ip6_vti.c:514 [inline]
vti6_tnl_xmit+0x10d4/0x1c0c net/ipv6/ip6_vti.c:553
__netdev_start_xmit include/linux/netdevice.h:4414 [inline]
netdev_start_xmit include/linux/netdevice.h:4423 [inline]
xmit_one net/core/dev.c:3292 [inline]
dev_hard_start_xmit+0x1b2/0x980 net/core/dev.c:3308
__dev_queue_xmit+0x271d/0x3060 net/core/dev.c:3878
dev_queue_xmit+0x18/0x20 net/core/dev.c:3911
neigh_direct_output+0x16/0x20 net/core/neighbour.c:1527
neigh_output include/net/neighbour.h:508 [inline]
ip_finish_output2+0x949/0x1740 net/ipv4/ip_output.c:229
ip_finish_output+0x73c/0xd50 net/ipv4/ip_output.c:317
NF_HOOK_COND include/linux/netfilter.h:278 [inline]
ip_output+0x21f/0x670 net/ipv4/ip_output.c:405
dst_output include/net/dst.h:444 [inline]
NF_HOOK include/linux/netfilter.h:289 [inline]
raw_send_hdrinc net/ipv4/raw.c:432 [inline]
raw_sendmsg+0x1d2b/0x2f20 net/ipv4/raw.c:663
inet_sendmsg+0x147/0x5d0 net/ipv4/af_inet.c:798
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xdd/0x130 net/socket.c:661
sock_write_iter+0x27c/0x3e0 net/socket.c:988
call_write_iter include/linux/fs.h:1866 [inline]
new_sync_write+0x4c7/0x760 fs/read_write.c:474
__vfs_write+0xe4/0x110 fs/read_write.c:487
vfs_write+0x20c/0x580 fs/read_write.c:549
ksys_write+0x14f/0x2d0 fs/read_write.c:599
__do_sys_write fs/read_write.c:611 [inline]
__se_sys_write fs/read_write.c:608 [inline]
__x64_sys_write+0x73/0xb0 fs/read_write.c:608
do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x458c29
Code: ad b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 7b b8 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f293b44bc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000458c29
RDX: 0000000000000014 RSI: 00000000200002c0 RDI: 0000000000000003
RBP: 000000000073bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f293b44c6d4
R13: 00000000004c8623 R14: 00000000004ded68 R15: 00000000ffffffff
The buggy address belongs to the page:
page:ffffea00025aafc0 count:0 mapcount:0 mapping:0000000000000000 index:0x0
flags: 0x1fffc0000000000()
raw: 01fffc0000000000 0000000000000000 ffffffff025a0101 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff888096abef80: 00 00 00 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 f2
ffff888096abf000: f2 f2 f2 f2 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888096abf080: 00 00 f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00
^
ffff888096abf100: 00 00 00 00 f1 f1 f1 f1 00 00 f3 f3 00 00 00 00
ffff888096abf180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00--- net/ipv4/route.c | 34 ++++++++++++++++++++++++---------- 1 file changed, 24 insertions(+), 10 deletions(-)
net/ipv4/route.c +24 -10
@@ -1183,25 +1183,39 @@ static struct dst_entry *ipv4_dst_check(return dst; } -static void ipv4_link_failure (struct sk_buff *skb) +static void ipv4_send_dest_unreach (struct sk_buff *skb) {struct ip_options opt; -struct rtable *rt;int res;/* Recompile ip options since IPCB may not be valid anymore. +* Also check we have a reasonable ipv4 header. */ -memset (&opt,0 ,sizeof (opt)); - opt.optlen =ip_hdr (skb)->ihl*4 -sizeof (struct iphdr ); - -rcu_read_lock (); - res =__ip_options_compile (dev_net (skb->dev), &opt, skb,NULL ); -rcu_read_unlock (); - -if (res) +if (!pskb_network_may_pull (skb,sizeof (struct iphdr )) || +ip_hdr (skb)->version !=4 ||ip_hdr (skb)->ihl <5 )return ; +memset (&opt,0 ,sizeof (opt)); +if (ip_hdr (skb)->ihl >5 ) { +if (!pskb_network_may_pull (skb,ip_hdr (skb)->ihl *4 )) +return ; + opt.optlen =ip_hdr (skb)->ihl *4 -sizeof (struct iphdr ); + +rcu_read_lock (); + res =__ip_options_compile (dev_net (skb->dev), &opt, skb,NULL ); +rcu_read_unlock (); + +if (res) +return ; + }__icmp_send (skb,ICMP_DEST_UNREACH ,ICMP_HOST_UNREACH ,0 , &opt); +} + +static void ipv4_link_failure (struct sk_buff *skb) +{ +struct rtable *rt; + +ipv4_send_dest_unreach (skb); rt =skb_rtable (skb);if (rt)
Greg Kroah-Hartman
maintainerPATCH 74/89 mlxsw: spectrum: Fix autoneg status in ethtool
In reply to Greg Kroah-HartmanFrom: Amit Cohen <[email protected]>
[ Upstream commit 151f0dddbbfe4c35c9c5b64873115aafd436af9d ]
If link is down and autoneg is set to on/off, the status in ethtool does not change.
The reason is when the link is down the function returns with zero before changing autoneg value.
Move the checking of link state (up/down) to be performed after setting autoneg value, in order to be sure that autoneg will change in any case.
--- drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/mellanox/mlxsw/spectrum.c +2 -2
@@ -2667,11 +2667,11 @@ mlxsw_sp_port_set_link_ksettings(structif (err)return err; + mlxsw_sp_port->link.autoneg = autoneg; +if (!netif_running (dev))return 0 ; - mlxsw_sp_port->link.autoneg = autoneg; -mlxsw_sp_port_admin_status_set (mlxsw_sp_port, false);mlxsw_sp_port_admin_status_set (mlxsw_sp_port, true);
Greg Kroah-Hartman
maintainerPATCH 75/89 net/mlx5e: ethtool, Remove unsupported SFP EEPROM high pages query
In reply to Greg Kroah-HartmanFrom: Erez Alfasi <[email protected]>
[ Upstream commit ace329f4ab3ba434be2adf618073c752d083b524 ]
Querying EEPROM high pages data for SFP module is currently not supported by our driver and yet queried, resulting in invalid FW queries.
Set the EEPROM ethtool data length to 256 for SFP module will limit the reading for page 0 only and prevent invalid FW queries.
--- drivers/net/ethernet/mellanox/mlx5/core/en_ethtool.c | 2 +- drivers/net/ethernet/mellanox/mlx5/core/port.c | 4 ---- 2 files changed, 1 insertion(+), 5 deletions(-)
drivers/net/ethernet/mellanox/mlx5/core/en_ethtool.c +1 -1
@@ -1470,7 +1470,7 @@ static int mlx5e_get_module_info(structbreak ;case MLX5_MODULE_ID_SFP : modinfo->type =ETH_MODULE_SFF_8472 ; - modinfo->eeprom_len =ETH_MODULE_SFF_8472_LEN ; + modinfo->eeprom_len =MLX5_EEPROM_PAGE_LENGTH ;break ;default : netdev_err(priv->netdev, "%s: cable type not recognized:0x%x\n",
drivers/net/ethernet/mellanox/mlx5/core/port.c +0 -4
@@ -404,10 +404,6 @@ int mlx5_query_module_eeprom(struct mlx5 size -= offset + size -MLX5_EEPROM_PAGE_LENGTH ; i2c_addr =MLX5_I2C_ADDR_LOW ; -if (offset >=MLX5_EEPROM_PAGE_LENGTH ) { - i2c_addr =MLX5_I2C_ADDR_HIGH ; - offset -=MLX5_EEPROM_PAGE_LENGTH ; - }MLX5_SET (mcia_reg, in, l,0 );MLX5_SET (mcia_reg, in, module, module_num);
Greg Kroah-Hartman
maintainerPATCH 76/89 net: rds: exchange of 8K and 1M pool
In reply to Greg Kroah-HartmanFrom: Zhu Yanjun <[email protected]>
[ Upstream commit 4b9fc7146249a6e0e3175d0acc033fdcd2bfcb17 ]
Before the commit 490ea5967b0d ("RDS: IB: move FMR code to its own file"), when the dirty_count is greater than 9/10 of max_items of 8K pool, 1M pool is used, Vice versa. After the commit 490ea5967b0d ("RDS: IB: move FMR code to its own file"), the above is removed. When we make the following tests.
Server:
rds-stress -r 1.1.1.16 -D 1M
Client:
rds-stress -r 1.1.1.14 -s 1.1.1.16 -D 1M
The following will appear.
"
connecting to 1.1.1.16:4000
negotiated options, tasks will start in 2 seconds Starting up..header from 1.1.1.166:4001 to id 4001 bogus ..
tsks tx/s rx/s tx+rx K/s mbi K/s mbo K/s tx us/c rtt us cpu %
1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00
...
"
So this exchange between 8K and 1M pool is added back.
--- net/rds/ib_fmr.c | 11 +++++++++++ net/rds/ib_rdma.c | 3 --- 2 files changed, 11 insertions(+), 3 deletions(-)
net/rds/ib_fmr.c +11 -0
@@ -44,6 +44,17 @@ struct rds_ib_mr *rds_ib_alloc_fmr(strucelse pool = rds_ibdev->mr_1m_pool; +if (atomic_read (&pool->dirty_count) >= pool->max_items /10 ) +queue_delayed_work (rds_ib_mr_wq, &pool->flush_worker,10 ); + +/* Switch pools if one of the pool is reaching upper limit */ +if (atomic_read (&pool->dirty_count) >= pool->max_items *9 /10 ) { +if (pool->pool_type ==RDS_IB_MR_8K_POOL ) + pool = rds_ibdev->mr_1m_pool; +else + pool = rds_ibdev->mr_8k_pool; + } + ibmr =rds_ib_try_reuse_ibmr (pool);if (ibmr)return ibmr;
net/rds/ib_rdma.c +0 -3
@@ -454,9 +454,6 @@ struct rds_ib_mr *rds_ib_try_reuse_ibmr(struct rds_ib_mr *ibmr =NULL ;int iter =0 ; -if (atomic_read (&pool->dirty_count) >= pool->max_items_soft /10 ) -queue_delayed_work (rds_ib_mr_wq, &pool->flush_worker,10 ); -while (1 ) { ibmr =rds_ib_reuse_mr (pool);if (ibmr)
Greg Kroah-Hartman
maintainerPATCH 50/89 tipc: handle the err returned from cmd header function
In reply to Greg Kroah-HartmanFrom: Xin Long <[email protected]>
commit 2ac695d1d602ce00b12170242f58c3d3a8e36d04 upstream.
Syzbot found a crash:
BUG: KMSAN: uninit-value in tipc_nl_compat_name_table_dump+0x54f/0xcd0 net/tipc/netlink_compat.c:872
Call Trace:
tipc_nl_compat_name_table_dump+0x54f/0xcd0 net/tipc/netlink_compat.c:872
__tipc_nl_compat_dumpit+0x59e/0xda0 net/tipc/netlink_compat.c:215
tipc_nl_compat_dumpit+0x63a/0x820 net/tipc/netlink_compat.c:280
tipc_nl_compat_handle net/tipc/netlink_compat.c:1226 [inline]
tipc_nl_compat_recv+0x1b5f/0x2750 net/tipc/netlink_compat.c:1265
genl_family_rcv_msg net/netlink/genetlink.c:601 [inline]
genl_rcv_msg+0x185f/0x1a60 net/netlink/genetlink.c:626
netlink_rcv_skb+0x431/0x620 net/netlink/af_netlink.c:2477
genl_rcv+0x63/0x80 net/netlink/genetlink.c:637
netlink_unicast_kernel net/netlink/af_netlink.c:1310 [inline]
netlink_unicast+0xf3e/0x1020 net/netlink/af_netlink.c:1336
netlink_sendmsg+0x127f/0x1300 net/netlink/af_netlink.c:1917
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg net/socket.c:632 [inline]Uninit was created at:
__alloc_skb+0x309/0xa20 net/core/skbuff.c:208
alloc_skb include/linux/skbuff.h:1012 [inline]
netlink_alloc_large_skb net/netlink/af_netlink.c:1182 [inline]
netlink_sendmsg+0xb82/0x1300 net/netlink/af_netlink.c:1892
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg net/socket.c:632 [inline]It was supposed to be fixed on commit 974cb0e3e7c9 ("tipc: fix uninit-value in tipc_nl_compat_name_table_dump") by checking TLV_GET_DATA_LEN(msg->req) in cmd->header()/tipc_nl_compat_name_table_dump_header(), which is called ahead of tipc_nl_compat_name_table_dump().
However, tipc_nl_compat_dumpit() doesn't handle the error returned from cmd header function. It means even when the check added in that fix fails, it won't stop calling tipc_nl_compat_name_table_dump(), and the issue will be triggered again.
So this patch is to add the process for the err returned from cmd header function in tipc_nl_compat_dumpit().
--- net/tipc/netlink_compat.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
net/tipc/netlink_compat.c +8 -2
@@ -267,8 +267,14 @@ static int tipc_nl_compat_dumpit(structif (msg->rep_type)tipc_tlv_init (msg->rep, msg->rep_type); -if (cmd->header) - (*cmd->header)(msg); +if (cmd->header) { + err = (*cmd->header)(msg); +if (err) { +kfree_skb (msg->rep); + msg->rep =NULL ; +return err; + } + } arg =nlmsg_new (0 ,GFP_KERNEL );if (!arg) {
Greg Kroah-Hartman
maintainerPATCH 79/89 net/tls: fix refcount adjustment in fallback
In reply to Greg Kroah-HartmanFrom: Jakub Kicinski <[email protected]>
[ Upstream commit 9188d5ca454fd665145904267e726e9e8d122f5c ]
Unlike atomic_add(), refcount_add() does not deal well with a negative argument. TLS fallback code reallocates the skb and is very likely to shrink the truesize, leading to:
[ 189.513254] WARNING: CPU: 5 PID: 0 at lib/refcount.c:81 refcount_add_not_zero_checked+0x15c/0x180 Call Trace: refcount_add_checked+0x6/0x40 tls_enc_skb+0xb93/0x13e0 [tls]
Once wmem_allocated count saturates the application can no longer send data on the socket. This is similar to Eric's fixes for GSO, TCP:
commit 7ec318feeed1 ("tcp: gso: avoid refcount_t warning from tcp_gso_segment()") and UDP:
commit 575b65bc5bff ("udp: avoid refcount_t saturation in __udp_gso_segment()").
Unlike the GSO case, for TLS fallback it's likely that the skb has shrunk, so the "likely" annotation is the other way around (likely branch being "sub").
--- net/tls/tls_device_fallback.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
net/tls/tls_device_fallback.c +10 -3
@@ -193,6 +193,9 @@ static void update_chksum(struct sk_buffstatic void complete_skb (struct sk_buff *nskb,struct sk_buff *skb,int headln) { +struct sock *sk = skb->sk; +int delta; +skb_copy_header (nskb, skb);skb_put (nskb, skb->len);
@@ -200,11 +203,15 @@ static void complete_skb(struct sk_buffupdate_chksum (nskb, headln); nskb->destructor = skb->destructor; - nskb->sk = skb->sk; + nskb->sk = sk; skb->destructor =NULL ; skb->sk =NULL ; -refcount_add (nskb->truesize - skb->truesize, - &nskb->sk->sk_wmem_alloc); + + delta = nskb->truesize - skb->truesize; +if (likely (delta <0 )) +WARN_ON_ONCE (refcount_sub_and_test (-delta, &sk->sk_wmem_alloc)); +else if (delta) +refcount_add (delta, &sk->sk_wmem_alloc); }/* This function may be called after the user socket is already
Greg Kroah-Hartman
maintainerPATCH 80/89 stmmac: pci: Adjust IOT2000 matching
In reply to Greg Kroah-HartmanFrom: Su Bao Cheng <[email protected]>
[ Upstream commit e0c1d14a1a3211dccf0540a6703ffbd5d2a75bdb ]
Since there are more IOT2040 variants with identical hardware but different asset tags, the asset tag matching should be adjusted to support them.
For the board name "SIMATIC IOT2000", currently there are 2 types of hardware, IOT2020 and IOT2040. The IOT2020 is identified by its unique asset tag. Match on it first. If we then match on the board name only, we will catch all IOT2040 variants. In the future there will be no other devices with the "SIMATIC IOT2000" DMI board name but different hardware.
--- drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c +6 -2
@@ -159,6 +159,12 @@ static const struct dmi_system_id quark_ }, .driver_data = (void *)&galileo_stmmac_dmi_data, }, +/* +* There are 2 types of SIMATIC IOT2000: IOT20202 and IOT2040. +* The asset tag "6ES7647-0AA00-0YA2" is only for IOT2020 which +* has only one pci network device while other asset tags are +* for IOT2040 which has two. +*/ { .matches = { DMI_EXACT_MATCH(DMI_BOARD_NAME, "SIMATIC IOT2000"),
@@ -170,8 +176,6 @@ static const struct dmi_system_id quark_ { .matches = { DMI_EXACT_MATCH(DMI_BOARD_NAME, "SIMATIC IOT2000"), - DMI_EXACT_MATCH(DMI_BOARD_ASSET_TAG, - "6ES7647-0AA00-1YA2"), }, .driver_data = (void *)&iot2040_stmmac_dmi_data, },
Greg Kroah-Hartman
maintainerPATCH 81/89 team: fix possible recursive locking when add slaves
In reply to Greg Kroah-HartmanFrom: Hangbin Liu <[email protected]>
[ Upstream commit 925b0c841e066b488cc3a60272472b2c56300704 ]
If we add a bond device which is already the master of the team interface, we will hold the team->lock in team_add_slave() first and then request the lock in team_set_mac_address() again. The functions are called like:
- team_add_slave()
- team_port_add()
- team_port_enter()
- team_modeop_port_enter()
- __set_port_dev_addr()
- dev_set_mac_address()
- bond_set_mac_address()
- dev_set_mac_address()
- team_set_mac_address
Although team_upper_dev_link() would check the upper devices but it is called too late. Fix it by adding a checking before processing the slave.
v2: Do not split the string in netdev_err()
--- drivers/net/team/team.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/net/team/team.c +7 -0
@@ -1157,6 +1157,13 @@ static int team_port_add(struct team *tereturn -EINVAL ; } +if (netdev_has_upper_dev (dev, port_dev)) { +NL_SET_ERR_MSG (extack,"Device is already an upper device of the team interface" ); +netdev_err (dev,"Device %s is already an upper device of the team interface\n" , + portname); +return -EBUSY ; + } +if (port_dev->features &NETIF_F_VLAN_CHALLENGED &&vlan_uses_dev (dev)) {NL_SET_ERR_MSG (extack,"Device is VLAN challenged and team device has VLAN set up" );
Greg Kroah-Hartman
maintainerPATCH 83/89 net/ncsi: handle overflow when incrementing mac address
In reply to Greg Kroah-HartmanFrom: Tao Ren <[email protected]>
[ Upstream commit 1c5c12ee308aacf635c8819cd4baa3bd58f8a8b7 ]
Previously BMC's MAC address is calculated by simply adding 1 to the last byte of network controller's MAC address, and it produces incorrect result when network controller's MAC address ends with 0xFF.
The problem can be fixed by calling eth_addr_inc() function to increment MAC address; besides, the MAC address is also validated before assigning to BMC.
--- include/linux/etherdevice.h | 12 ++++++++++++ net/ncsi/ncsi-rsp.c | 6 +++++- 2 files changed, 17 insertions(+), 1 deletion(-)
include/linux/etherdevice.h +12 -0
@@ -448,6 +448,18 @@ static inline void eth_addr_dec(u8 *addr }/** +* eth_addr_inc() - Increment the given MAC address. +* @addr: Pointer to a six-byte array containing Ethernet address to increment. +*/ +static inline void eth_addr_inc (u8 *addr) +{ +u64 u =ether_addr_to_u64 (addr); + + u++; +u64_to_ether_addr (u, addr); +} + +/** * is_etherdev_addr - Tell if given Ethernet address belongs to the device. * @dev: Pointer to a device structure * @addr: Pointer to a six-byte array containing the Ethernet address
net/ncsi/ncsi-rsp.c +5 -1
@@ -11,6 +11,7 @@#include <linux/kernel.h> #include <linux/init.h> #include <linux/netdevice.h> +#include <linux/etherdevice.h> #include <linux/skbuff.h> #include <net/ncsi.h>
@@ -667,7 +668,10 @@ static int ncsi_rsp_handler_oem_bcm_gma( ndev->priv_flags |=IFF_LIVE_ADDR_CHANGE ;memcpy (saddr.sa_data, &rsp->data[BCM_MAC_ADDR_OFFSET ],ETH_ALEN );/* Increase mac address by 1 for BMC's address */ - saddr.sa_data[ETH_ALEN -1 ]++; +eth_addr_inc ((u8 *)saddr.sa_data); +if (!is_valid_ether_addr ((const u8 *)saddr.sa_data)) +return -ENXIO ; + ret = ops->ndo_set_mac_address (ndev, &saddr);if (ret <0 )netdev_warn (ndev,"NCSI: 'Writing mac address to device failed\n" );
Greg Kroah-Hartman
maintainerPATCH 51/89 slip: make slhc_free() silently accept an error pointer
In reply to Greg Kroah-HartmanFrom: Linus Torvalds <[email protected]>
commit baf76f0c58aec435a3a864075b8f6d8ee5d1f17e upstream.
This way, slhc_free() accepts what slhc_init() returns, whether that is an error or not.
In particular, the pattern in sl_alloc_bufs() is
slcomp = slhc_init(16, 16);
...
slhc_free(slcomp);for the error handling path, and rather than complicate that code, just make it ok to always free what was returned by the init function.
That's what the code used to do before commit 4ab42d78e37a ("ppp, slip:
Validate VJ compression slot parameters completely") when slhc_init() just returned NULL for the error case, with no actual indication of the details of the error.
--- drivers/net/slip/slhc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/slip/slhc.c +1 -1
@@ -153,7 +153,7 @@ out_fail:void slhc_free (struct slcompress *comp) { -if ( comp ==NULLSLCOMPR ) +if (IS_ERR_OR_NULL (comp) )return ;if ( comp->tstate !=NULLSLSTATE )
Greg Kroah-Hartman
maintainerPATCH 53/89 binder: fix handling of misaligned binder object
In reply to Greg Kroah-HartmanFrom: Todd Kjos <[email protected]>
commit 26528be6720bb40bc8844e97ee73a37e530e9c5e upstream.
Fixes crash found by syzbot:
kernel BUG at drivers/android/binder_alloc.c:LINE! (2)
--- drivers/android/binder_alloc.c | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-)
drivers/android/binder_alloc.c +8 -10
@@ -959,14 +959,13 @@ enum lru_status binder_alloc_free_page(s index = page - alloc->pages; page_addr = (uintptr_t )alloc->buffer + index *PAGE_SIZE ; + + mm = alloc->vma_vm_mm; +if (!mmget_not_zero (mm)) + goto err_mmget; +if (!down_write_trylock (&mm->mmap_sem)) + goto err_down_write_mmap_sem_failed; vma =binder_alloc_get_vma (alloc); -if (vma) { -if (!mmget_not_zero (alloc->vma_vm_mm)) - goto err_mmget; - mm = alloc->vma_vm_mm; -if (!down_write_trylock (&mm->mmap_sem)) - goto err_down_write_mmap_sem_failed; - }list_lru_isolate (lru, item);spin_unlock (lock);
@@ -979,10 +978,9 @@ enum lru_status binder_alloc_free_page(s PAGE_SIZE);trace_binder_unmap_user_end (alloc, index); - -up_write (&mm->mmap_sem); -mmput (mm); } +up_write (&mm->mmap_sem); +mmput (mm);trace_binder_unmap_kernel_start (alloc, index);
Greg Kroah-Hartman
maintainerPATCH 55/89 mac80211_hwsim: calculate if_combination.max_interfaces
In reply to Greg Kroah-HartmanFrom: Johannes Berg <[email protected]>
commit 45fcef8b727b6f171bc5443e8153181a367d7a15 upstream.
If we just set this to 2048, and have multiple limits you can select from, the total number might run over and cause a warning in cfg80211. This doesn't make sense, so we just calculate the total max_interfaces now.
--- drivers/net/wireless/mac80211_hwsim.c | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-)
drivers/net/wireless/mac80211_hwsim.c +15 -4
@@ -2642,7 +2642,7 @@ static int mac80211_hwsim_new_radio(struenum nl80211_band band;const struct ieee80211_ops *ops = &mac80211_hwsim_ops;struct net *net; -int idx; +int idx, i;int n_limits =0 ;if (WARN_ON (param->channels >1 && !param->use_chanctx))
@@ -2766,12 +2766,23 @@ static int mac80211_hwsim_new_radio(stru goto failed_hw; } + data->if_combination.max_interfaces =0 ; +for (i =0 ; i < n_limits; i++) + data->if_combination.max_interfaces += + data->if_limits[i].max; + data->if_combination.n_limits = n_limits; - data->if_combination.max_interfaces =2048 ; data->if_combination.limits = data->if_limits; - hw->wiphy->iface_combinations = &data->if_combination; - hw->wiphy->n_iface_combinations =1 ; +/* +* If we actually were asked to support combinations, +* advertise them - if there's only a single thing like +* only IBSS then don't advertise it as combinations. +*/ +if (data->if_combination.max_interfaces >1 ) { + hw->wiphy->iface_combinations = &data->if_combination; + hw->wiphy->n_iface_combinations =1 ; + }if (param->ciphers) { memcpy(data->ciphers, param->ciphers,
Greg Kroah-Hartman
maintainerPATCH 56/89 NFS: Forbid setting AF_INET6 to "struct sockaddr_in"->sin_family.
In reply to Greg Kroah-HartmanFrom: Tetsuo Handa <[email protected]>
commit 7c2bd9a39845bfb6d72ddb55ce737650271f6f96 upstream.
syzbot is reporting uninitialized value at rpc_sockaddr2uaddr() [1]. This is because syzbot is setting AF_INET6 to "struct sockaddr_in"->sin_family (which is embedded into user-visible "struct nfs_mount_data" structure) despite nfs23_validate_mount_data() cannot pass sizeof(struct sockaddr_in6) bytes of AF_INET6 address to rpc_sockaddr2uaddr().
Since "struct nfs_mount_data" structure is user-visible, we can't change "struct nfs_mount_data" to use "struct sockaddr_storage". Therefore, assuming that everybody is using AF_INET family when passing address via "struct nfs_mount_data"->addr, reject if its sin_family is not AF_INET.
[1] https://syzkaller.appspot.com/bug?id=599993614e7cbbf66bc2656a919ab2a95fb5d75c
--- fs/nfs/super.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/nfs/super.c +2 -1
@@ -2041,7 +2041,8 @@ static int nfs23_validate_mount_data(voimemcpy (sap, &data->addr,sizeof (data->addr)); args->nfs_server.addrlen =sizeof (data->addr); args->nfs_server.port =ntohs (data->addr.sin_port); -if (!nfs_verify_server_address (sap)) +if (sap->sa_family !=AF_INET || + !nfs_verify_server_address (sap)) goto out_no_address;if (!(data->flags &NFS_MOUNT_TCP ))
Greg Kroah-Hartman
maintainerPATCH 47/89 USB: Consolidate LPM checks to avoid enabling LPM twice
In reply to Greg Kroah-HartmanFrom: Kai-Heng Feng <[email protected]>
commit d7a6c0ce8d26412903c7981503bad9e1cc7c45d2 upstream.
USB Bluetooth controller QCA ROME (0cf3:e007) sometimes stops working after S3:
[ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin [ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110)
After some experiments, I found that disabling LPM can workaround the issue.
On some platforms, the USB power is cut during S3, so the driver uses reset-resume to resume the device. During port resume, LPM gets enabled twice, by usb_reset_and_verify_device() and usb_port_resume().
Consolidate all checks into new LPM helpers to make sure LPM only gets enabled once.
--- drivers/usb/core/driver.c | 11 ++++++++--- drivers/usb/core/hub.c | 12 ++++-------- drivers/usb/core/message.c | 3 +-- 3 files changed, 13 insertions(+), 13 deletions(-)
drivers/usb/core/driver.c +8 -3
@@ -1901,9 +1901,6 @@ static int usb_set_usb2_hardware_lpm(strstruct usb_hcd *hcd =bus_to_hcd (udev->bus);int ret = -EPERM ; -if (enable && !udev->usb2_hw_lpm_allowed) -return 0 ; -if (hcd->driver->set_usb2_hw_lpm) { ret = hcd->driver->set_usb2_hw_lpm (hcd, udev, enable);if (!ret)
@@ -1915,11 +1912,19 @@ static int usb_set_usb2_hardware_lpm(strint usb_enable_usb2_hardware_lpm (struct usb_device *udev) { +if (!udev->usb2_hw_lpm_capable || + !udev->usb2_hw_lpm_allowed || + udev->usb2_hw_lpm_enabled) +return 0 ; +return usb_set_usb2_hardware_lpm (udev,1 ); }int usb_disable_usb2_hardware_lpm (struct usb_device *udev) { +if (!udev->usb2_hw_lpm_enabled) +return 0 ; +return usb_set_usb2_hardware_lpm (udev,0 ); }
drivers/usb/core/hub.c +4 -8
@@ -3220,8 +3220,7 @@ int usb_port_suspend(struct usb_device * }/* disable USB2 hardware LPM */ -if (udev->usb2_hw_lpm_enabled ==1 ) -usb_disable_usb2_hardware_lpm (udev); +usb_disable_usb2_hardware_lpm (udev);if (usb_disable_ltm (udev)) {dev_err (&udev->dev,"Failed to disable LTM before suspend\n" );
@@ -3259,8 +3258,7 @@ int usb_port_suspend(struct usb_device *usb_enable_ltm (udev); err_ltm:/* Try to enable USB2 hardware LPM again */ -if (udev->usb2_hw_lpm_capable ==1 ) -usb_enable_usb2_hardware_lpm (udev); +usb_enable_usb2_hardware_lpm (udev);if (udev->do_remote_wakeup) (void )usb_disable_remote_wakeup (udev);
@@ -3543,8 +3541,7 @@ int usb_port_resume(struct usb_device *uhub_port_logical_disconnect (hub, port1); }else {/* Try to enable USB2 hardware LPM */ -if (udev->usb2_hw_lpm_capable ==1 ) -usb_enable_usb2_hardware_lpm (udev); +usb_enable_usb2_hardware_lpm (udev);/* Try to enable USB3 LTM */ usb_enable_ltm (udev);
@@ -5649,8 +5646,7 @@ static int usb_reset_and_verify_device(s/* Disable USB2 hardware LPM. * It will be re-enabled by the enumeration process. */ -if (udev->usb2_hw_lpm_enabled ==1 ) -usb_disable_usb2_hardware_lpm (udev); +usb_disable_usb2_hardware_lpm (udev);/* Disable LPM while we reset the device and reinstall the alt settings. * Device-initiated LPM, and system exit latency settings are cleared
drivers/usb/core/message.c +1 -2
@@ -1243,8 +1243,7 @@ void usb_disable_device(struct usb_devic dev->actconfig->interface[i] =NULL ; } -if (dev->usb2_hw_lpm_enabled ==1 ) -usb_disable_usb2_hardware_lpm (dev); +usb_disable_usb2_hardware_lpm (dev);usb_unlocked_disable_lpm (dev);usb_disable_ltm (dev);
Greg Kroah-Hartman
maintainerPATCH 88/89 net/tls: avoid potential deadlock in tls_set_device_offload_rx()
In reply to Greg Kroah-HartmanFrom: Jakub Kicinski <[email protected]>
[ Upstream commit 62ef81d5632634d5e310ed25b9b940b2b6612b46 ]
If device supports offload, but offload fails tls_set_device_offload_rx() will call tls_sw_free_resources_rx() which (unhelpfully) releases and reacquires the socket lock.
For a small fix release and reacquire the device_offload_lock.
--- net/tls/tls_device.c | 2 ++ 1 file changed, 2 insertions(+)
net/tls/tls_device.c +2 -0
@@ -884,7 +884,9 @@ int tls_set_device_offload_rx(struct soc goto release_netdev; free_sw_resources: +up_read (&device_offload_lock);tls_sw_free_resources_rx (sk); +down_read (&device_offload_lock); release_ctx: ctx->priv_ctx_rx =NULL ; release_netdev:
Greg Kroah-Hartman
maintainerPATCH 86/89 net/mlx5e: Fix the max MTU check in case of XDP
In reply to Greg Kroah-HartmanFrom: Maxim Mikityanskiy <[email protected]>
[ Upstream commit d460c2718906252a2a69bc6f89b537071f792e6e ]
MLX5E_XDP_MAX_MTU was calculated incorrectly. It didn't account for NET_IP_ALIGN and MLX5E_HW2SW_MTU, and it also misused MLX5_SKB_FRAG_SZ. This commit fixes the calculations and adds a brief explanation for the formula used.
--- drivers/net/ethernet/mellanox/mlx5/core/en/xdp.c | 20 ++++++++++++++++++++ drivers/net/ethernet/mellanox/mlx5/core/en/xdp.h | 3 +-- drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 5 +++-- 3 files changed, 24 insertions(+), 4 deletions(-)
drivers/net/ethernet/mellanox/mlx5/core/en/xdp.c +20 -0
@@ -33,6 +33,26 @@#include <linux/bpf_trace.h> #include "en/xdp.h" +int mlx5e_xdp_max_mtu (struct mlx5e_params *params) +{ +int hr =NET_IP_ALIGN +XDP_PACKET_HEADROOM ; + +/* Let S := SKB_DATA_ALIGN(sizeof(struct skb_shared_info)). +* The condition checked in mlx5e_rx_is_linear_skb is: +* SKB_DATA_ALIGN(sw_mtu + hard_mtu + hr) + S <= PAGE_SIZE (1) +* (Note that hw_mtu == sw_mtu + hard_mtu.) +* What is returned from this function is: +* max_mtu = PAGE_SIZE - S - hr - hard_mtu (2) +* After assigning sw_mtu := max_mtu, the left side of (1) turns to +* SKB_DATA_ALIGN(PAGE_SIZE - S) + S, which is equal to PAGE_SIZE, +* because both PAGE_SIZE and S are already aligned. Any number greater +* than max_mtu would make the left side of (1) greater than PAGE_SIZE, +* so max_mtu is the maximum MTU allowed. +*/ + +return MLX5E_HW2SW_MTU (params,SKB_MAX_HEAD (hr)); +} +static inline bool mlx5e_xmit_xdp_buff (struct mlx5e_xdpsq *sq,struct mlx5e_dma_info *di,struct xdp_buff *xdp)
drivers/net/ethernet/mellanox/mlx5/core/en/xdp.h +1 -2
@@ -34,13 +34,12 @@#include "en.h" -#define MLX5E_XDP_MAX_MTU ((int)(PAGE_SIZE - \ - MLX5_SKB_FRAG_SZ(XDP_PACKET_HEADROOM)))#define MLX5E_XDP_MIN_INLINE (ETH_HLEN + VLAN_HLEN)#define MLX5E_XDP_TX_EMPTY_DS_COUNT \ (sizeof(struct mlx5e_tx_wqe) / MLX5_SEND_WQE_DS) #define MLX5E_XDP_TX_DS_COUNT (MLX5E_XDP_TX_EMPTY_DS_COUNT + 1 /* SG DS */) +int mlx5e_xdp_max_mtu (struct mlx5e_params *params);bool mlx5e_xdp_handle (struct mlx5e_rq *rq,struct mlx5e_dma_info *di,void *va,u16 *rx_headroom,u32 *len);bool mlx5e_poll_xdpsq_cq (struct mlx5e_cq *cq,struct mlx5e_rq *rq);
drivers/net/ethernet/mellanox/mlx5/core/en_main.c +3 -2
@@ -3816,7 +3816,7 @@ int mlx5e_change_mtu(struct net_device *if (params->xdp_prog && !mlx5e_rx_is_linear_skb (priv->mdev, &new_channels.params)) {netdev_err (netdev,"MTU(%d) > %d is not allowed while XDP enabled\n" , - new_mtu,MLX5E_XDP_MAX_MTU ); + new_mtu,mlx5e_xdp_max_mtu (params)); err = -EINVAL ; goto out; }
@@ -4280,7 +4280,8 @@ static int mlx5e_xdp_allowed(struct mlx5if (!mlx5e_rx_is_linear_skb (priv->mdev, &new_channels.params)) {netdev_warn (netdev,"XDP is not allowed with MTU(%d) > %d\n" , - new_channels.params.sw_mtu,MLX5E_XDP_MAX_MTU ); + new_channels.params.sw_mtu, +mlx5e_xdp_max_mtu (&new_channels.params));return -EINVAL ; }
Greg Kroah-Hartman
maintainerPATCH 89/89 net/tls: dont leak IV and record seq when offload fails
In reply to Greg Kroah-HartmanFrom: Jakub Kicinski <[email protected]>
[ Upstream commit 12c7686111326148b4b5db189130522a4ad1be4a ]
When device refuses the offload in tls_set_device_offload_rx() it calls tls_sw_free_resources_rx() to clean up software context state.
Unfortunately, tls_sw_free_resources_rx() does not free all the state tls_set_sw_offload() allocated - it leaks IV and sequence number buffers. All other code paths which lead to tls_sw_release_resources_rx() (which tls_sw_free_resources_rx() calls) free those right before the call.
Avoid the leak by moving freeing of iv and rec_seq into tls_sw_release_resources_rx().
--- net/tls/tls_device.c | 2 -- net/tls/tls_main.c | 5 +---- net/tls/tls_sw.c | 3 +++ 3 files changed, 4 insertions(+), 6 deletions(-)
net/tls/tls_device.c +0 -2
@@ -921,8 +921,6 @@ void tls_device_offload_cleanup_rx(struc } out:up_read (&device_offload_lock); -kfree (tls_ctx->rx.rec_seq); -kfree (tls_ctx->rx.iv);tls_sw_release_resources_rx (sk); }
net/tls/tls_main.c +1 -4
@@ -304,11 +304,8 @@ static void tls_sk_proto_close(struct so#endif } -if (ctx->rx_conf ==TLS_SW ) { -kfree (ctx->rx.rec_seq); -kfree (ctx->rx.iv); +if (ctx->rx_conf ==TLS_SW )tls_sw_free_resources_rx (sk); - }#ifdef CONFIG_TLS_DEVICE if (ctx->rx_conf ==TLS_HW )
net/tls/tls_sw.c +3 -0
@@ -1830,6 +1830,9 @@ void tls_sw_release_resources_rx(structstruct tls_context *tls_ctx =tls_get_ctx (sk);struct tls_sw_context_rx *ctx =tls_sw_ctx_rx (tls_ctx); +kfree (tls_ctx->rx.rec_seq); +kfree (tls_ctx->rx.iv); +if (ctx->aead_recv) {kfree_skb (ctx->recv_pkt); ctx->recv_pkt =NULL ;
Greg Kroah-Hartman
maintainerPATCH 87/89 net/mlx5e: Fix use-after-free after xdp_return_frame
In reply to Greg Kroah-HartmanFrom: Maxim Mikityanskiy <[email protected]>
[ Upstream commit 12fc512f5741443a03adde2ead20724da8ad550a ]
xdp_return_frame releases the frame. It leads to releasing the page, so it's not allowed to access xdpi.xdpf->len after that, because xdpi.xdpf is at xdp->data_hard_start after convert_to_xdp_frame. This patch moves the memory access to precede the return of the frame.
--- drivers/net/ethernet/mellanox/mlx5/core/en/xdp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/mellanox/mlx5/core/en/xdp.c +2 -2
@@ -324,9 +324,9 @@ bool mlx5e_poll_xdpsq_cq(struct mlx5e_cqmlx5e_xdpi_fifo_pop (xdpi_fifo);if (is_redirect) { -xdp_return_frame (xdpi.xdpf);dma_unmap_single (sq->pdev, xdpi.dma_addr, xdpi.xdpf->len,DMA_TO_DEVICE ); +xdp_return_frame (xdpi.xdpf); }else {/* Recycle RX page */ mlx5e_page_release (rq, &xdpi.di, true);
@@ -365,9 +365,9 @@ void mlx5e_free_xdpsq_descs(struct mlx5emlx5e_xdpi_fifo_pop (xdpi_fifo);if (is_redirect) { -xdp_return_frame (xdpi.xdpf);dma_unmap_single (sq->pdev, xdpi.dma_addr, xdpi.xdpf->len,DMA_TO_DEVICE ); +xdp_return_frame (xdpi.xdpf); }else {/* Recycle RX page */ mlx5e_page_release (rq, &xdpi.di, false);
Greg Kroah-Hartman
maintainerPATCH 54/89 sched/deadline: Correctly handle active 0-lag timers
In reply to Greg Kroah-HartmanFrom: luca abeni <[email protected]>
commit 1b02cd6a2d7f3e2a6a5262887d2cb2912083e42f upstream.
syzbot reported the following warning:
[ ] WARNING: CPU: 4 PID: 17089 at kernel/sched/deadline.c:255 task_non_contending+0xae0/0x1950
line 255 of deadline.c is:
WARN_ON(hrtimer_active(&dl_se->inactive_timer));
in task_non_contending().
Unfortunately, in some cases (for example, a deadline task continuosly blocking and waking immediately) it can happen that a task blocks (and task_non_contending() is called) while the 0-lag timer is still active.
In this case, the safest thing to do is to immediately decrease the running bandwidth of the task, without trying to re-arm the 0-lag timer.
--- kernel/sched/deadline.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
kernel/sched/deadline.c +1 -2
@@ -252,7 +252,6 @@ static void task_non_contending(struct tif (dl_entity_is_special (dl_se))return ; -WARN_ON (hrtimer_active (&dl_se->inactive_timer));WARN_ON (dl_se->dl_non_contending); zerolag_time = dl_se->deadline -
@@ -269,7 +268,7 @@ static void task_non_contending(struct t* If the "0-lag time" already passed, decrease the active * utilization now, instead of starting a timer */ -if (zerolag_time <0 ) { +if ((zerolag_time <0 ) ||hrtimer_active (&dl_se->inactive_timer)) {if (dl_task (p))sub_running_bw (dl_se, dl_rq);if (!dl_task (p) || p->state ==TASK_DEAD ) {
Greg Kroah-Hartman
maintainerPATCH 85/89 mlxsw: spectrum: Put MC TCs into DWRR mode
In reply to Greg Kroah-HartmanFrom: Petr Machata <[email protected]>
[ Upstream commit f476b3f809fa02f47af6333ed63715058c3fc348 ]
Both Spectrum-1 and Spectrum-2 chips are currently configured such that pairs of TC n (which is used for UC traffic) and TC n+8 (which is used for MC traffic) are feeding into the same subgroup. Strict prioritization is configured between the two TCs, and by enabling MC-aware mode on the switch, the lower-numbered (UC) TCs are favored over the higher-numbered (MC) TCs.
On Spectrum-2 however, there is an issue in configuration of the MC-aware mode. As a result, MC traffic is prioritized over UC traffic. To work around the issue, configure the MC TCs with DWRR mode (while keeping the UC TCs in strict mode).
With this patch, the multicast-unicast arbitration results in the same behavior on both Spectrum-1 and Spectrum-2 chips.
--- drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/mellanox/mlxsw/spectrum.c +1 -1
@@ -2961,7 +2961,7 @@ static int mlxsw_sp_port_ets_init(struct err =mlxsw_sp_port_ets_set (mlxsw_sp_port,MLXSW_REG_QEEC_HIERARCY_TC , i +8 , i, - false,0 ); + true,100 );if (err)return err; }
Greg Kroah-Hartman
maintainerPATCH 52/89 workqueue: Try to catch flush_work() without INIT_WORK().
In reply to Greg Kroah-HartmanFrom: Tetsuo Handa <[email protected]>
commit 4d43d395fed124631ca02356c711facb90185175 upstream.
syzbot found a flush_work() caller who forgot to call INIT_WORK() because that work_struct was allocated by kzalloc() [1]. But the message
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
by lock_map_acquire() is failing to tell that INIT_WORK() is missing.
Since flush_work() without INIT_WORK() is a bug, and INIT_WORK() should set ->func field to non-zero, let's warn if ->func field is zero.
[1] https://syzkaller.appspot.com/bug?id=a5954455fcfa51c29ca2ab55b203076337e1c770
--- kernel/workqueue.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/workqueue.c +3 -0
@@ -2931,6 +2931,9 @@ static bool __flush_work(struct work_strif (WARN_ON (!wq_online))return false; +if (WARN_ON (!work->func)) +return false; +if (!from_cancel) {lock_map_acquire (&work->lockdep_map);lock_map_release (&work->lockdep_map);
Greg Kroah-Hartman
maintainerPATCH 84/89 mlxsw: pci: Reincrease PCI reset timeout
In reply to Greg Kroah-HartmanFrom: Ido Schimmel <[email protected]>
[ Upstream commit 1ab3030193d25878b3b1409060e1e0a879800c95 ]
During driver initialization the driver sends a reset to the device and waits for the firmware to signal that it is ready to continue.
Commit d2f372ba0914 ("mlxsw: pci: Increase PCI SW reset timeout") increased the timeout to 13 seconds due to longer PHY calibration in Spectrum-2 compared to Spectrum-1.
Recently it became apparent that this timeout is too short and therefore this patch increases it again to a safer limit that will be reduced in the future.
--- drivers/net/ethernet/mellanox/mlxsw/pci_hw.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/mellanox/mlxsw/pci_hw.h +1 -1
@@ -27,7 +27,7 @@#define MLXSW_PCI_SW_RESET 0xF0010#define MLXSW_PCI_SW_RESET_RST_BIT BIT(0) -#define MLXSW_PCI_SW_RESET_TIMEOUT_MSECS 13000 +#define MLXSW_PCI_SW_RESET_TIMEOUT_MSECS 20000#define MLXSW_PCI_SW_RESET_WAIT_MSECS 100#define MLXSW_PCI_FW_READY 0xA1844#define MLXSW_PCI_FW_READY_MASK 0xFFFF
Greg Kroah-Hartman
maintainerPATCH 82/89 net: socionext: replace napi_alloc_frag with the netdev variant on init
In reply to Greg Kroah-HartmanFrom: Ilias Apalodimas <[email protected]>
[ Upstream commit ffbf9870dcf1342592a1a26f4cf70bda39046134 ]
The netdev variant is usable on any context since it disables interrupts. The napi variant of the call should only be used within softirq context. Replace napi_alloc_frag on driver init with the correct netdev_alloc_frag call
Changes since v1:
- Adjusted commit message
--- drivers/net/ethernet/socionext/netsec.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/net/ethernet/socionext/netsec.c +7 -4
@@ -673,7 +673,8 @@ static void netsec_process_tx(struct net }static void *netsec_alloc_rx_data (struct netsec_priv *priv, -dma_addr_t *dma_handle,u16 *desc_len) +dma_addr_t *dma_handle,u16 *desc_len, +bool napi) {size_t total_len =SKB_DATA_ALIGN (sizeof (struct skb_shared_info ));size_t payload_len =NETSEC_RX_BUF_SZ ;
@@ -682,7 +683,7 @@ static void *netsec_alloc_rx_data(struct total_len +=SKB_DATA_ALIGN (payload_len +NETSEC_SKB_PAD ); - buf =napi_alloc_frag (total_len); + buf = napi ?napi_alloc_frag (total_len) :netdev_alloc_frag (total_len);if (!buf)return NULL ;
@@ -765,7 +766,8 @@ static int netsec_process_rx(struct nets/* allocate a fresh buffer and map it to the hardware. * This will eventually replace the old buffer in the hardware */ - buf_addr =netsec_alloc_rx_data (priv, &dma_handle, &desc_len); + buf_addr =netsec_alloc_rx_data (priv, &dma_handle, &desc_len, + true);if (unlikely (!buf_addr))break ;
@@ -1069,7 +1071,8 @@ static int netsec_setup_rx_dring(structvoid *buf;u16 len; - buf =netsec_alloc_rx_data (priv, &dma_handle, &len); + buf =netsec_alloc_rx_data (priv, &dma_handle, &len, + false);if (!buf) {netsec_uninit_pkt_dring (priv,NETSEC_RING_RX ); goto err_out;
Greg Kroah-Hartman
maintainerPATCH 78/89 net: stmmac: move stmmac_check_ether_addr() to driver probe
In reply to Greg Kroah-HartmanFrom: Vinod Koul <[email protected]>
[ Upstream commit b561af36b1841088552464cdc3f6371d92f17710 ]
stmmac_check_ether_addr() checks the MAC address and assigns one in driver open(). In many cases when we create slave netdevice, the dev addr is inherited from master but the master dev addr maybe NULL at that time, so move this call to driver probe so that address is always valid.
--- drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c +2 -2
@@ -2590,8 +2590,6 @@ static int stmmac_open(struct net_deviceu32 chan;int ret; -stmmac_check_ether_addr (priv); -if (priv->hw->pcs !=STMMAC_PCS_RGMII && priv->hw->pcs !=STMMAC_PCS_TBI && priv->hw->pcs !=STMMAC_PCS_RTBI ) {
@@ -4265,6 +4263,8 @@ int stmmac_dvr_probe(struct device *deviif (ret) goto error_hw_init; +stmmac_check_ether_addr (priv); +/* Configure real RX and TX queues */ netif_set_real_num_rx_queues (ndev, priv->plat->rx_queues_to_use);netif_set_real_num_tx_queues (ndev, priv->plat->tx_queues_to_use);
Greg Kroah-Hartman
maintainerPATCH 77/89 net/rose: fix unbound loop in rose_loopback_timer()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit 0453c682459583910d611a96de928f4442205493 ]
This patch adds a limit on the number of skbs that fuzzers can queue into loopback_queue. 1000 packets for rose loopback seems more than enough.
Then, since we now have multiple cpus in most linux hosts, we also need to limit the number of skbs rose_loopback_timer() can dequeue at each round.
rose_loopback_queue() can be drop-monitor friendly, calling consume_skb() or kfree_skb() appropriately.
Finally, use mod_timer() instead of del_timer() + add_timer()
syzbot report was :
rcu: INFO: rcu_preempt self-detected stall on CPU rcu: 0-...!: (10499 ticks this GP) idle=536/1/0x4000000000000002 softirq=103291/103291 fqs=34 rcu: (t=10500 jiffies g=140321 q=323) rcu: rcu_preempt kthread starved for 10426 jiffies! g140321 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1 rcu: RCU grace-period kthread stack dump: rcu_preempt I29168 10 2 0x80000000 Call Trace: context_switch kernel/sched/core.c:2877 [inline] __schedule+0x813/0x1cc0 kernel/sched/core.c:3518 schedule+0x92/0x180 kernel/sched/core.c:3562 schedule_timeout+0x4db/0xfd0 kernel/time/timer.c:1803 rcu_gp_fqs_loop kernel/rcu/tree.c:1971 [inline] rcu_gp_kthread+0x962/0x17b0 kernel/rcu/tree.c:2128 kthread+0x357/0x430 kernel/kthread.c:253 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352 NMI backtrace for cpu 0 CPU: 0 PID: 7632 Comm: kworker/0:4 Not tainted 5.1.0-rc5+ #172 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events iterate_cleanup_work Call Trace: <IRQ> __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x172/0x1f0 lib/dump_stack.c:113 nmi_cpu_backtrace.cold+0x63/0xa4 lib/nmi_backtrace.c:101 nmi_trigger_cpumask_backtrace+0x1be/0x236 lib/nmi_backtrace.c:62 arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38 trigger_single_cpu_backtrace include/linux/nmi.h:164 [inline] rcu_dump_cpu_stacks+0x183/0x1cf kernel/rcu/tree.c:1223 print_cpu_stall kernel/rcu/tree.c:1360 [inline] check_cpu_stall kernel/rcu/tree.c:1434 [inline] rcu_pending kernel/rcu/tree.c:3103 [inline] rcu_sched_clock_irq.cold+0x500/0xa4a kernel/rcu/tree.c:2544 update_process_times+0x32/0x80 kernel/time/timer.c:1635 tick_sched_handle+0xa2/0x190 kernel/time/tick-sched.c:161 tick_sched_timer+0x47/0x130 kernel/time/tick-sched.c:1271 __run_hrtimer kernel/time/hrtimer.c:1389 [inline] __hrtimer_run_queues+0x33e/0xde0 kernel/time/hrtimer.c:1451 hrtimer_interrupt+0x314/0x770 kernel/time/hrtimer.c:1509 local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1035 [inline] smp_apic_timer_interrupt+0x120/0x570 arch/x86/kernel/apic/apic.c:1060 apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:807 RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x50 kernel/kcov.c:95 Code: 89 25 b4 6e ec 08 41 bc f4 ff ff ff e8 cd 5d ea ff 48 c7 05 9e 6e ec 08 00 00 00 00 e9 a4 e9 ff ff 90 90 90 90 90 90 90 90 90 <55> 48 89 e5 48 8b 75 08 65 48 8b 04 25 00 ee 01 00 65 8b 15 c8 60 RSP: 0018:ffff8880ae807ce0 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff13 RAX: ffff88806fd40640 RBX: dffffc0000000000 RCX: ffffffff863fbc56 RDX: 0000000000000100 RSI: ffffffff863fbc1d RDI: ffff88808cf94228 RBP: ffff8880ae807d10 R08: ffff88806fd40640 R09: ffffed1015d00f8b R10: ffffed1015d00f8a R11: 0000000000000003 R12: ffff88808cf941c0 R13: 00000000fffff034 R14: ffff8882166cd840 R15: 0000000000000000 rose_loopback_timer+0x30d/0x3f0 net/rose/rose_loopback.c:91 call_timer_fn+0x190/0x720 kernel/time/timer.c:1325 expire_timers kernel/time/timer.c:1362 [inline] __run_timers kernel/time/timer.c:1681 [inline] __run_timers kernel/time/timer.c:1649 [inline] run_timer_softirq+0x652/0x1700 kernel/time/timer.c:1694 __do_softirq+0x266/0x95a kernel/softirq.c:293 do_softirq_own_stack+0x2a/0x40 arch/x86/entry/entry_64.S:1027
--- net/rose/rose_loopback.c | 27 ++++++++++++++++----------- 1 file changed, 16 insertions(+), 11 deletions(-)
net/rose/rose_loopback.c +16 -11
@@ -16,6 +16,7 @@#include <linux/init.h> static struct sk_buff_head loopback_queue; +#define ROSE_LOOPBACK_LIMIT 1000static struct timer_list loopback_timer;static void rose_set_loopback_timer (void );
@@ -35,29 +36,27 @@ static int rose_loopback_running(void)int rose_loopback_queue (struct sk_buff *skb,struct rose_neigh *neigh) { -struct sk_buff *skbn; +struct sk_buff *skbn =NULL ; - skbn =skb_clone (skb,GFP_ATOMIC ); +if (skb_queue_len (&loopback_queue) <ROSE_LOOPBACK_LIMIT ) + skbn =skb_clone (skb,GFP_ATOMIC ); -kfree_skb (skb); - -if (skbn !=NULL ) { +if (skbn) { +consume_skb (skb);skb_queue_tail (&loopback_queue, skbn);if (!rose_loopback_running ())rose_set_loopback_timer (); + }else { +kfree_skb (skb); }return 1 ; } -static void rose_set_loopback_timer (void ) { -del_timer (&loopback_timer); - - loopback_timer.expires = jiffies +10 ; -add_timer (&loopback_timer); +mod_timer (&loopback_timer, jiffies +10 ); }static void rose_loopback_timer (struct timer_list *unused)
@@ -68,8 +67,12 @@ static void rose_loopback_timer(struct tstruct sock *sk;unsigned short frametype;unsigned int lci_i, lci_o; +int count; -while ((skb =skb_dequeue (&loopback_queue)) !=NULL ) { +for (count =0 ; count <ROSE_LOOPBACK_LIMIT ; count++) { + skb =skb_dequeue (&loopback_queue); +if (!skb) +return ;if (skb->len <ROSE_MIN_LEN ) {kfree_skb (skb);continue ;
@@ -106,6 +109,8 @@ static void rose_loopback_timer(struct tkfree_skb (skb); } } +if (!skb_queue_empty (&loopback_queue)) +mod_timer (&loopback_timer, jiffies +1 ); } void __exit rose_loopback_clear(void)
Greg Kroah-Hartman
maintainerPATCH 73/89 ipv4: set the tcp_min_rtt_wlen range from 0 to one day
In reply to Greg Kroah-HartmanFrom: ZhangXiaoxu <[email protected]>
[ Upstream commit 19fad20d15a6494f47f85d869f00b11343ee5c78 ]
There is a UBSAN report as below:
UBSAN: Undefined behaviour in net/ipv4/tcp_input.c:2877:56 signed integer overflow: 2147483647 * 1000 cannot be represented in type 'int' CPU: 3 PID: 0 Comm: swapper/3 Not tainted 5.1.0-rc4-00058-g582549e #1 Call Trace: <IRQ> dump_stack+0x8c/0xba ubsan_epilogue+0x11/0x60 handle_overflow+0x12d/0x170 ? ttwu_do_wakeup+0x21/0x320 __ubsan_handle_mul_overflow+0x12/0x20 tcp_ack_update_rtt+0x76c/0x780 tcp_clean_rtx_queue+0x499/0x14d0 tcp_ack+0x69e/0x1240 ? __wake_up_sync_key+0x2c/0x50 ? update_group_capacity+0x50/0x680 tcp_rcv_established+0x4e2/0xe10 tcp_v4_do_rcv+0x22b/0x420 tcp_v4_rcv+0xfe8/0x1190 ip_protocol_deliver_rcu+0x36/0x180 ip_local_deliver+0x15b/0x1a0 ip_rcv+0xac/0xd0 __netif_receive_skb_one_core+0x7f/0xb0 __netif_receive_skb+0x33/0xc0 netif_receive_skb_internal+0x84/0x1c0 napi_gro_receive+0x2a0/0x300 receive_buf+0x3d4/0x2350 ? detach_buf_split+0x159/0x390 virtnet_poll+0x198/0x840 ? reweight_entity+0x243/0x4b0 net_rx_action+0x25c/0x770 __do_softirq+0x19b/0x66d irq_exit+0x1eb/0x230 do_IRQ+0x7a/0x150 common_interrupt+0xf/0xf </IRQ>
It can be reproduced by:
echo 2147483647 > /proc/sys/net/ipv4/tcp_min_rtt_wlen
--- Documentation/networking/ip-sysctl.txt | 1 + net/ipv4/sysctl_net_ipv4.c | 5 ++++- 2 files changed, 5 insertions(+), 1 deletion(-)
Documentation/networking/ip-sysctl.txt +1 -0
@@ -422,6 +422,7 @@ tcp_min_rtt_wlen - INTEGER minimum RTT when it is moved to a longer path (e.g., due to traffic engineering). A longer window makes the filter more resistant to RTT inflations such as transient congestion. The unit is seconds. + Possible values: 0 - 86400 (1 day) Default: 300 tcp_moderate_rcvbuf - BOOLEAN
net/ipv4/sysctl_net_ipv4.c +4 -1
@@ -49,6 +49,7 @@ static int ip_ping_group_range_min[] = {static int ip_ping_group_range_max[] = {GID_T_MAX ,GID_T_MAX };static int comp_sack_nr_max =255 ;static u32 u32_max_div_HZ =UINT_MAX /HZ ; +static int one_day_secs =24 *3600 ;/* obsolete */ static int sysctl_tcp_low_latency__read_mostly ;
@@ -1151,7 +1152,9 @@ static struct ctl_table ipv4_net_table[] .data = &init_net.ipv4.sysctl_tcp_min_rtt_wlen, .maxlen = sizeof(int), .mode = 0644, - .proc_handler = proc_dointvec + .proc_handler = proc_dointvec_minmax, + .extra1 = &zero, + .extra2 = &one_day_secs }, { .procname = "tcp_autocorking",
Greg Kroah-Hartman
maintainerPATCH 68/89 Fix aio_poll() races
In reply to Greg Kroah-HartmanFrom: Al Viro <[email protected]>
commit af5c72b1fc7a00aa484e90b0c4e0eeb582545634 upstream.
aio_poll() has to cope with several unpleasant problems:
* requests that might stay around indefinitely need to
be made visible for io_cancel(2); that must not be done to a request already completed, though.
* in cases when ->poll() has placed us on a waitqueue,
wakeup might have happened (and request completed) before ->poll() returns.
* worse, in some early wakeup cases request might end
up re-added into the queue later - we can't treat "woken up and currently not in the queue" as "it's not going to stick around indefinitely"
* ... moreover, ->poll() might have decided not to
put it on any queues to start with, and that needs to be distinguished from the previous case
* ->poll() might have tried to put us on more than one queue.
Only the first will succeed for aio poll, so we might end up missing wakeups. OTOH, we might very well notice that only after the wakeup hits and request gets completed (all before ->poll() gets around to the second poll_wait()). In that case it's too late to decide that we have an error.
req->woken was an attempt to deal with that. Unfortunately, it was broken. What we need to keep track of is not that wakeup has happened - the thing might come back after that. It's that async reference is already gone and won't come back, so we can't (and needn't) put the request on the list of cancellables.
The easiest case is "request hadn't been put on any waitqueues"; we can tell by seeing NULL apt.head, and in that case there won't be anything async. We should either complete the request ourselves (if vfs_poll() reports anything of interest) or return an error.
In all other cases we get exclusion with wakeups by grabbing the queue lock.
If request is currently on queue and we have something interesting from vfs_poll(), we can steal it and complete the request ourselves.
If it's on queue and vfs_poll() has not reported anything interesting, we either put it on the cancellable list, or, if we know that it hadn't been put on all queues ->poll() wanted it on, we steal it and return an error.
If it's _not_ on queue, it's either been already dealt with (in which case we do nothing), or there's aio_poll_complete_work() about to be executed. In that case we either put it on the cancellable list, or, if we know it hadn't been put on all queues ->poll() wanted it on, simulate what cancel would've done.
It's a lot more convoluted than I'd like it to be. Single-consumer APIs suck, and unfortunately aio is not an exception...
--- fs/aio.c | 90 ++++++++++++++++++++++++++++----------------------------------- 1 file changed, 40 insertions(+), 50 deletions(-)
fs/aio.c +40 -50
@@ -181,7 +181,7 @@ struct poll_iocb {struct file *file;struct wait_queue_head *head;__poll_t events; -bool woken; +bool done;bool cancelled;struct wait_queue_entry wait;struct work_struct work;
@@ -1606,12 +1606,6 @@ static int aio_fsync(struct fsync_iocb *return 0 ; } -static inline void aio_poll_complete (struct aio_kiocb *iocb,__poll_t mask) -{ - iocb->ki_res.res =mangle_poll (mask); -iocb_put (iocb); -} -static void aio_poll_complete_work (struct work_struct *work) { struct poll_iocb *req = container_of(work, struct poll_iocb, work);
@@ -1637,9 +1631,11 @@ static void aio_poll_complete_work(strucreturn ; }list_del_init (&iocb->ki_list); + iocb->ki_res.res =mangle_poll (mask); + req->done = true;spin_unlock_irq (&ctx->ctx_lock); -aio_poll_complete (iocb, mask); +iocb_put (iocb); }/* assumes we are called with irqs disabled */
@@ -1667,31 +1663,27 @@ static int aio_poll_wake(struct wait_que__poll_t mask =key_to_poll (key);unsigned long flags; - req->woken = true; -/* for instances that support it check for an event match first: */ -if (mask) { -if (!(mask & req->events)) -return 0 ; +if (mask && !(mask & req->events)) +return 0 ; +list_del_init (&req->wait.entry); + +if (mask &&spin_trylock_irqsave (&iocb->ki_ctx->ctx_lock, flags)) {/* * Try to complete the iocb inline if we can. Use * irqsave/irqrestore because not all filesystems (e.g. fuse) * call this function with IRQs disabled and because IRQs * have to be disabled before ctx_lock is obtained. */ -if (spin_trylock_irqsave (&iocb->ki_ctx->ctx_lock, flags)) { -list_del (&iocb->ki_list); -spin_unlock_irqrestore (&iocb->ki_ctx->ctx_lock, flags); - -list_del_init (&req->wait.entry); -aio_poll_complete (iocb, mask); -return 1 ; - } +list_del (&iocb->ki_list); + iocb->ki_res.res =mangle_poll (mask); + req->done = true; +spin_unlock_irqrestore (&iocb->ki_ctx->ctx_lock, flags); +iocb_put (iocb); + }else { +schedule_work (&req->work); } - -list_del_init (&req->wait.entry); -schedule_work (&req->work);return 1 ; }
@@ -1723,6 +1715,7 @@ static ssize_t aio_poll(struct aio_kiocbstruct kioctx *ctx = aiocb->ki_ctx;struct poll_iocb *req = &aiocb->poll;struct aio_poll_table apt; +bool cancel = false;__poll_t mask;/* reject any unknown events outside the normal event mask. */
@@ -1736,7 +1729,7 @@ static ssize_t aio_poll(struct aio_kiocb req->events =demangle_poll (iocb->aio_buf) |EPOLLERR |EPOLLHUP ; req->head =NULL ; - req->woken = false; + req->done = false; req->cancelled = false; apt.pt._qproc = aio_poll_queue_proc;
@@ -1749,36 +1742,33 @@ static ssize_t aio_poll(struct aio_kiocbinit_waitqueue_func_entry (&req->wait, aio_poll_wake); mask =vfs_poll (req->file, &apt.pt) & req->events; -if (unlikely (!req->head)) { -/* we did not manage to set up a waitqueue, done */ - goto out; - } -spin_lock_irq (&ctx->ctx_lock); -spin_lock (&req->head->lock); -if (req->woken) { -/* wake_up context handles the rest */ - mask =0 ; +if (likely (req->head)) { +spin_lock (&req->head->lock); +if (unlikely (list_empty (&req->wait.entry))) { +if (apt.error) + cancel = true; + apt.error =0 ; + mask =0 ; + } +if (mask || apt.error) { +list_del_init (&req->wait.entry); + }else if (cancel) { +WRITE_ONCE (req->cancelled, true); + }else if (!req->done) {/* actually waiting for an event */ +list_add_tail (&aiocb->ki_list, &ctx->active_reqs); + aiocb->ki_cancel = aio_poll_cancel; + } +spin_unlock (&req->head->lock); + } +if (mask) {/* no async, we'd stolen it */ + aiocb->ki_res.res =mangle_poll (mask); apt.error =0 ; - }else if (mask || apt.error) { -/* if we get an error or a mask we are done */ -WARN_ON_ONCE (list_empty (&req->wait.entry)); -list_del_init (&req->wait.entry); - }else { -/* actually waiting for an event */ -list_add_tail (&aiocb->ki_list, &ctx->active_reqs); - aiocb->ki_cancel = aio_poll_cancel; } -spin_unlock (&req->head->lock);spin_unlock_irq (&ctx->ctx_lock); - -out: -if (unlikely (apt.error)) -return apt.error; -if (mask) -aio_poll_complete (aiocb, mask); -return 0 ; +iocb_put (aiocb); +return apt.error; } static int __io_submit_one(struct kioctx *ctx, const struct iocb *iocb,
Greg Kroah-Hartman
maintainerPATCH 66/89 aio: keep io_event in aio_kiocb
In reply to Greg Kroah-HartmanFrom: Al Viro <[email protected]>
commit a9339b7855094ba11a97e8822ae038135e879e79 upstream.
We want to separate forming the resulting io_event from putting it into the ring buffer.
--- fs/aio.c | 31 +++++++++++++------------------ 1 file changed, 13 insertions(+), 18 deletions(-)
fs/aio.c +13 -18
@@ -204,8 +204,7 @@ struct aio_kiocb {struct kioctx *ki_ctx;kiocb_cancel_fn *ki_cancel; -struct iocb __user *ki_user_iocb;/* user's aiocb */ -__u64 ki_user_data;/* user's data for completion */ +struct io_event ki_res;struct list_head ki_list;/* the aio core uses this * for cancellation */
@@ -1084,15 +1083,6 @@ static inline void iocb_put(struct aio_kiocb_destroy (iocb); } -static void aio_fill_event (struct io_event *ev,struct aio_kiocb *iocb, -long res,long res2) -{ - ev->obj = (u64 )(unsigned long )iocb->ki_user_iocb; - ev->data = iocb->ki_user_data; - ev->res = res; - ev->res2 = res2; -} -/* aio_complete * Called when the io request on the given iocb is complete. */
@@ -1104,6 +1094,8 @@ static void aio_complete(struct aio_kiocunsigned tail, pos, head;unsigned long flags; + iocb->ki_res.res = res; + iocb->ki_res.res2 = res2;/* * Add a completion event to the ring buffer. Must be done holding * ctx->completion_lock to prevent other code from messing with the tail
@@ -1120,14 +1112,14 @@ static void aio_complete(struct aio_kioc ev_page =kmap_atomic (ctx->ring_pages[pos /AIO_EVENTS_PER_PAGE ]); event = ev_page + pos %AIO_EVENTS_PER_PAGE ; -aio_fill_event (event, iocb, res, res2); + *event = iocb->ki_res;kunmap_atomic (ev_page);flush_dcache_page (ctx->ring_pages[pos /AIO_EVENTS_PER_PAGE ]); -pr_debug ("%p[%u]: %p: %p %Lx %lx %lx\n" , - ctx, tail, iocb, iocb->ki_user_iocb, iocb->ki_user_data, - res, res2); +pr_debug ("%p[%u]: %p: %p %Lx %Lx %Lx\n" , ctx, tail, iocb, + (void __user *)(unsigned long )iocb->ki_res.obj, + iocb->ki_res.data, iocb->ki_res.res, iocb->ki_res.res2);/* after flagging the request as done, we * must never even look at it again
@@ -1844,8 +1836,10 @@ static int __io_submit_one(struct kioctx goto out_put_req; } - req->ki_user_iocb = user_iocb; - req->ki_user_data = iocb->aio_data; + req->ki_res.obj = (u64 )(unsigned long )user_iocb; + req->ki_res.data = iocb->aio_data; + req->ki_res.res =0 ; + req->ki_res.res2 =0 ;switch (iocb->aio_lio_opcode) {case IOCB_CMD_PREAD :
@@ -2019,6 +2013,7 @@ SYSCALL_DEFINE3(io_cancel, aio_context_tstruct aio_kiocb *kiocb;int ret = -EINVAL ;u32 key; +u64 obj = (u64 )(unsigned long )iocb;if (unlikely (get_user (key, &iocb->aio_key)))return -EFAULT ;
@@ -2032,7 +2027,7 @@ SYSCALL_DEFINE3(io_cancel, aio_context_tspin_lock_irq (&ctx->ctx_lock);/* TODO: use a hash or array, this sucks. */ list_for_each_entry (kiocb, &ctx->active_reqs, ki_list) { -if (kiocb->ki_user_iocb == iocb) { +if (kiocb->ki_res.obj == obj) { ret = kiocb->ki_cancel (&kiocb->rw);list_del_init (&kiocb->ki_list);break ;
Greg Kroah-Hartman
maintainerPATCH 62/89 net/rds: Check address length before reading address family
In reply to Greg Kroah-HartmanFrom: Tetsuo Handa <[email protected]>
commit dd3ac9a684358b8c1d5c432ca8322aaf5e4f28ee upstream.
syzbot is reporting uninitialized value at rds_connect() [1] and rds_bind() [2]. This is because syzbot is passing ulen == 0 whereas these functions expect that it is safe to access sockaddr->family field in order to determine minimal address length for validation.
[1] https://syzkaller.appspot.com/bug?id=f4e61c010416c1e6f0fa3ffe247561b60a50ad71
[2] https://syzkaller.appspot.com/bug?id=a4bf9e41b7e055c3823fdcd83e8c58ca7270e38f
--- net/rds/af_rds.c | 3 +++ net/rds/bind.c | 2 ++ 2 files changed, 5 insertions(+)
net/rds/af_rds.c +3 -0
@@ -506,6 +506,9 @@ static int rds_connect(struct socket *sostruct rds_sock *rs =rds_sk_to_rs (sk);int ret =0 ; + if (addr_len < offsetofend(struct sockaddr, sa_family)) +return -EINVAL ; +lock_sock (sk);switch (uaddr->sa_family) {
net/rds/bind.c +2 -0
@@ -173,6 +173,8 @@ int rds_bind(struct socket *sock, struct/* We allow an RDS socket to be bound to either IPv4 or IPv6 * address. */ + if (addr_len < offsetofend(struct sockaddr, sa_family)) +return -EINVAL ;if (uaddr->sa_family ==AF_INET ) {struct sockaddr_in *sin = (struct sockaddr_in *)uaddr;
Greg Kroah-Hartman
maintainerPATCH 60/89 tipc: check link name with right length in tipc_nl_compat_link_set
In reply to Greg Kroah-HartmanFrom: Xin Long <[email protected]>
commit 8c63bf9ab4be8b83bd8c34aacfd2f1d2c8901c8a upstream.
A similar issue as fixed by Patch "tipc: check bearer name with right length in tipc_nl_compat_bearer_enable" was also found by syzbot in tipc_nl_compat_link_set().
The length to check with should be 'TLV_GET_DATA_LEN(msg->req) - offsetof(struct tipc_link_config, name)'.
--- net/tipc/netlink_compat.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
net/tipc/netlink_compat.c +6 -1
@@ -777,7 +777,12 @@ static int tipc_nl_compat_link_set(struc lc = (struct tipc_link_config *)TLV_DATA (msg->req); - len =min_t (int,TLV_GET_DATA_LEN (msg->req),TIPC_MAX_LINK_NAME ); + len =TLV_GET_DATA_LEN (msg->req); + len -= offsetof(struct tipc_link_config , name); +if (len <=0 ) +return -EINVAL ; + + len =min_t (int, len,TIPC_MAX_LINK_NAME );if (!string_is_valid (lc->name, len))return -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 46/89 USB: Add new USB LPM helpers
In reply to Greg Kroah-HartmanFrom: Kai-Heng Feng <[email protected]>
commit 7529b2574a7aaf902f1f8159fbc2a7caa74be559 upstream.
Use new helpers to make LPM enabling/disabling more clear.
This is a preparation to subsequent patch.
--- drivers/usb/core/driver.c | 12 +++++++++++- drivers/usb/core/hub.c | 12 ++++++------ drivers/usb/core/message.c | 2 +- drivers/usb/core/sysfs.c | 5 ++++- drivers/usb/core/usb.h | 10 ++++++++-- 5 files changed, 30 insertions(+), 11 deletions(-)
drivers/usb/core/driver.c +11 -1
@@ -1896,7 +1896,7 @@ int usb_runtime_idle(struct device *dev)return -EBUSY ; } -int usb_set_usb2_hardware_lpm (struct usb_device *udev,int enable) +static int usb_set_usb2_hardware_lpm (struct usb_device *udev,int enable) {struct usb_hcd *hcd =bus_to_hcd (udev->bus);int ret = -EPERM ;
@@ -1913,6 +1913,16 @@ int usb_set_usb2_hardware_lpm(struct usbreturn ret; } +int usb_enable_usb2_hardware_lpm (struct usb_device *udev) +{ +return usb_set_usb2_hardware_lpm (udev,1 ); +} + +int usb_disable_usb2_hardware_lpm (struct usb_device *udev) +{ +return usb_set_usb2_hardware_lpm (udev,0 ); +} +#endif /* CONFIG_PM */ struct bus_type usb_bus_type = {
drivers/usb/core/hub.c +6 -6
@@ -3221,7 +3221,7 @@ int usb_port_suspend(struct usb_device */* disable USB2 hardware LPM */ if (udev->usb2_hw_lpm_enabled ==1 ) -usb_set_usb2_hardware_lpm (udev,0 ); +usb_disable_usb2_hardware_lpm (udev);if (usb_disable_ltm (udev)) {dev_err (&udev->dev,"Failed to disable LTM before suspend\n" );
@@ -3260,7 +3260,7 @@ int usb_port_suspend(struct usb_device * err_ltm:/* Try to enable USB2 hardware LPM again */ if (udev->usb2_hw_lpm_capable ==1 ) -usb_set_usb2_hardware_lpm (udev,1 ); +usb_enable_usb2_hardware_lpm (udev);if (udev->do_remote_wakeup) (void )usb_disable_remote_wakeup (udev);
@@ -3544,7 +3544,7 @@ int usb_port_resume(struct usb_device *u }else {/* Try to enable USB2 hardware LPM */ if (udev->usb2_hw_lpm_capable ==1 ) -usb_set_usb2_hardware_lpm (udev,1 ); +usb_enable_usb2_hardware_lpm (udev);/* Try to enable USB3 LTM */ usb_enable_ltm (udev);
@@ -4435,7 +4435,7 @@ static void hub_set_initial_usb2_lpm_polif ((udev->bos->ext_cap->bmAttributes &cpu_to_le32 (USB_BESL_SUPPORT )) || connect_type ==USB_PORT_CONNECT_TYPE_HARD_WIRED ) { udev->usb2_hw_lpm_allowed =1 ; -usb_set_usb2_hardware_lpm (udev,1 ); +usb_enable_usb2_hardware_lpm (udev); } }
@@ -5650,7 +5650,7 @@ static int usb_reset_and_verify_device(s* It will be re-enabled by the enumeration process. */ if (udev->usb2_hw_lpm_enabled ==1 ) -usb_set_usb2_hardware_lpm (udev,0 ); +usb_disable_usb2_hardware_lpm (udev);/* Disable LPM while we reset the device and reinstall the alt settings. * Device-initiated LPM, and system exit latency settings are cleared
@@ -5753,7 +5753,7 @@ static int usb_reset_and_verify_device(s done:/* Now that the alt settings are re-installed, enable LTM and LPM. */ -usb_set_usb2_hardware_lpm (udev,1 ); +usb_enable_usb2_hardware_lpm (udev);usb_unlocked_enable_lpm (udev);usb_enable_ltm (udev);usb_release_bos_descriptor (udev);
drivers/usb/core/message.c +1 -1
@@ -1244,7 +1244,7 @@ void usb_disable_device(struct usb_devic }if (dev->usb2_hw_lpm_enabled ==1 ) -usb_set_usb2_hardware_lpm (dev,0 ); +usb_disable_usb2_hardware_lpm (dev);usb_unlocked_disable_lpm (dev);usb_disable_ltm (dev);
drivers/usb/core/sysfs.c +4 -1
@@ -528,7 +528,10 @@ static ssize_t usb2_hardware_lpm_store(sif (!ret) { udev->usb2_hw_lpm_allowed = value; - ret =usb_set_usb2_hardware_lpm (udev, value); +if (value) + ret =usb_enable_usb2_hardware_lpm (udev); +else + ret =usb_disable_usb2_hardware_lpm (udev); }usb_unlock_device (udev);
drivers/usb/core/usb.h +8 -2
@@ -92,7 +92,8 @@ extern int usb_remote_wakeup(struct usb_extern int usb_runtime_suspend (struct device *dev);extern int usb_runtime_resume (struct device *dev);extern int usb_runtime_idle (struct device *dev); -extern int usb_set_usb2_hardware_lpm (struct usb_device *udev,int enable); +extern int usb_enable_usb2_hardware_lpm (struct usb_device *udev); +extern int usb_disable_usb2_hardware_lpm (struct usb_device *udev);#else
@@ -112,7 +113,12 @@ static inline int usb_autoresume_device(return 0 ; } -static inline int usb_set_usb2_hardware_lpm (struct usb_device *udev,int enable) +static inline int usb_enable_usb2_hardware_lpm (struct usb_device *udev) +{ +return 0 ; +} + +static inline int usb_disable_usb2_hardware_lpm (struct usb_device *udev) {return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 45/89 drm/vc4: Fix compilation error reported by kbuild test bot
In reply to Greg Kroah-HartmanFrom: Maarten Lankhorst <[email protected]>
commit 462ce5d963f18b71c63f6b7730a35a2ee5273540 upstream.
A pointer to crtc was missing, resulting in the following build error:drivers/gpu/drm/vc4/vc4_crtc.c:1045:44: sparse: sparse: incorrect type in argument 1 (different base types)drivers/gpu/drm/vc4/vc4_crtc.c:1045:44: sparse: expected struct drm_crtc *crtcdrivers/gpu/drm/vc4/vc4_crtc.c:1045:44: sparse: got struct drm_crtc_state *statedrivers/gpu/drm/vc4/vc4_crtc.c:1045:39: sparse: sparse: not enough arguments for function vc4_crtc_destroy_state
--- drivers/gpu/drm/vc4/vc4_crtc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/vc4/vc4_crtc.c +1 -1
@@ -999,7 +999,7 @@ static void vc4_crtc_reset(struct drm_crtc *crtc) {if (crtc->state) -vc4_crtc_destroy_state (crtc->state); +vc4_crtc_destroy_state (crtc, crtc->state); crtc->state =kzalloc (sizeof (struct vc4_crtc_state ),GFP_KERNEL );if (crtc->state)
Greg Kroah-Hartman
maintainerPATCH 41/89 powerpc/mm/radix: Make Radix require HUGETLB_PAGE
In reply to Greg Kroah-HartmanFrom: Michael Ellerman <[email protected]>
commit 8adddf349fda0d3de2f6bb41ddf838cbf36a8ad2 upstream.
Joel reported weird crashes using skiroot_defconfig, in his case we jumped into an NX page:
kernel tried to execute exec-protected page (c000000002bff4f0) - exploit attempt? (uid: 0)
BUG: Unable to handle kernel instruction fetch Faulting instruction address: 0xc000000002bff4f0
Looking at the disassembly, we had simply branched to that address:
c000000000c001bc 49fff335 bl c000000002bff4f0
But that didn't match the original kernel image:
c000000000c001bc 4bfff335 bl c000000000bff4f0 <kobject_get+0x8>
When STRICT_KERNEL_RWX is enabled, and we're using the radix MMU, we call radix__change_memory_range() late in boot to change page protections. We do that both to mark rodata read only and also to mark init text no-execute. That involves walking the kernel page tables, and clearing _PAGE_WRITE or _PAGE_EXEC respectively.
With radix we may use hugepages for the linear mapping, so the code in radix__change_memory_range() uses eg. pmd_huge() to test if it has found a huge mapping, and if so it stops the page table walk and changes the PMD permissions.
However if the kernel is built without HUGETLBFS support, pmd_huge() is just a #define that always returns 0. That causes the code in radix__change_memory_range() to incorrectly interpret the PMD value as a pointer to a PTE page rather than as a PTE at the PMD level.
We can see this using dv in xmon which also uses pmd_huge():
0:mon> dv c000000000000000
pgd @ 0xc000000001740000
pgdp @ 0xc000000001740000 = 0x80000000ffffb009
pudp @ 0xc0000000ffffb000 = 0x80000000ffffa009
pmdp @ 0xc0000000ffffa000 = 0xc00000000000018f <- this is a PTE
ptep @ 0xc000000000000100 = 0xa64bb17da64ab07d <- kernel text
The end result is we treat the value at 0xc000000000000100 as a PTE and clear _PAGE_WRITE or _PAGE_EXEC, potentially corrupting the code at that address.
In Joel's specific case we cleared the sign bit in the offset of the branch, causing a backward branch to turn into a forward branch which caused us to branch into a non-executable page. However the exact nature of the crash depends on kernel version, compiler version, and other factors.
We need to fix radix__change_memory_range() to not use accessors that depend on HUGETLBFS, but we also have radix memory hotplug code that uses pmd_huge() etc that will also need fixing. So for now just disallow the broken combination of Radix with HUGETLBFS disabled.
The only defconfig we have that is affected is skiroot_defconfig, so turn on HUGETLBFS there so that it still gets Radix.
--- arch/powerpc/configs/skiroot_defconfig | 1 + arch/powerpc/platforms/Kconfig.cputype | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-)
arch/powerpc/configs/skiroot_defconfig +1 -0
@@ -260,6 +260,7 @@ CONFIG_UDF_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_PROC_KCORE=y +CONFIG_HUGETLBFS=y # CONFIG_MISC_FILESYSTEMS is not set # CONFIG_NETWORK_FILESYSTEMS is not set CONFIG_NLS=y
arch/powerpc/platforms/Kconfig.cputype +1 -1
@@ -318,7 +318,7 @@ config ARCH_ENABLE_SPLIT_PMD_PTLOCK config PPC_RADIX_MMU bool "Radix MMU Support" - depends on PPC_BOOK3S_64 + depends on PPC_BOOK3S_64 && HUGETLB_PAGE select ARCH_HAS_GIGANTIC_PAGE if (MEMORY_ISOLATION && COMPACTION) || CMA default y help
Greg Kroah-Hartman
maintainerPATCH 43/89 drm/ttm: fix re-init of global structures
In reply to Greg Kroah-HartmanFrom: Christian König <[email protected]>
commit bd4264112f93045704731850c5e4d85db981cd85 upstream.
When a driver unloads without unloading TTM we don't correctly clear the global structures leading to errors on re-init.
Next step should probably be to remove the global structures and kobjs all together, but this is tricky since we need to maintain backward compatibility.
--- drivers/gpu/drm/ttm/ttm_bo.c | 10 +++++----- drivers/gpu/drm/ttm/ttm_memory.c | 5 +++-- include/drm/ttm/ttm_bo_driver.h | 1 - 3 files changed, 8 insertions(+), 8 deletions(-)
drivers/gpu/drm/ttm/ttm_bo.c +5 -5
@@ -49,9 +49,8 @@ static void ttm_bo_global_kobj_release(s* ttm_global_mutex - protecting the global BO state */ DEFINE_MUTEX (ttm_global_mutex); -struct ttm_bo_global ttm_bo_glob = { - .use_count =0 -}; +unsigned ttm_bo_glob_use_count; +struct ttm_bo_global ttm_bo_glob;static struct attribute ttm_bo_count = { .name ="bo_count" ,
@@ -1535,12 +1534,13 @@ static void ttm_bo_global_release(void)struct ttm_bo_global *glob = &ttm_bo_glob;mutex_lock (&ttm_global_mutex); -if (--glob->use_count >0 ) +if (--ttm_bo_glob_use_count >0 ) goto out;kobject_del (&glob->kobj);kobject_put (&glob->kobj);ttm_mem_global_release (&ttm_mem_glob); +memset (glob,0 ,sizeof (*glob)); out:mutex_unlock (&ttm_global_mutex); }
@@ -1552,7 +1552,7 @@ static int ttm_bo_global_init(void)unsigned i;mutex_lock (&ttm_global_mutex); -if (++glob->use_count >1 ) +if (++ttm_bo_glob_use_count >1 ) goto out; ret =ttm_mem_global_init (&ttm_mem_glob);
drivers/gpu/drm/ttm/ttm_memory.c +3 -2
@@ -461,8 +461,8 @@ out_no_zone:void ttm_mem_global_release (struct ttm_mem_global *glob) { -unsigned int i;struct ttm_mem_zone *zone; +unsigned int i;/* let the page allocator first stop the shrink work. */ ttm_page_alloc_fini ();
@@ -475,9 +475,10 @@ void ttm_mem_global_release(struct ttm_m zone = glob->zones[i];kobject_del (&zone->kobj);kobject_put (&zone->kobj); - } + }kobject_del (&glob->kobj);kobject_put (&glob->kobj); +memset (glob,0 ,sizeof (*glob)); }static void ttm_check_swapping (struct ttm_mem_global *glob)
include/drm/ttm/ttm_bo_driver.h +0 -1
@@ -411,7 +411,6 @@ extern struct ttm_bo_global {/** * Protected by ttm_global_mutex. */ -unsigned int use_count;struct list_head device_list;/**
Greg Kroah-Hartman
maintainerPATCH 38/89 dmaengine: sh: rcar-dmac: Fix glitch in dmaengine_tx_status
In reply to Greg Kroah-HartmanFrom: Achim Dahlhoff <[email protected]>
commit 6e7da74775348d96e2d7efaf3f91410e18c481ef upstream.
The tx_status poll in the rcar_dmac driver reads the status register which indicates which chunk is busy (DMACHCRB). Afterwards the point inside the chunk is read from DMATCRB. It is possible that the chunk has changed between the two reads. The result is a non-monotonous increase of the residue. Fix this by introducing a 'safe read' logic.
--- drivers/dma/sh/rcar-dmac.c | 26 +++++++++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-)
drivers/dma/sh/rcar-dmac.c +23 -3
@@ -1282,6 +1282,9 @@ static unsigned int rcar_dmac_chan_get_renum dma_status status;unsigned int residue =0 ;unsigned int dptr =0 ; +unsigned int chcrb; +unsigned int tcrb; +unsigned int i;if (!desc)return 0 ;
@@ -1330,14 +1333,31 @@ static unsigned int rcar_dmac_chan_get_r }/* +* We need to read two registers. +* Make sure the control register does not skip to next chunk +* while reading the counter. +* Trying it 3 times should be enough: Initial read, retry, retry +* for the paranoid. +*/ +for (i =0 ; i <3 ; i++) { + chcrb =rcar_dmac_chan_read (chan,RCAR_DMACHCRB ) & +RCAR_DMACHCRB_DPTR_MASK ; + tcrb =rcar_dmac_chan_read (chan,RCAR_DMATCRB ); +/* Still the same? */ +if (chcrb == (rcar_dmac_chan_read (chan,RCAR_DMACHCRB ) & +RCAR_DMACHCRB_DPTR_MASK )) +break ; + } +WARN_ONCE (i >=3 ,"residue might be not continuous!" ); + +/* * In descriptor mode the descriptor running pointer is not maintained * by the interrupt handler, find the running descriptor from the * descriptor pointer field in the CHCRB register. In non-descriptor * mode just use the running descriptor pointer. */ if (desc->hwdescs.use) { - dptr = (rcar_dmac_chan_read (chan,RCAR_DMACHCRB ) & -RCAR_DMACHCRB_DPTR_MASK ) >>RCAR_DMACHCRB_DPTR_SHIFT ; + dptr = chcrb >>RCAR_DMACHCRB_DPTR_SHIFT ;if (dptr ==0 ) dptr = desc->nchunks; dptr--;
@@ -1355,7 +1375,7 @@ static unsigned int rcar_dmac_chan_get_r }/* Add the residue for the current chunk. */ - residue +=rcar_dmac_chan_read (chan,RCAR_DMATCRB ) << desc->xfer_shift; + residue += tcrb << desc->xfer_shift;return residue; }
Greg Kroah-Hartman
maintainerPATCH 13/89 crypto: xts - Fix atomic sleep when walking skcipher
In reply to Greg Kroah-HartmanFrom: Herbert Xu <[email protected]>
commit 44427c0fbc09b448b22410978a4ef6ee37599d25 upstream.
When we perform a walk in the completion function, we need to ensure that it is atomic.
--- crypto/xts.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
crypto/xts.c +5 -1
@@ -137,8 +137,12 @@ static void crypt_done(struct crypto_asy {struct skcipher_request *req = areq->data; -if (!err) +if (!err) { +struct rctx *rctx =skcipher_request_ctx (req); + + rctx->subreq.base.flags &= ~CRYPTO_TFM_REQ_MAY_SLEEP ; err =xor_tweak_post (req); + }skcipher_request_complete (req, err); }
Greg Kroah-Hartman
maintainerPATCH 33/89 sunrpc: dont mark uninitialised items as VALID.
In reply to Greg Kroah-HartmanFrom: NeilBrown <[email protected]>
commit d58431eacb226222430940134d97bfd72f292fcd upstream.
A recent commit added a call to cache_fresh_locked() when an expired item was found.
The call sets the CACHE_VALID flag, so it is important that the item actually is valid.
There are two ways it could be valid:
1/ If ->update has been called to fill in relevant content 2/ if CACHE_NEGATIVE is set, to say that content doesn't exist.
An expired item that is waiting for an update will be neither. Setting CACHE_VALID will mean that a subsequent call to cache_put() will be likely to dereference uninitialised pointers.
So we must make sure the item is valid, and we already have code to do that in try_to_negate_entry(). This takes the hash lock and so cannot be used directly, so take out the two lines that we need and use them.
Now cache_fresh_locked() is certain to be called only on a valid item.
--- net/sunrpc/cache.c | 3 +++ 1 file changed, 3 insertions(+)
net/sunrpc/cache.c +3 -0
@@ -54,6 +54,7 @@ static void cache_init(struct cache_head h->last_refresh = now; } +static inline int cache_is_valid (struct cache_head *h);static void cache_fresh_locked (struct cache_head *head,time_t expiry,struct cache_detail *detail); static void cache_fresh_unlocked(struct cache_head *head,
@@ -105,6 +106,8 @@ static struct cache_head *sunrpc_cache_aif (cache_is_expired (detail, tmp)) {hlist_del_init_rcu (&tmp->cache_list); detail->entries --; +if (cache_is_valid (tmp) == -EAGAIN ) +set_bit (CACHE_NEGATIVE , &tmp->flags);cache_fresh_locked (tmp,0 , detail); freeme = tmp;break ;
Greg Kroah-Hartman
maintainerPATCH 35/89 Input: synaptics-rmi4 - write config register values to the right offset
In reply to Greg Kroah-HartmanFrom: Lucas Stach <[email protected]>
commit 3a349763cf11e63534b8f2d302f2d0c790566497 upstream.
Currently any changed config register values don't take effect, as the function to write them back is called with the wrong register offset.
sensors and F11)
--- drivers/input/rmi4/rmi_f11.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/input/rmi4/rmi_f11.c +1 -1
@@ -1230,7 +1230,7 @@ static int rmi_f11_initialize(struct rmi } rc =f11_write_control_regs (fn, &f11->sens_query, - &f11->dev_controls, fn->fd.query_base_addr); + &f11->dev_controls, fn->fd.control_base_addr);if (rc)dev_warn (&fn->dev,"Failed to write control registers\n" );
Greg Kroah-Hartman
maintainerPATCH 12/89 tracing: Fix buffer_ref pipe ops
In reply to Greg Kroah-HartmanFrom: Jann Horn <[email protected]>
commit b987222654f84f7b4ca95b3a55eca784cb30235b upstream.
This fixes multiple issues in buffer_pipe_buf_ops:
- The ->steal() handler must not return zero unless the pipe buffer has the only reference to the page. But generic_pipe_buf_steal() assumes that every reference to the pipe is tracked by the page's refcount, which isn't true for these buffers - buffer_pipe_buf_get(), which duplicates a buffer, doesn't touch the page's refcount.
Fix it by using generic_pipe_buf_nosteal(), which refuses every attempted theft. It should be easy to actually support ->steal, but the only current users of pipe_buf_steal() are the virtio console and FUSE, and they also only use it as an optimization. So it's probably not worth the effort.
- The ->get() and ->release() handlers can be invoked concurrently on pipe buffers backed by the same struct buffer_ref. Make them safe against concurrency by using refcount_t.
- The pointers stored in ->private were only zeroed out when the last reference to the buffer_ref was dropped. As far as I know, this shouldn't be necessary anyway, but if we do it, let's always do it.
--- fs/splice.c | 4 ++-- include/linux/pipe_fs_i.h | 1 + kernel/trace/trace.c | 28 ++++++++++++++-------------- 3 files changed, 17 insertions(+), 16 deletions(-)
fs/splice.c +2 -2
@@ -333,8 +333,8 @@ const struct pipe_buf_operations default .get = generic_pipe_buf_get, }; -static int generic_pipe_buf_nosteal (struct pipe_inode_info *pipe, -struct pipe_buffer *buf) +int generic_pipe_buf_nosteal (struct pipe_inode_info *pipe, +struct pipe_buffer *buf) {return 1 ; }
include/linux/pipe_fs_i.h +1 -0
@@ -181,6 +181,7 @@ void free_pipe_info(struct pipe_inode_invoid generic_pipe_buf_get (struct pipe_inode_info *,struct pipe_buffer *);int generic_pipe_buf_confirm (struct pipe_inode_info *,struct pipe_buffer *);int generic_pipe_buf_steal (struct pipe_inode_info *,struct pipe_buffer *); +int generic_pipe_buf_nosteal (struct pipe_inode_info *,struct pipe_buffer *);void generic_pipe_buf_release (struct pipe_inode_info *,struct pipe_buffer *);void pipe_buf_mark_unmergeable (struct pipe_buffer *buf);
kernel/trace/trace.c +14 -14
@@ -6823,19 +6823,23 @@ struct buffer_ref {struct ring_buffer *buffer;void *page;int cpu; -int ref; +refcount_t refcount; }; +static void buffer_ref_release (struct buffer_ref *ref) +{ +if (!refcount_dec_and_test (&ref->refcount)) +return ; +ring_buffer_free_read_page (ref->buffer, ref->cpu, ref->page); +kfree (ref); +} +static void buffer_pipe_buf_release (struct pipe_inode_info *pipe,struct pipe_buffer *buf) {struct buffer_ref *ref = (struct buffer_ref *)buf->private; -if (--ref->ref) -return ; - -ring_buffer_free_read_page (ref->buffer, ref->cpu, ref->page); -kfree (ref); +buffer_ref_release (ref); buf->private =0 ; }
@@ -6844,7 +6848,7 @@ static void buffer_pipe_buf_get(struct p {struct buffer_ref *ref = (struct buffer_ref *)buf->private; - ref->ref++; +refcount_inc (&ref->refcount); }/* Pipe buffer operations for a buffer. */
@@ -6852,7 +6856,7 @@ static const struct pipe_buf_operations .can_merge = 0, .confirm = generic_pipe_buf_confirm, .release = buffer_pipe_buf_release, - .steal = generic_pipe_buf_steal, + .steal = generic_pipe_buf_nosteal, .get = buffer_pipe_buf_get, };
@@ -6865,11 +6869,7 @@ static void buffer_spd_release(struct spstruct buffer_ref *ref = (struct buffer_ref *)spd->partial[i].private; -if (--ref->ref) -return ; - -ring_buffer_free_read_page (ref->buffer, ref->cpu, ref->page); -kfree (ref); +buffer_ref_release (ref); spd->partial[i].private =0 ; }
@@ -6924,7 +6924,7 @@ tracing_buffers_splice_read(struct filebreak ; } - ref->ref =1 ; +refcount_set (&ref->refcount,1 ); ref->buffer = iter->trace_buffer->buffer; ref->page =ring_buffer_alloc_read_page (ref->buffer, iter->cpu_file);if (IS_ERR (ref->page)) {
Greg Kroah-Hartman
maintainerPATCH 30/89 nfsd: Dont release the callback slot unless it was actually held
In reply to Greg Kroah-HartmanFrom: Trond Myklebust <[email protected]>
commit e6abc8caa6deb14be2a206253f7e1c5e37e9515b upstream.
If there are multiple callbacks queued, waiting for the callback slot when the callback gets shut down, then they all currently end up acting as if they hold the slot, and call nfsd4_cb_sequence_done() resulting in interesting side-effects.
In addition, the 'retry_nowait' path in nfsd4_cb_sequence_done() causes a loop back to nfsd4_cb_prepare() without first freeing the slot, which causes a deadlock when nfsd41_cb_get_slot() gets called a second time.
This patch therefore adds a boolean to track whether or not the callback did pick up the slot, so that it can do the right thing in these 2 cases.
--- fs/nfsd/nfs4callback.c | 8 +++++++- fs/nfsd/state.h | 1 + 2 files changed, 8 insertions(+), 1 deletion(-)
fs/nfsd/nfs4callback.c +7 -1
@@ -1023,8 +1023,9 @@ static void nfsd4_cb_prepare(struct rpc_ cb->cb_seq_status =1 ; cb->cb_status =0 ;if (minorversion) { -if (!nfsd41_cb_get_slot (clp, task)) +if (!cb->cb_holds_slot && !nfsd41_cb_get_slot (clp, task))return ; + cb->cb_holds_slot = true; }rpc_call_start (task); }
@@ -1051,6 +1052,9 @@ static bool nfsd4_cb_sequence_done(strucreturn true; } +if (!cb->cb_holds_slot) + goto need_restart; +switch (cb->cb_seq_status) {case 0 :/*
@@ -1089,6 +1093,7 @@ static bool nfsd4_cb_sequence_done(struc cb->cb_seq_status); } + cb->cb_holds_slot = false;clear_bit (0 , &clp->cl_cb_slot_busy);rpc_wake_up_next (&clp->cl_cb_waitq); dprintk("%s: freed slot, new seqid=%d\n", __func__,
@@ -1296,6 +1301,7 @@ void nfsd4_init_cb(struct nfsd4_callback cb->cb_seq_status =1 ; cb->cb_status =0 ; cb->cb_need_restart = false; + cb->cb_holds_slot = false; }void nfsd4_run_cb (struct nfsd4_callback *cb)
fs/nfsd/state.h +1 -0
@@ -70,6 +70,7 @@ struct nfsd4_callback {int cb_seq_status;int cb_status;bool cb_need_restart; +bool cb_holds_slot; };struct nfsd4_callback_ops {
Greg Kroah-Hartman
maintainerPATCH 29/89 ceph: fix ci->i_head_snapc leak
In reply to Greg Kroah-HartmanFrom: Yan, Zheng <[email protected]>
commit 37659182bff1eeaaeadcfc8f853c6d2b6dbc3f47 upstream.
We missed two places that i_wrbuffer_ref_head, i_wr_ref, i_dirty_caps and i_flushing_caps may change. When they are all zeros, we should free i_head_snapc.
--- fs/ceph/mds_client.c | 9 +++++++++ fs/ceph/snap.c | 7 ++++++- 2 files changed, 15 insertions(+), 1 deletion(-)
fs/ceph/mds_client.c +9 -0
@@ -1286,6 +1286,15 @@ static int remove_session_caps_cb(structlist_add (&ci->i_prealloc_cap_flush->i_list, &to_remove); ci->i_prealloc_cap_flush =NULL ; } + +if (drop && + ci->i_wrbuffer_ref_head ==0 && + ci->i_wr_ref ==0 && + ci->i_dirty_caps ==0 && + ci->i_flushing_caps ==0 ) { +ceph_put_snap_context (ci->i_head_snapc); + ci->i_head_snapc =NULL ; + } }spin_unlock (&ci->i_ceph_lock);while (!list_empty (&to_remove)) {
fs/ceph/snap.c +6 -1
@@ -568,7 +568,12 @@ void ceph_queue_cap_snap(struct ceph_ino old_snapc =NULL ; update_snapc: -if (ci->i_head_snapc) { +if (ci->i_wrbuffer_ref_head ==0 && + ci->i_wr_ref ==0 && + ci->i_dirty_caps ==0 && + ci->i_flushing_caps ==0 ) { + ci->i_head_snapc =NULL ; + }else { ci->i_head_snapc =ceph_get_snap_context (new_snapc);dout (" new snapc is %p\n" , new_snapc); }
Greg Kroah-Hartman
maintainerPATCH 25/89 RDMA/ucontext: Fix regression with disassociate
In reply to Greg Kroah-HartmanFrom: Jason Gunthorpe <[email protected]>
commit 67f269b37f9b4d52c5e7f97acea26c0852e9b8a1 upstream.
When this code was consolidated the intention was that the VMA would become backed by anonymous zero pages after the zap_vma_pte - however this very subtly relied on setting the vm_ops = NULL and clearing the VM_SHARED bits to transform the VMA into an anonymous VMA. Since the vm_ops was removed this broke.
Now userspace gets a SIGBUS if it touches the vma after disassociation.
Instead of converting the VMA to anonymous provide a fault handler that puts a zero'd page into the VMA when user-space touches it after disassociation.
--- drivers/infiniband/core/uverbs.h | 1 drivers/infiniband/core/uverbs_main.c | 52 ++++++++++++++++++++++++++++++++-- 2 files changed, 50 insertions(+), 3 deletions(-)
drivers/infiniband/core/uverbs.h +1 -0
@@ -160,6 +160,7 @@ struct ib_uverbs_file {struct mutex umap_lock;struct list_head umaps; +struct page *disassociate_page;struct idr idr;/* spinlock protects write access to idr */
drivers/infiniband/core/uverbs_main.c +49 -3
88 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 23/89 RDMA/mlx5: Do not allow the user to write to the clock page
In reply to Greg Kroah-HartmanFrom: Jason Gunthorpe <[email protected]>
commit c660133c339f9ab684fdf568c0d51b9ae5e86002 upstream.
The intent of this VMA was to be read-only from user space, but the VM_MAYWRITE masking was missed, so mprotect could make it writable.
--- drivers/infiniband/hw/mlx5/main.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/infiniband/hw/mlx5/main.c +2 -0
@@ -1982,6 +1982,7 @@ static int mlx5_ib_mmap_clock_info_page(if (vma->vm_flags &VM_WRITE )return -EPERM ; + vma->vm_flags &= ~VM_MAYWRITE ;if (!dev->mdev->clock_info_page)return -EOPNOTSUPP ;
@@ -2147,6 +2148,7 @@ static int mlx5_ib_mmap(struct ib_uconteif (vma->vm_flags &VM_WRITE )return -EPERM ; + vma->vm_flags &= ~VM_MAYWRITE ;/* Don't expose to user-space information it shouldn't have */ if (PAGE_SIZE >4096 )
Greg Kroah-Hartman
maintainerPATCH 21/89 arm64: mm: Ensure tail of unaligned initrd is reserved
In reply to Greg Kroah-HartmanFrom: Bjorn Andersson <[email protected]>
commit d4d18e3ec6091843f607e8929a56723e28f393a6 upstream.
In the event that the start address of the initrd is not aligned, but has an aligned size, the base + size will not cover the entire initrd image and there is a chance that the kernel will corrupt the tail of the image.
By aligning the end of the initrd to a page boundary and then subtracting the adjusted start address the memblock reservation will cover all pages that contains the initrd.
--- arch/arm64/mm/init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/mm/init.c +1 -1
@@ -406,7 +406,7 @@ void __init arm64_memblock_init(void)* Otherwise, this is a no-op */ u64 base = phys_initrd_start &PAGE_MASK ; -u64 size =PAGE_ALIGN (phys_initrd_size); +u64 size =PAGE_ALIGN (phys_initrd_start + phys_initrd_size) - base;/* * We can only add back the initrd memory if we don't end up
Greg Kroah-Hartman
maintainerPATCH 7/89 block, bfq: fix use after free in bfq_bfqq_expire
In reply to Greg Kroah-Hartman[ Upstream commit eed47d19d9362bdd958e4ab56af480b9dbf6b2b6 ]
The function bfq_bfqq_expire() invokes the function __bfq_bfqq_expire(), and the latter may free the in-service bfq-queue. If this happens, then no other instruction of bfq_bfqq_expire() must be executed, or a use-after-free will occur.
Basing on the assumption that __bfq_bfqq_expire() invokes bfq_put_queue() on the in-service bfq-queue exactly once, the queue is assumed to be freed if its refcounter is equal to one right before invoking __bfq_bfqq_expire().
But, since commit 9dee8b3b057e ("block, bfq: fix queue removal from weights tree") this assumption is false. __bfq_bfqq_expire() may also invoke bfq_weights_tree_remove() and, since commit 9dee8b3b057e ("block, bfq: fix queue removal from weights tree"), also the latter function may invoke bfq_put_queue(). So __bfq_bfqq_expire() may invoke bfq_put_queue() twice, and this is the actual case where the in-service queue may happen to be freed.
To address this issue, this commit moves the check on the refcounter of the queue right around the last bfq_put_queue() that may be invoked on the queue.
--- block/bfq-iosched.c | 15 +++++++-------- block/bfq-iosched.h | 2 +- block/bfq-wf2q.c | 17 +++++++++++++++-- 3 files changed, 23 insertions(+), 11 deletions(-)
block/bfq-iosched.c +7 -8
@@ -2804,7 +2804,7 @@ static void bfq_dispatch_remove(struct request_queue *q, struct request *rq)bfq_remove_request (q, rq); } -static void __bfq_bfqq_expire (struct bfq_data *bfqd,struct bfq_queue *bfqq) +static bool __bfq_bfqq_expire (struct bfq_data *bfqd,struct bfq_queue *bfqq) {/* * If this bfqq is shared between multiple processes, check
@@ -2837,9 +2837,11 @@ static void __bfq_bfqq_expire(struct bfq_data *bfqd, struct bfq_queue *bfqq)/* * All in-service entities must have been properly deactivated * or requeued before executing the next function, which -* resets all in-service entites as no more in service. +* resets all in-service entities as no more in service. This +* may cause bfqq to be freed. If this happens, the next +* function returns true. */ -__bfq_bfqd_reset_in_service (bfqd); +return __bfq_bfqd_reset_in_service (bfqd); }/**
@@ -3244,7 +3246,6 @@ void bfq_bfqq_expire(struct bfq_data *bfqd,bool slow;unsigned long delta =0 ;struct bfq_entity *entity = &bfqq->entity; -int ref;/* * Check whether the process is slow (see bfq_bfqq_is_slow).
@@ -3313,10 +3314,8 @@ void bfq_bfqq_expire(struct bfq_data *bfqd,* reason. */ __bfq_bfqq_recalc_budget (bfqd, bfqq, reason); - ref = bfqq->ref; -__bfq_bfqq_expire (bfqd, bfqq); - -if (ref ==1 )/* bfqq is gone, no more actions on it */ +if (__bfq_bfqq_expire (bfqd, bfqq)) +/* bfqq is gone, no more actions on it */ return ; bfqq->injected_service =0 ;
block/bfq-iosched.h +1 -1
@@ -993,7 +993,7 @@ bool __bfq_deactivate_entity(struct bfq_entity *entity, bool ins_into_idle_tree);bool next_queue_may_preempt (struct bfq_data *bfqd);struct bfq_queue *bfq_get_next_queue (struct bfq_data *bfqd); -void __bfq_bfqd_reset_in_service (struct bfq_data *bfqd); +bool __bfq_bfqd_reset_in_service (struct bfq_data *bfqd);void bfq_deactivate_bfqq (struct bfq_data *bfqd,struct bfq_queue *bfqq,bool ins_into_idle_tree,bool expiration);void bfq_activate_bfqq (struct bfq_data *bfqd,struct bfq_queue *bfqq);
block/bfq-wf2q.c +15 -2
@@ -1599,7 +1599,8 @@ struct bfq_queue *bfq_get_next_queue(struct bfq_data *bfqd)return bfqq; } -void __bfq_bfqd_reset_in_service (struct bfq_data *bfqd) +/* returns true if the in-service queue gets freed */ +bool __bfq_bfqd_reset_in_service (struct bfq_data *bfqd) {struct bfq_queue *in_serv_bfqq = bfqd->in_service_queue;struct bfq_entity *in_serv_entity = &in_serv_bfqq->entity;
@@ -1623,8 +1624,20 @@ void __bfq_bfqd_reset_in_service(struct bfq_data *bfqd)* service tree either, then release the service reference to * the queue it represents (taken with bfq_get_entity). */ -if (!in_serv_entity->on_st) +if (!in_serv_entity->on_st) { +/* +* If no process is referencing in_serv_bfqq any +* longer, then the service reference may be the only +* reference to the queue. If this is the case, then +* bfqq gets freed here. +*/ +int ref = in_serv_bfqq->ref;bfq_put_queue (in_serv_bfqq); +if (ref ==1 ) +return true; + } + +return false; } void bfq_deactivate_bfqq(struct bfq_data *bfqd, struct bfq_queue *bfqq,
Signature · 1 line
2.19.1
Greg Kroah-Hartman
maintainerPATCH 4/89 powerpc/vdso32: fix CLOCK_MONOTONIC on PPC64
In reply to Greg Kroah-Hartman[ Upstream commit dd9a994fc68d196a052b73747e3366c57d14a09e ]
Commit b5b4453e7912 ("powerpc/vdso64: Fix CLOCK_MONOTONIC inconsistencies across Y2038") changed the type of wtom_clock_sec to s64 on PPC64. Therefore, VDSO32 needs to read it with a 4 bytes shift in order to retrieve the lower part of it.
--- arch/powerpc/kernel/vdso32/gettimeofday.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/powerpc/kernel/vdso32/gettimeofday.S +1 -1
@@ -98,7 +98,7 @@ V_FUNCTION_BEGIN(__kernel_clock_gettime) * can be used, r7 contains NSEC_PER_SEC. */ - lwz r5,WTOM_CLOCK_SEC(r9) + lwz r5,(WTOM_CLOCK_SEC+LOPART)(r9) lwz r6,WTOM_CLOCK_NSEC(r9) /* We now have our offset in r5,r6. We create a fake dependency
Signature · 1 line
2.19.1
Greg Kroah-Hartman
maintainerPATCH 3/89 intel_th: gth: Fix an off-by-one in output unassigning
In reply to Greg Kroah-Hartman[ Upstream commit 91d3f8a629849968dc91d6ce54f2d46abf4feb7f ]
Commit 9ed3f22223c3 ("intel_th: Don't reference unassigned outputs") fixes a NULL dereference for all masters except the last one ("256+"), which keeps the stale pointer after the output driver had been unassigned.
Fix the off-by-one.
--- drivers/hwtracing/intel_th/gth.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwtracing/intel_th/gth.c +1 -1
@@ -616,7 +616,7 @@ static void intel_th_gth_unassign(struct intel_th_device *thdev, othdev->output.port =-1 ; othdev->output.active = false; gth->output[port].output =NULL ; -for (master =0 ; master <TH_CONFIGURABLE_MASTERS ; master++) +for (master =0 ; master <=TH_CONFIGURABLE_MASTERS ; master++)if (gth->master[master] == port) gth->master[master] =-1 ;spin_unlock (>h->gth_lock);
Signature · 1 line
2.19.1
Greg Kroah-Hartman
maintainerPATCH 2/89 netfilter: nf_tables: bogus EBUSY in helper removal from transaction
In reply to Greg Kroah-Hartman[ Upstream commit 8ffcd32f64633926163cdd07a7d295c500a947d1 ]
Proper use counter updates when activating and deactivating the object, otherwise, this hits bogus EBUSY error.
--- net/netfilter/nft_objref.c | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-)
net/netfilter/nft_objref.c +16 -3
@@ -64,21 +64,34 @@ nla_put_failure:return -1 ; } -static void nft_objref_destroy (const struct nft_ctx *ctx, -const struct nft_expr *expr) +static void nft_objref_deactivate (const struct nft_ctx *ctx, +const struct nft_expr *expr, +enum nft_trans_phase phase) {struct nft_object *obj =nft_objref_priv (expr); +if (phase ==NFT_TRANS_COMMIT ) +return ; + obj->use--; } +static void nft_objref_activate (const struct nft_ctx *ctx, +const struct nft_expr *expr) +{ +struct nft_object *obj =nft_objref_priv (expr); + + obj->use++; +} +static struct nft_expr_type nft_objref_type;static const struct nft_expr_ops nft_objref_ops = { .type = &nft_objref_type, .size =NFT_EXPR_SIZE (sizeof (struct nft_object *)), .eval = nft_objref_eval, .init = nft_objref_init, - .destroy = nft_objref_destroy, + .activate = nft_objref_activate, + .deactivate = nft_objref_deactivate, .dump = nft_objref_dump, };
Signature · 1 line
2.19.1
stable-rc/linux-5.0.y boot: 128 boots: 6 failed, 118 passed with 2 offline, 1 untried/unknown, 1 conflict (v5.0.10-90-g852cce372723)
stable-rc/linux-5.0.y boot: 128 boots: 6 failed, 118 passed with 2 offline, 1 untried/unknown, 1 conflict (v5.0.10-90-g852cce372723)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.0.y/kernel/v5.0.10-90-g852cce372723/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-5.0.y/kernel/v5.0.10-90-g852cce372723/
Tree: stable-rc
Branch: linux-5.0.y
Git Describe: v5.0.10-90-g852cce372723
Git Commit: 852cce372723872dc1e9f40fef3bcfd2b3215420
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 75 unique boards, 24 SoC families, 14 builds out of 208
Boot Regressions Detected:
arm64:
defconfig:
gcc-7:
hip07-d05:
lab-collabora: new failure (last pass: v5.0.10-72-g49e23c831c03)Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-7:
bcm4708-smartrg-sr400ac: 1 failed lab
bcm72521-bcm97252sffe: 1 failed lab
bcm7445-bcm97445c: 1 failed lab
sun4i-a10-cubieboard: 1 failed lab
sun7i-a20-cubietruck: 1 failed labarm64:
defconfig:
gcc-7:
hip07-d05: 1 failed labOffline Platforms:
arm:
multi_v7_defconfig:
gcc-7
stih410-b2120: 1 offline lab
sun7i-a20-bananapi: 1 offline labConflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig:
exynos5800-peach-pi:
lab-baylibre-seattle: FAIL (gcc-7)
lab-collabora: PASS (gcc-7)
---
For more info write to <[email protected]>
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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 Thu 02 May 2019 11:35:03 AM 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/v5.x/stable-review/patch-5.0.11-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.0.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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 Thu 02 May 2019 11:35:03 AM 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/v5.x/stable-review/patch-5.0.11-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.0.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: 5.0.11-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-5.0.y
git commit: 852cce372723872dc1e9f40fef3bcfd2b3215420
git describe: v5.0.10-90-g852cce372723
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.0-oe/build/v5.0.10-90-g852cce372723
No regressions (compared to build v5.0.10)
No fixes (compared to build v5.0.10)
Ran 24990 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c
- hi6220-hikey
- i386
- juno-r2
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15
- x86
Test Suites
-----------
* install-android-platform-tools-r2600
* kselftest
* libgpiod
* libhugetlbfs
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-cpuhotplug-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-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
* v4l2-compliance
* kvm-unit-tests
* ltp-cve-tests
* ltp-fs-tests
* spectre-meltdown-checker-test
* ltp-open-posix-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
* ssuite
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Greg Kroah-Hartman
maintainerQuoted 15 lines · shuah
Quoted 14 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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 Thu 02 May 2019 11:35:03 AM 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/v5.x/stable-review/patch-5.0.11-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.0.y
and the diffstat can be found below.
Quoted 6 lines
Quoted 4 lines
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
Thanks for testing all four of these and letting me know.
greg k-h
Greg Kroah-Hartman
maintainerQuoted 17 lines · Naresh Kamboju
Quoted 15 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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 Thu 02 May 2019 11:35:03 AM 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/v5.x/stable-review/patch-5.0.11-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.0.y
and the diffstat can be found below.
Quoted 7 lines
Quoted 4 lines
thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm,x86_64, and i386.
Thanks for testing all of these and letting me know.
greg k-h
Jon Hunter
maintainerQuoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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 Thu 02 May 2019 11:35:03 AM 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/v5.x/stable-review/patch-5.0.11-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.0.y
and the diffstat can be found below.thanks,
greg k-h
All tests are passing for Tegra ...
Test results for stable-v5.0:
12 builds: 12 pass, 0 fail
22 boots: 22 pass, 0 fail
32 tests: 32 pass, 0 failLinux version: 5.0.11-rc1-g852cce3
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04Cheers
Jon
Signature · 1 line
nvpublic
Greg Kroah-Hartman
maintainerQuoted 23 lines · Jon Hunter
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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 Thu 02 May 2019 11:35:03 AM 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/v5.x/stable-review/patch-5.0.11-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.0.y
and the diffstat can be found below.thanks,
greg k-h
All tests are passing for Tegra ...
Test results for stable-v5.0:
Quoted 8 lines
12 builds: 12 pass, 0 fail 22 boots: 22 pass, 0 fail 32 tests: 32 pass, 0 failLinux version: 5.0.11-rc1-g852cce3
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,tegra194-p2972-0000, tegra20-ventana, tegra210-p2371-2180, tegra30-cardhu-a04
Great! Thanks for testing all of these and letting me know.
greg k-h
Sasha Levin
maintainerRe: [PATCH 5.0 44/89] Revert "drm/i915/fbdev: Actually configure untiled displays"
In reply to Greg Kroah-HartmanQuoted 8 lines · Greg Kroah-Hartman
From: Dave Airlie <[email protected]>
commit
9fa246256e09dc30820524401cdbeeaadee94025upstream.This reverts commit
d179b88deb3bf6fed4991a31fd6f0f2cad21fab5.This commit is documented to break userspace X.org modesetting driver in certain configurations.
Quoted 8 lines
The X.org modesetting userspace driver is broken. No fixes are available yet. In order for this patch to be applied it either needs a config option or a workaround developed.
This has been reported a few times, saying it's a userspace problem is clearly against the regression rules.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109806
Signed-off-by Dave Airlie <[email protected]>Cc <[email protected]> # v3.19+Signed-off-by Greg Kroah-Hartman <[email protected]>
This commit has a follow-up fix as abbc0697d5fbf ("drm/fb: revert the i915 Actually configure untiled displays from master").
--
Thanks,
Sasha
Sasha Levin
maintainerRe: [PATCH 5.0 44/89] Revert "drm/i915/fbdev: Actually configure untiled displays"
Quoted 13 lines · Sasha Levin
Quoted 12 lines · Greg Kroah-Hartman
From: Dave Airlie <[email protected]>
commit
9fa246256e09dc30820524401cdbeeaadee94025upstream.This reverts commit
d179b88deb3bf6fed4991a31fd6f0f2cad21fab5.This commit is documented to break userspace X.org modesetting driver in certain configurations.
The X.org modesetting userspace driver is broken. No fixes are available yet. In order for this patch to be applied it either needs a config option or a workaround developed.
This has been reported a few times, saying it's a userspace problem is clearly against the regression rules.
Quoted 7 lines
Quoted 4 lines
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109806
Signed-off-by Dave Airlie <[email protected]>Cc <[email protected]> # v3.19+Signed-off-by Greg Kroah-Hartman <[email protected]>This commit has a follow-up fix as
abbc0697d5fbf("drm/fb: revert the i915 Actually configure untiled displays from master").
Uh, sorry, ignore that. I mixed stuff up. Not enough coffee.
--
Thanks,
Sasha
Greg Kroah-Hartman
maintainerRe: [PATCH 5.0 44/89] Revert "drm/i915/fbdev: Actually configure untiled displays"
In reply to Sasha LevinQuoted 13 lines · Sasha Levin
Quoted 12 lines · Greg Kroah-Hartman
From: Dave Airlie <[email protected]>
commit
9fa246256e09dc30820524401cdbeeaadee94025upstream.This reverts commit
d179b88deb3bf6fed4991a31fd6f0f2cad21fab5.This commit is documented to break userspace X.org modesetting driver in certain configurations.
The X.org modesetting userspace driver is broken. No fixes are available yet. In order for this patch to be applied it either needs a config option or a workaround developed.
This has been reported a few times, saying it's a userspace problem is clearly against the regression rules.
Quoted 7 lines
Quoted 4 lines
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109806
Signed-off-by Dave Airlie <[email protected]>Cc <[email protected]> # v3.19+Signed-off-by Greg Kroah-Hartman <[email protected]>This commit has a follow-up fix as
abbc0697d5fbf("drm/fb: revert the i915 Actually configure untiled displays from master").
I don't see that commit in Linus's tree, where did you find it?
confused,
greg k-h
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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 Thu 02 May 2019 11:35:03 AM UTC. Anything received after that time might be too late.
Build results:
total: 159 pass: 159 fail: 0 Qemu test results: total: 349 pass: 349 fail: 0
Guenter
Greg Kroah-Hartman
maintainerQuoted 6 lines · Guenter Roeck
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.0.11 release. There are 89 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
Quoted 3 lines
Responses should be made by Thu 02 May 2019 11:35:03 AM UTC. Anything received after that time might be too late.
Build results:
total: 159 pass: 159 fail: 0 Qemu test results: total: 349 pass: 349 fail: 0
Wonderful, thanks for testing all of these and letting me know.
greg k-h
Built and booted on my x86 machine. No dmesg regression.
Greg Kroah-Hartman
maintainerQuoted 1 line · Bharath Vedartham
Built and booted on my x86 machine. No dmesg regression.
Thanks for testing two of these and letting me know.
greg k-h
Re: [PATCH 5.0 25/89] RDMA/ucontext: Fix regression with disassociate
In reply to Greg Kroah-HartmanQuoted 24 lines · Greg Kroah-Hartman
From: Jason Gunthorpe <[email protected]>
commit
67f269b37f9b4d52c5e7f97acea26c0852e9b8a1upstream.When this code was consolidated the intention was that the VMA would become backed by anonymous zero pages after the
zap_vma_pte- however this very subtly relied on setting thevm_ops= NULL and clearing theVM_SHAREDbits to transform the VMA into an anonymous VMA. Since thevm_opswas removed this broke.Now userspace gets a SIGBUS if it touches the vma after disassociation.
Instead of converting the VMA to anonymous provide a fault handler that puts a zero'd page into the VMA when user-space touches it after disassociation.
Suggested-by Andrea Arcangeli <[email protected]>Fixes 5f9794dc94f5 ("RDMA/ucontext: Add a core API for mmaping driver IO memory")Signed-off-by Jason Gunthorpe <[email protected]>Signed-off-by Leon Romanovsky <[email protected]>Signed-off-by Jason Gunthorpe <[email protected]>Signed-off-by Greg Kroah-Hartman <[email protected]>
Quoted 1 line
---
This commit breaks build on s390 and mips, please pick also commit 6a5c5d26c4c6 ("rdma: fix build errors on s390 and MIPS due to bad ZERO_PAGE use").
Michal Kubecek
Re: [PATCH 5.0 25/89] RDMA/ucontext: Fix regression with disassociate
Quoted 25 lines · Michal Kubecek
Quoted 24 lines · Greg Kroah-Hartman
From: Jason Gunthorpe <[email protected]>
commit
67f269b37f9b4d52c5e7f97acea26c0852e9b8a1upstream.When this code was consolidated the intention was that the VMA would become backed by anonymous zero pages after the
zap_vma_pte- however this very subtly relied on setting thevm_ops= NULL and clearing theVM_SHAREDbits to transform the VMA into an anonymous VMA. Since thevm_opswas removed this broke.Now userspace gets a SIGBUS if it touches the vma after disassociation.
Instead of converting the VMA to anonymous provide a fault handler that puts a zero'd page into the VMA when user-space touches it after disassociation.
Suggested-by Andrea Arcangeli <[email protected]>Fixes 5f9794dc94f5 ("RDMA/ucontext: Add a core API for mmaping driver IO memory")Signed-off-by Jason Gunthorpe <[email protected]>Signed-off-by Leon Romanovsky <[email protected]>Signed-off-by Jason Gunthorpe <[email protected]>Signed-off-by Greg Kroah-Hartman <[email protected]>
Quoted 5 lines
Quoted 1 line
---
This commit breaks build on s390 and mips, please pick also commit
6a5c5d26c4c6("rdma: fix build errors on s390 and MIPS due to badZERO_PAGEuse").
Oops, it's already there as 71/89, I managed to overlook it. Sorry for the noise.
Michal Kubecek