search for: enetdown

...ype); } - spin_unlock_bh(&priv->j1939_socks_lock); + read_unlock_bh(&priv->j1939_socks_lock); }; void j1939_sk_send_loop_abort(struct sock *sk, int err) @@ -1271,7 +1272,7 @@ void j1939_sk_netdev_event_netdown(struct j1939_priv *priv) struct j1939_sock *jsk; int error_code = ENETDOWN; - spin_lock_bh(&priv->j1939_socks_lock); + read_lock_bh(&priv->j1939_socks_lock); list_for_each_entry(jsk, &priv->j1939_socks, list) { jsk->sk.sk_err = error_code; if (!sock_flag(&jsk->sk, SOCK_DEAD)) @@ -1279,7 +1280,7 @@ void j1939_sk_netdev_event_netdown...

...llvm/include/llvm/Support/system_error.h:534: error: ‘EISDIR’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:535: error: ‘EMSGSIZE’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:536: error: ‘ENETDOWN’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:537: error: ‘ENETRESET’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:538: error: ‘ENETUNREACH’ was not declared in this scope /home/carl/Down...

...= 0) { @@ -1287,6 +1349,11 @@ newsock = accept(listen_socks[i], (struct sockaddr *)&from, &fromlen); if (newsock < 0) { +#if #system(bs2000) + /* There is not much use in looping after the network layer has been brought down... Die gracefully. */ + if (errno == ENETDOWN) + fatal("accept: %.100s", strerror(errno)); +#endif if (errno != EINTR && errno != EWOULDBLOCK) error("accept: %.100s", strerror(errno)); continue; diff -bur openssh-3.7.1p2.orig/ttymodes.c openssh-3.7.1p2/ttymodes.c --- openssh-3.7.1p2.orig/ttym...

Looks like the GSO is involved? I got this while running Dom0 only (no guests), with a BOINC/Rosetta@home application running on all 4 cores. changeset: 10649:8e55c5c11475 Build: x86_32p (pae). ------------[ cut here ]------------ kernel BUG at net/core/dev.c:1133! invalid opcode: 0000 [#1] SMP CPU: 0 EIP: 0061:[<c04dceb0>] Not tainted VLI EFLAGS: 00210297 (2.6.16.13-xen

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw This is the port to Windows using native Windows APIs (not MSYS or Cygwin). This patch series is at the point where it basically now works. I can run the server with the memory plugin, and access it remotely using guestfish, creating filesystems and so on without any apparent problems. Nevertheless there are many

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw-nolib After a lot of work I have made the port to Windows work without using a separate library. Instead, on Windows only, we build an "import library" (library of stubs) which resolves references to nbdkit_* functions in the main program and fixes up the plugin, basically the first technique outlined in

...ed on transport endpoint" EPFNOSUPPORT (96) => "Protocol family not supported" EAFNOSUPPORT (97) => "Address family not supported by protocol" EADDRINUSE (98) => "Address already in use" EADDRNOTAVAIL (99) => "Cannot assign requested address" ENETDOWN (100) => "Network is down" ENETUNREACH (101) => "Network is unreachable" ENETRESET (102) => "Network dropped connection because of reset" ECONNABORTED (103) => "Software caused connection abort" ECONNRESET (104) => "Connection reset by pee...

On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > > > Find attached two patches I have in order to build klibc 2.0.2 > against kernel 3.8.13 > We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > Hope it helps. > those patches are wrong and again very brittle. just use the way it is described in `make help': A) cd ~/src/linux