linux-kernel - Re: Suspected sock_sendmsg() with MSG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 24 Feb 2009 16:54:30 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Parav Pandit <paravpandit@...oo.com>
Cc:	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: Suspected sock_sendmsg() with MSG_DONTWAIT can block bug.

Parav Pandit <paravpandit@...oo.com> writes:

> Short quick question:
> ---------------------
> If sock_sendmsg() is calls with MSG_DONTWAIT, it should send the packet without blocking the context or fail the call with error value.

It is allowed to fail with errors.

> Which means sock_sendmsg() with MSG_DONTWAIT can be called from soft-irq/ interrupt ctx.
> Is that correct?

No. It can still block for memory for example. Also there's no irq locking
in place Irq context is not allowed. MSG_DONTWAIT just means don't block
on buffer space or connection finish.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/