Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux 5.19.16 #183

Closed
wants to merge 0 commits into from
Closed

Linux 5.19.16 #183

wants to merge 0 commits into from

Conversation

jackpot51
Copy link
Member

@jackpot51 jackpot51 requested review from a team October 17, 2022 13:48
@jackpot51 jackpot51 self-assigned this Oct 17, 2022
13r0ck
13r0ck previously approved these changes Oct 17, 2022
@leviport
Copy link
Member

Looks like this breaks k10temp stuff on zen4

@13r0ck 13r0ck self-requested a review October 17, 2022 21:10
13r0ck
13r0ck previously approved these changes Oct 17, 2022
@leviport
Copy link
Member

Bluetooth and wifi both look fine on Pop and Ubuntu with this kernel though, so that's good.

@n3m0-22
Copy link

n3m0-22 commented Oct 17, 2022

Same dkms issues for VirtualBox and bcmwl-kernel-source as noted in #182.

@n3m0-22
Copy link

n3m0-22 commented Oct 18, 2022

VirtualBox 6.1.36 and VirtualBox 7.0.0 are now both running. There is an error when upgrading from 6 to 7 Conflicts with the installed package 'virtualbox-qt'. Uninstalling VirtualBox 6 before installing VirtualBox 7 resolves gets around this without breaking VMs created in version 6. Extension and Guest Additions also upgrade to version 7 without issue.

Also bcmwl-kernel-source is now installing.

@leviport
Copy link
Member

Looks like Nvidia DKMS stuff is good with 515, 510, and 470

@XV-02
Copy link

XV-02 commented Oct 18, 2022

I'm seeing an issue with bluetooth on Lemp9. Bluetooth devices are not being found, and as such cannot be connected to. The bluetooth settings panel just shows bluetooth as constantly searching. Checking lemp11 right now for a comparison

This is not a regression tied to kernel update. OldKern shows the same behaviour

Copy link
Member

@leviport leviport left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The k10temp commit has some issues. I'd revert that one, but otherwise this is good to go.

@jackpot51 jackpot51 closed this Oct 18, 2022
@jackpot51 jackpot51 deleted the linux-5.19.16 branch October 18, 2022 19:36
mmstick pushed a commit that referenced this pull request Mar 28, 2024
[ Upstream commit f7b94bd ]

Attemting to do sock_lock on .recvmsg may cause a deadlock as shown
bellow, so instead of using sock_sock this uses sk_receive_queue.lock
on bt_sock_ioctl to avoid the UAF:

INFO: task kworker/u9:1:121 blocked for more than 30 seconds.
      Not tainted 6.7.6-lemon #183
Workqueue: hci0 hci_rx_work
Call Trace:
 <TASK>
 __schedule+0x37d/0xa00
 schedule+0x32/0xe0
 __lock_sock+0x68/0xa0
 ? __pfx_autoremove_wake_function+0x10/0x10
 lock_sock_nested+0x43/0x50
 l2cap_sock_recv_cb+0x21/0xa0
 l2cap_recv_frame+0x55b/0x30a0
 ? psi_task_switch+0xeb/0x270
 ? finish_task_switch.isra.0+0x93/0x2a0
 hci_rx_work+0x33a/0x3f0
 process_one_work+0x13a/0x2f0
 worker_thread+0x2f0/0x410
 ? __pfx_worker_thread+0x10/0x10
 kthread+0xe0/0x110
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x2c/0x50
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1b/0x30
 </TASK>

Fixes: 2e07e83 ("Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg")
Signed-off-by: Luiz Augusto von Dentz <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants