ntb.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Allen Hubbe" <Allen.Hubbe@emc.com>
To: "'Yu, Xiangliang'" <Xiangliang.Yu@amd.com>, linux-ntb@googlegroups.com
Cc: 'Jon Mason' <jdmason@kudzu.us>, 'Dave Jiang' <dave.jiang@intel.com>
Subject: RE: [PATCH 2/2] NTB: Remove _addr functions from ntb_hw_amd
Date: Wed, 23 Mar 2016 10:01:08 -0400	[thread overview]
Message-ID: <000001d1850c$734ad1c0$59e07540$@emc.com> (raw)
In-Reply-To: <BLUPR12MB0420FA1F9309F7B47825EDA6EB810@BLUPR12MB0420.namprd12.prod.outlook.com>

> From: Yu, Xiangliang
> > From: Allen Hubbe
> > > From: Yu, Xiangliang
> > > > From: Allen Hubbe
> > > > Kernel zero day testing warned about address space confusion.  A
> > > > virtual iomem address was used where a physical address is expected.
> > > > The offending functions implement an optional part of the api, so
> > > > they are removed.  They can be added later, after testing.
> > >
> > > Ntb_dev_ops_is_valid will check the related implement and AMD ntb
> > > driver can't Register ntb device if you remove the two functions.
> >
> > See [PATCH 1/2].
> 
> I haven't received the mail of [PATCH 1/2].

I resent it just to you.  Are you not subscribed to the linux-ntb mailing list?

Note: this patch 2/2 just takes the _addr functions out of the driver, which is the only change I am comfortable to make without testing.  Since I cannot test the driver, I cannot provide any real fix for the functions.  Since you have the ability to test, if you provide a fix for these functions, I expect your patch would be accepted instead of this one.  If you provide a fix, it would be best to provide that fix assuming that my patch has not been applied, so that your changes for the fix are clear in the patch.


  reply	other threads:[~2016-03-23 14:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21  8:53 [PATCH 1/2] NTB: Make _addr functions optional in the API Allen Hubbe
2016-03-21  8:53 ` [PATCH 2/2] NTB: Remove _addr functions from ntb_hw_amd Allen Hubbe
2016-03-22  0:00   ` Jon Mason
2016-03-22  6:30   ` Yu, Xiangliang
2016-03-22 14:00     ` Allen Hubbe
2016-03-23  3:22       ` Yu, Xiangliang
2016-03-23 14:01         ` Allen Hubbe [this message]
2016-03-24  6:46           ` Yu, Xiangliang
2016-03-27 15:22             ` Jon Mason

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='000001d1850c$734ad1c0$59e07540$@emc.com' \
    --to=allen.hubbe@emc.com \
    --cc=Xiangliang.Yu@amd.com \
    --cc=dave.jiang@intel.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-ntb@googlegroups.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).