From: David Miller <davem@davemloft.net>
To: acme@redhat.com
Cc: gerrit@erg.abdn.ac.uk, dccp@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] dccp_diag: LISTEN sockets don't have CCIDs
Date: Wed, 17 Dec 2008 16:08:19 -0800 (PST) [thread overview]
Message-ID: <20081217.160819.99264095.davem@davemloft.net> (raw)
In-Reply-To: <20081217200332.GY14518@ghostprotocols.net>
From: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Wed, 17 Dec 2008 18:03:32 -0200
> And thus when we try to use 'ss -danemi' on these sockets that have no
> ccid blocks (data collected using systemtap after I fixed the problem):
>
> dccp_diag_get_info sk=0xffff8801220a3100, dp->dccps_hc_rx_ccid=0x0000000000000000, dp->dccps_hc_tx_ccid=0x0000000000000000
>
> We get an OOPS:
...
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Applied to net-next-2.6, thanks!
prev parent reply other threads:[~2008-12-18 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 20:03 [PATCH] dccp_diag: LISTEN sockets don't have CCIDs Arnaldo Carvalho de Melo
2008-12-18 0:08 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081217.160819.99264095.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@redhat.com \
--cc=dccp@vger.kernel.org \
--cc=gerrit@erg.abdn.ac.uk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).