netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 198353] New: Generic netlink family bug when multicast groups are greater than 13
Date: Thu, 4 Jan 2018 16:30:45 -0800	[thread overview]
Message-ID: <20180104163045.2dfee077@xeon-e3> (raw)



Begin forwarded message:

Date: Fri, 05 Jan 2018 00:21:42 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 198353] New: Generic netlink family bug when multicast groups are greater than 13


https://bugzilla.kernel.org/show_bug.cgi?id=198353

            Bug ID: 198353
           Summary: Generic netlink family bug when multicast groups are
                    greater than 13
           Product: Networking
           Version: 2.5
    Kernel Version: 4.4
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: jaipal.katkuri@itron.com
        Regression: No

Created attachment 273405
  --> https://bugzilla.kernel.org/attachment.cgi?id=273405&action=edit  
linux-4.4-netlink-genlmcgroup.patch

Kernel Version: 4.4
File: netlink/genetlink.c

While reserving multicast groups for a netlink family in the kernel, if the
request has more than 13 groups the code allocates only 13 groups and returns
success.

In the function "genl_allocate_reserve_groups" the variable "id" is returned
with the first available multicast group slot but it doesn't check if the
request "n_groups" is more than 13.

Attached patch fixes the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-01-05  0:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180104163045.2dfee077@xeon-e3 \
    --to=stephen@networkplumber.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 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).