linux-kernel - sk_stream_wait

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 for Android: free password hash cracker in your pocket

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

Message-ID: <e42309110908260644y65d87fc2q54405ef95be0caaf@mail.gmail.com>
Date:	Wed, 26 Aug 2009 19:14:23 +0530
From:	Ravish Tayal <ravish.tayal@...il.com>
To:	linux-arm@...r.kernel.org,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: sk_stream_wait_memory: Query

Hi,

In " tcp_sendmsg" function in 2 situation, tcp code attempts to jump
to "wait_for_memory:
" case when
1. it fails to allocate to the new skb  [sk_stream_alloc_pskb failure]
2. it fails to allocate new cache page.

and invokes the sk_stream_wait_memory function.

inside which it invokes the
  sk_wait_event(sk, &current_timeo, sk_stream_memory_free(sk) &&
vm_wait);

in case if sk_stream_wait_memory is invoked due to skb allocation
failure, it would busy loop and would not relinquish the control.
[For non-preemptive kernel]

Is it fair expectation, or even this case it should let it current
task get scheduled and re try after timer expiry.

regards
Ravish Tayal

in the case if linux kernel is configured as non-premeptive
--
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/