All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, Masahide NAKAMURA <nakam@linux-ipv6.org>
Subject: [PATCH] [XFRM] Fix XFRMGRP_REPORT to use correct multicast group
Date: Thu, 07 Dec 2006 19:14:58 -0500	[thread overview]
Message-ID: <1165536898.3666.3.camel@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 103 bytes --]


Against net-2.6 but should probably go into anything stable that has
reports already.

cheers,
jamal


[-- Attachment #2: xfrm_repg_fix --]
[-- Type: text/plain, Size: 1088 bytes --]

[XFRM] Fix XFRMGRP_REPORT to use correct multicast group

XFRMGRP_REPORT uses 0x10 which is a group that belongs
to events. The correct value is 0x20.
We should really be using xfrm_nlgroups going forward; it was tempting
to delete the definition of XFRMGRP_REPORT but it would break at
least iproute2.

Signed-off-by: J Hadi Salim <hadi@cyberus.ca>

---
commit 5229df1f9249e3b509ff426a74f4192b60ad6760
tree 4bb9548261165e1e0a907a6e3768e28b90794cc4
parent 03b09fc1e8f71a14c661af496941b6de963fddf1
author Jamal Hadi Salim <hadi@cyberus.ca> Thu, 07 Dec 2006 19:08:58 -0500
committer Jamal Hadi Salim <hadi@cyberus.ca> Thu, 07 Dec 2006 19:08:58 -0500

 include/linux/xfrm.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/include/linux/xfrm.h b/include/linux/xfrm.h
index 7907c42..5227603 100644
--- a/include/linux/xfrm.h
+++ b/include/linux/xfrm.h
@@ -355,7 +355,7 @@ struct xfrm_user_report {
 #define XFRMGRP_EXPIRE		2
 #define XFRMGRP_SA		4
 #define XFRMGRP_POLICY		8
-#define XFRMGRP_REPORT		0x10
+#define XFRMGRP_REPORT		0x20
 #endif
 
 enum xfrm_nlgroups {

             reply	other threads:[~2006-12-08  0:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08  0:14 jamal [this message]
2006-12-08  8:12 ` [PATCH] [XFRM] Fix XFRMGRP_REPORT to use correct multicast group David Miller

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=1165536898.3666.3.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=davem@davemloft.net \
    --cc=nakam@linux-ipv6.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.