public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Chris Leech <cleech@redhat.com>
Cc: Johannes Thumshirn <jth@kernel.org>,
	fcoe-devel@open-fcoe.org, linux-scsi@vger.kernel.org,
	Vasu Dev <vasu.dev@linux.intel.com>
Subject: Re: [PATCH v2] libfc: sanity check cpu number extracted from xid
Date: Wed, 13 Jul 2016 21:50:33 -0400	[thread overview]
Message-ID: <yq1shvdm1hy.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1467300756-7949-1-git-send-email-cleech@redhat.com> (Chris Leech's message of "Thu, 30 Jun 2016 08:32:36 -0700")

>>>>> "Chris" == Chris Leech <cleech@redhat.com> writes:

Chris> In the receive path libfc extracts a cpu number from the ox_id in
Chris> the fiber channel header and uses that to do a per_cpu_ptr
Chris> conversion.  If, for some reason, a frame is received with an
Chris> invalid ox_id, per_cpu_ptr will return an invalid pointer and the
Chris> libfc receive path will panic the system trying to use it.

Applied to 4.8/scsi-queue.

-- 
Martin K. Petersen	Oracle Linux Engineering

      parent reply	other threads:[~2016-07-14  1:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160630070925.ptbgkeq57txs55gf@c203.arch.suse.de>
     [not found] ` <20160630070925.ptbgkeq57txs55gf-3LAbnSA0sDC4fIQPS+WK3rNAH6kLmebB@public.gmane.org>
2016-06-30 15:32   ` [PATCH v2] libfc: sanity check cpu number extracted from xid Chris Leech
     [not found]     ` <1467300756-7949-1-git-send-email-cleech-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-01  8:09       ` Johannes Thumshirn
2016-07-14  1:51         ` Martin K. Petersen
2016-07-14  1:50     ` Martin K. Petersen [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=yq1shvdm1hy.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=cleech@redhat.com \
    --cc=fcoe-devel@open-fcoe.org \
    --cc=jth@kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=vasu.dev@linux.intel.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