All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Linux NFC <linux-nfc@lists.01.org>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
Subject: Re: [GIT] [NFC] 3.7 fix pull request
Date: Mon, 3 Dec 2012 13:40:56 -0500	[thread overview]
Message-ID: <20121203184056.GF26027@tuxdriver.com> (raw)
In-Reply-To: <20121129131452.GE12685@sortiz-mobl>

I don't think this will make 3.7.  Any problem if I just pull it for 3.8?

John

On Thu, Nov 29, 2012 at 02:14:52PM +0100, Samuel Ortiz wrote:
> Hi John,
> 
> I'm hoping it's not too late for 3.7 fixes, so here is a last minute one:
> 
> This is an NFC LLCP fix for 3.7 and contains only one patch.
> 
> It fixes a potential crash when receiving an LLCP HDLC frame acking a frame
> that is not the last sent one. In that case we may dereference an already
> freed pointer.
> 
> 
> The following changes since commit 6bdd253f635f7b2ef027d116933a6c9ec148b87f:
> 
>   mac80211: fix remain-on-channel (non-)cancelling (2012-11-26 14:41:40 -0500)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-3.0.git tags/nfc-fixes-3.7-2
> 
> for you to fetch changes up to 289814918ce3af1296ac7d9b05508bde64e97348:
> 
>   NFC: Fix incorrect llcp pointer dereference (2012-11-28 18:42:04 +0100)
> 
> ----------------------------------------------------------------
> Waldemar Rymarkiewicz (1):
>       NFC: Fix incorrect llcp pointer dereference
> 
>  net/nfc/llcp/llcp.c |    5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> -- 
> Intel Open Source Technology Centre
> http://oss.intel.com/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2012-12-03 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 13:14 [GIT] [NFC] 3.7 fix pull request Samuel Ortiz
2012-12-03 18:40 ` John W. Linville [this message]
2012-12-03 23:26   ` Samuel Ortiz
2012-12-06 20:12     ` John W. Linville

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=20121203184056.GF26027@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-nfc@lists.01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=waldemar.rymarkiewicz@tieto.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 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.