netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: john@Calva.COM
Cc: netdev@vger.kernel.org
Subject: Re: Patch to fix kernel bug 15678 - x25 code accesses fields beyond the end of packet.
Date: Wed, 07 Apr 2010 21:29:36 -0700 (PDT)	[thread overview]
Message-ID: <20100407.212936.09766299.davem@davemloft.net> (raw)
In-Reply-To: <4BB8C0F1.2090100@Calva.COM>

From: John Hughes <john@Calva.COM>
Date: Sun, 04 Apr 2010 18:40:17 +0200

> From: John Hughes <john@calva.com>
> Subject: Patch to fix bug 15678 - x25 accesses fields beyond end of packet.
> 
> Here is a patch to stop X.25 examining fields beyond the end of the packet.
> 
> For example, when a simple CALL ACCEPTED was received:
> 
> 	10 10 0f
> 
> x25_parse_facilities was attempting to decode the FACILITIES field, but this
> packet contains no facilities field.
> 
> Signed-off-by: John Hughes <john@calva.com>

Applied, thanks John.

      reply	other threads:[~2010-04-08  4:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 16:40 Patch to fix kernel bug 15678 - x25 code accesses fields beyond the end of packet John Hughes
2010-04-08  4:29 ` 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=20100407.212936.09766299.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=john@Calva.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 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).