netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ubraun@linux.vnet.ibm.com
Cc: mschwid2@linux.vnet.ibm.com, heicars2@linux.vnet.ibm.com,
	netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	ubraunu@linux.vnet.ibm.com
Subject: Re: [PATCH net 0/1] af_iucv: Validate socket address length in iucv_sock_bind()
Date: Tue, 19 Jan 2016 14:23:57 -0500 (EST)	[thread overview]
Message-ID: <20160119.142357.829571599757607853.davem@davemloft.net> (raw)
In-Reply-To: <1453196493-57590-1-git-send-email-ubraun@linux.vnet.ibm.com>

From: Ursula Braun <ubraun@linux.vnet.ibm.com>
Date: Tue, 19 Jan 2016 10:41:32 +0100

> this patch fixes a problem reported by Dmitry Vyukov in december. It is built
> and intended for the next-tree.

A bug fix is not appropriate for the next tree.

All bug fixes should target 'net'.  You even contacted me privately
asking me to queue this up for -stable.  Submitting something for
net-next and wanting a -stable backport is doubly inappropriate.

Things don't go to -stable unless it's in Linus's tree.  'net' is
for bug fixes, 'net-next' (closed right now) is for new features,
cleanups, and fixes to code only present in 'net-next'.

Anyways I applied this to 'net' and queued it up for -stable.

      parent reply	other threads:[~2016-01-19 19:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19  9:41 [PATCH net 0/1] af_iucv: Validate socket address length in iucv_sock_bind() Ursula Braun
2016-01-19  9:41 ` [PATCH net 1/1] " Ursula Braun
2016-01-19 19:23 ` 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=20160119.142357.829571599757607853.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=heicars2@linux.vnet.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=mschwid2@linux.vnet.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=ubraun@linux.vnet.ibm.com \
    --cc=ubraunu@linux.vnet.ibm.com \
    /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).