summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2026-08-24 14:08:19 +0200
committerChristian Brauner <brauner@kernel.org>2026-08-31 10:05:13 +0200
commitd0ae35565f5d588b5912e0a5355ada4ca72d2c02 (patch)
treefc119b0226b4903f08c3e3b6bba8c918782aa69b /tools/lib/python
parent7ac8d57a436c84a67effd3ba0bb7ec7017b385bc (diff)
downloadlinux-next-d0ae35565f5d588b5912e0a5355ada4ca72d2c02.tar.gz
linux-next-d0ae35565f5d588b5912e0a5355ada4ca72d2c02.zip
smb: prevent TIF_NOTIFY_SIGNAL from interrupting
smb blocks every signal during some sends: sigfillset(&mask); sigprocmask(SIG_BLOCK, &mask, &oldmask); An incomplete or partial send would cause the connection to become out of sync. That in turn would cause the session to be torn down and reconnected. In commit 00be6f26a2a7 ("smb: client: transport: avoid reconnects triggered by pending task work") smb hand-rolled its own solution. Have it use the new no_notify_signal_save() critical section instead. This stops io_uring from cancelling a send in flight but that's just like it is today and it is bounded by sk_sndtimeo at around 15s. Link: https://patch.msgid.link/20260824-work-tif_notify_signal-v2-4-6609e42b3157@kernel.org Acked-by: Paulo Alcantara <pc@manguebit.org> Reviewed-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions