)]}'
{
  "log": [
    {
      "commit": "3b885787ea4112eaa80945999ea0901bf742707f",
      "tree": "06fc15f8e8083d5652ccb4d06653d9812dce9c0b",
      "parents": [
        "d5e63bded6e819ca77ee1a1d97c783a31f6caf30"
      ],
      "author": {
        "name": "Neil Horman",
        "email": "nhorman@tuxdriver.com",
        "time": "Mon Oct 12 13:26:31 2009 -0700"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon Oct 12 13:26:31 2009 -0700"
      },
      "message": "net: Generalize socket rx gap / receive queue overflow cmsg\n\nCreate a new socket level option to report number of queue overflows\n\nRecently I augmented the AF_PACKET protocol to report the number of frames lost\non the socket receive queue between any two enqueued frames.  This value was\nexported via a SOL_PACKET level cmsg.  AFter I completed that work it was\nrequested that this feature be generalized so that any datagram oriented socket\ncould make use of this option.  As such I\u0027ve created this patch, It creates a\nnew SOL_SOCKET level option called SO_RXQ_OVFL, which when enabled exports a\nSOL_SOCKET level cmsg that reports the nubmer of times the sk_receive_queue\noverflowed between any two given frames.  It also augments the AF_PACKET\nprotocol to take advantage of this new feature (as it previously did not touch\nsk-\u003esk_drops, which this patch uses to record the overflow count).  Tested\nsuccessfully by me.\n\nNotes:\n\n1) Unlike my previous patch, this patch simply records the sk_drops value, which\nis not a number of drops between packets, but rather a total number of drops.\nDeltas must be computed in user space.\n\n2) While this patch currently works with datagram oriented protocols, it will\nalso be accepted by non-datagram oriented protocols. I\u0027m not sure if thats\nagreeable to everyone, but my argument in favor of doing so is that, for those\nprotocols which aren\u0027t applicable to this option, sk_drops will always be zero,\nand reporting no drops on a receive queue that isn\u0027t used for those\nnon-participating protocols seems reasonable to me.  This also saves us having\nto code in a per-protocol opt in mechanism.\n\n3) This applies cleanly to net-next assuming that commit\n977750076d98c7ff6cbda51858bb5a5894a9d9ab (my af packet cmsg patch) is reverted\n\nSigned-off-by: Neil Horman \u003cnhorman@tuxdriver.com\u003e\nSigned-off-by: Eric Dumazet \u003ceric.dumazet@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "0d6038ee76f2e06b79d0465807f67e86bf4025de",
      "tree": "ffb88e2f817ae2a76fece58a7f7d0de3fd37fbaf",
      "parents": [
        "49c794e94649020248e37b78db16cd25bad38b4f"
      ],
      "author": {
        "name": "Jan Engelhardt",
        "email": "jengelh@medozas.de",
        "time": "Tue Aug 04 07:28:29 2009 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Wed Aug 05 13:02:57 2009 -0700"
      },
      "message": "net: implement a SO_DOMAIN getsockoption\n\nThis sockopt goes in line with SO_TYPE and SO_PROTOCOL. It makes it\npossible for userspace programs to pass around file descriptors — I\nam referring to arguments-to-functions, but it may even work for the\nfd passing over UNIX sockets — without needing to also pass the\nauxiliary information (PF_INET6/IPPROTO_TCP).\n\nSigned-off-by: Jan Engelhardt \u003cjengelh@medozas.de\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "49c794e94649020248e37b78db16cd25bad38b4f",
      "tree": "76c455522d37fa0fa88c7466bb494523cb320fab",
      "parents": [
        "c1c00ab8626298ac784ea344bf10e94b5bd9bcb5"
      ],
      "author": {
        "name": "Jan Engelhardt",
        "email": "jengelh@medozas.de",
        "time": "Tue Aug 04 07:28:28 2009 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Wed Aug 05 13:02:56 2009 -0700"
      },
      "message": "net: implement a SO_PROTOCOL getsockoption\n\nSimilar to SO_TYPE returning the socket type, SO_PROTOCOL allows to\nretrieve the protocol used with a given socket.\n\nI am not quite sure why we have that-many copies of socket.h, and why\nthe values are not the same on all arches either, but for where hex\nnumbers dominate, I use 0x1029 for SO_PROTOCOL as that seems to be\nthe next free unused number across a bunch of operating systems, or\nso Google results make me want to believe. SO_PROTOCOL for others\njust uses the next free Linux number, 38.\n\nSigned-off-by: Jan Engelhardt \u003cjengelh@medozas.de\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "6103ec56c65c33774c7c38652c8204120c3c7519",
      "tree": "5d510da8f5aeb46b796a27192b04eec99d375886",
      "parents": [
        "2864d32be31a20a4617e37a857dd9915a57e2efb"
      ],
      "author": {
        "name": "Arnd Bergmann",
        "email": "arnd@arndb.de",
        "time": "Wed May 13 22:56:27 2009 +0000"
      },
      "committer": {
        "name": "Arnd Bergmann",
        "email": "arnd@klappe2.(none)",
        "time": "Thu Jun 11 21:02:15 2009 +0200"
      },
      "message": "asm-generic: add generic ABI headers\n\nThese header files are typically copied from an existing architecture\ninto any new one, slightly modified and then remain untouched until\nthe end of time in the name of ABI stability.\n\nTo make it easier for future architectures, provide a sane generic\nversion here. In cases where multiple architectures already use\nidentical code, I used the most common version. In cases like\nstat.h that are more or less broken everywhere, I provide a\nversion that is meant to be ideal for new architectures.\n\nSigned-off-by: Remis Lima Baima \u003cremis.developer@googlemail.com\u003e\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\n"
    }
  ]
}