All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, keyrings@vger.kernel.org,
	mark.rutland@arm.com, ebiggers@google.com
Subject: Re: [PATCH RESEND net-next v2] KEYS: DNS: limit the length of option strings
Date: Tue, 17 Apr 2018 18:37:36 +0000	[thread overview]
Message-ID: <20180417183736.GC9237@gmail.com> (raw)
In-Reply-To: <20180417.142437.1105065334888296683.davem@davemloft.net>

On Tue, Apr 17, 2018 at 02:24:37PM -0400, David Miller wrote:
> From: Eric Biggers <ebiggers3@gmail.com>
> Date: Tue, 17 Apr 2018 11:23:40 -0700
> 
> > Can you queue this up for stable too?  syzbot has been hitting this on older
> > kernel versions.
> 
> If you want a patch bound for stable, it must show up in Linus's tree
> first which means you should target 'net' rather than 'net-next'.

Okay, can you move the patch there, or do I need to resend, or is it too late
already?  It's a clean cherry-pick.  Sorry, I'm not too familiar with the quirks
of net and netdev -- most other maintainers do things differently.

Thanks,

Eric

WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers3@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, keyrings@vger.kernel.org,
	mark.rutland@arm.com, ebiggers@google.com
Subject: Re: [PATCH RESEND net-next v2] KEYS: DNS: limit the length of option strings
Date: Tue, 17 Apr 2018 11:37:36 -0700	[thread overview]
Message-ID: <20180417183736.GC9237@gmail.com> (raw)
In-Reply-To: <20180417.142437.1105065334888296683.davem@davemloft.net>

On Tue, Apr 17, 2018 at 02:24:37PM -0400, David Miller wrote:
> From: Eric Biggers <ebiggers3@gmail.com>
> Date: Tue, 17 Apr 2018 11:23:40 -0700
> 
> > Can you queue this up for stable too?  syzbot has been hitting this on older
> > kernel versions.
> 
> If you want a patch bound for stable, it must show up in Linus's tree
> first which means you should target 'net' rather than 'net-next'.

Okay, can you move the patch there, or do I need to resend, or is it too late
already?  It's a clean cherry-pick.  Sorry, I'm not too familiar with the quirks
of net and netdev -- most other maintainers do things differently.

Thanks,

Eric

  reply	other threads:[~2018-04-17 18:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 21:29 [PATCH RESEND net-next v2] KEYS: DNS: limit the length of option strings Eric Biggers
2018-04-16 21:29 ` Eric Biggers
2018-04-17 17:43 ` David Miller
2018-04-17 17:43   ` David Miller
2018-04-17 18:23   ` Eric Biggers
2018-04-17 18:23     ` Eric Biggers
2018-04-17 18:24     ` David Miller
2018-04-17 18:24       ` David Miller
2018-04-17 18:37       ` Eric Biggers [this message]
2018-04-17 18:37         ` Eric Biggers
2018-04-17 18:52         ` David Miller
2018-04-17 18:52           ` 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=20180417183736.GC9237@gmail.com \
    --to=ebiggers3@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ebiggers@google.com \
    --cc=keyrings@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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.