Displaying 6 results from an estimated 6 matches for "unix_stream_sendmsg".
2005 Nov 09
1
kernel BUG at arch/xen/i386/mm/hypervisor.c:354, (xen_create _contiguous_region)!
...b6>Ü cache_alloc_refill+0x226/0x260
Ä<c014e14c>Ü kmem_cache_alloc+0x9c/0xb0
Ä<c02601cd>Ü alloc_skb_from_cache+0x4d/0x100
Ä<c01071cb>Ü alloc_skb+0x9b/0xc0
Ä<c025ee90>Ü sock_alloc_send_pskb+0xc0/0x1d0
Ä<c025efcd>Ü sock_alloc_send_skb+0x2d/0x40
Ä<c02aff19>Ü unix_stream_sendmsg+0x199/0x470
Ä<c02c52a2>Ü schedule+0x3f2/0x780
Ä<c025be31>Ü sock_aio_write+0x101/0x120
Ä<c01778df>Ü pipe_wait+0x8f/0xb0
Ä<c0169c39>Ü do_sync_write+0xc9/0x110
Ä<c0177c0a>Ü pipe_readv+0x2ba/0x360
Ä<c0139200>Ü autoremove_wake_function+0x0/0x60
Ä<c0199c9a>...
2023 Aug 31
0
[RFC PATCH v2 0/2] vsock: handle writes to shutdowned socket
...gt;SIGPIPE in such cases (but SIGPIPE is not send when MSG_NOSIGNAL is set).
>
>First patch is implemented in the same way as net/ipv4/tcp.c:tcp_sendmsg_locked().
>It uses 'sk_stream_error()' function which handles EPIPE error. Another
>way is to use code from net/unix/af_unix.c:unix_stream_sendmsg() where
>same logic from 'sk_stream_error()' is implemented "from scratch", but
>it doesn't check 'sk_err' field. I think error from this field has more
>priority to be returned from syscall. So I guess it is better to reuse
>currently implemented 'sk_s...
2015 Nov 07
7
[Bug 92852] New: NV34: WARNING: ... at drivers/gpu/drm/drm_irq.c:924 drm_vblank_count_and_time+0x71/0x80 [drm]()
...] ? check_preempt_wakeup+0xe8/0x220
[<c05c6ea0>] ? poll_select_copy_remaining+0x130/0x130
[<c09ae2f8>] ? __alloc_skb+0x78/0x1e0
[<c05cf282>] ? __fdget+0x12/0x20
[<c09a6684>] ? __sys_recvmsg+0x44/0x80
[<c09a70ae>] ? SYSC_socketcall+0x7ae/0x9c0
[<c0a68718>] ? unix_stream_sendmsg+0x358/0x380
[<c09a514d>] ? sock_sendmsg+0x2d/0x40
[<c05b4a60>] ? do_readv_writev+0x140/0x350
[<c04cb81a>] ? ktime_get+0x4a/0x120
[<c09a5160>] ? sock_sendmsg+0x40/0x40
[<c04f857f>] ? __audit_syscall_entry+0xaf/0x110
[<c04012a4>] ? do_audit_syscall_entry.isra...
2005 Jun 04
11
kernel oops/IRQ exception when networking between many domUs
Hi,
I try to build experimental networks with Xen and stumbled over the same
problem that has been described quite well by Mark Doll in his posting
"xen_net: Failed to connect all virtual interfaces: err=-100"
here:
http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html
As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS
and NR_DYNIRQS had been
2005 Jun 04
11
kernel oops/IRQ exception when networking between many domUs
Hi,
I try to build experimental networks with Xen and stumbled over the same
problem that has been described quite well by Mark Doll in his posting
"xen_net: Failed to connect all virtual interfaces: err=-100"
here:
http://lists.xensource.com/archives/html/xen-users/2005-04/msg00447.html
As it was still present in 2.0.6, I tried 3.0-devel and found NR_PIRQS
and NR_DYNIRQS had been
2013 Sep 05
4
Bug#721946: xen-hypervisor-4.1-amd64: dom0_mem cannot exceed some value
...estore+0x7/0x8
Sep 5 18:03:46 pcale kernel: [ 1017.376418] [<ffffffff8134eb77>] ? _raw_spin_unlock_irqrestore+0xe/0xf
Sep 5 18:03:46 pcale kernel: [ 1017.376421] [<ffffffff81097a6e>] ? delayacct_end+0x72/0x7d
Sep 5 18:03:46 pcale kernel: [ 1017.376425] [<ffffffff812f9bbe>] ? unix_stream_sendmsg+0x11c/0x2c4
Sep 5 18:03:46 pcale kernel: [ 1017.376428] [<ffffffff8134de00>] ? out_of_line_wait_on_bit_lock+0x2/0x78
Sep 5 18:03:46 pcale kernel: [ 1017.376432] [<ffffffff8127e462>] ? sock_aio_write+0x121/0x135
Sep 5 18:03:46 pcale kernel: [ 1017.376436] [<ffffffff810072e8>]...