linux-kernel - Re: [PATCH char-misc-next v2 04/22] iommu: Allow iova to be used without requiring IOMMU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1444118727.93285.187.camel@localhost>
Date:	Tue, 06 Oct 2015 01:05:27 -0700
From:	Sudeep Dutt <sudeep.dutt@...el.com>
To:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Cc:	Sudeep Dutt <sudeep.dutt@...el.com>,
	"Woodhouse, David" <david.woodhouse@...el.com>,
	"Dixit, Ashutosh" <ashutosh.dixit@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Rao, Nikhil" <nikhil.rao@...el.com>,
	"joro@...tes.org" <joro@...tes.org>,
	"sakari.ailus@...ux.intel.com" <sakari.ailus@...ux.intel.com>,
	"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>
Subject: Re: [PATCH char-misc-next v2 04/22] iommu: Allow iova to be used
 without requiring IOMMU_SUPPORT

On Tue, 2015-10-06 at 08:56 +0100, gregkh@...uxfoundation.org wrote:
> On Mon, Oct 05, 2015 at 10:23:38PM -0700, Sudeep Dutt wrote:
> > On Tue, 2015-10-06 at 06:20 +0100, gregkh@...uxfoundation.org wrote:
> > > On Tue, Oct 06, 2015 at 06:12:40AM +0100, gregkh@...uxfoundation.org wrote:
> > > > On Mon, Oct 05, 2015 at 10:38:43AM -0700, Sudeep Dutt wrote:
> > > > > On Mon, 2015-10-05 at 03:50 -0700, Woodhouse, David wrote:
> > > > > > On Tue, 2015-09-29 at 18:09 -0700, Ashutosh Dixit wrote:
> > > > > > > From: Sudeep Dutt <sudeep.dutt@...el.com>
> > > > > > > 
> > > > > > > iova is a library which can be built without IOMMU_SUPPORT
> > > > > > > 
> > > > > > > Signed-off-by: Sudeep Dutt <sudeep.dutt@...el.com>
> > > > > > 
> > > > > > The first three of these patches are in 4.3-rc4 already. Apologies for
> > > > > > the delay in pushing them out.
> > > > > > 
> > > > > > This one looks sane enough too, but perhaps in that case we should move
> > > > > > the code *out* of drivers/iommu/ and into lib/iova/ ?
> > > > > > 
> > > > > 
> > > > > Yes, moving the code into lib/iova is the correct long term solution. I
> > > > > have sent Greg a patch which reverts this commit since it is no longer
> > > > > required and will create a merge conflict for him unnecessarily as well
> > > > > with 4.3-rc4.
> > > > 
> > > > I can handle merge issues, that's trivial.  Reverting the patch
> > > > shoulnd't really be needed, right?  Let me see what happens when I merge
> > > > to see if your patch is necessary...
> > > 
> > > Ok, I don't think it is needed, the merge was pretty trivial.
> > > 
> > > Can you test out my char-misc-testing branch right now to see if it's
> > > all ok with the merge?  If so, I'll move it all over to the "real" place
> > > for it to start showing up in linux-next, i.e. my char-misc-next branch.
> > > 
> > 
> > Hi Greg,
> > 
> > I think it is best to revert this patch as it is incorrect. The iommu
> > folder gets compiled only if IOMMU_SUPPORT is enabled so IOMMU_IOVA
> > should indeed be included only when IOMMU_SUPPORT is enabled.
> > 
> > Sincere apologies for the mess here but I believe it will all get fixed
> > up if you accept the revert of 353649e5da I sent across earlier today.
> 
> Again, look at the merge, I think I already handled this in that manner.
> If not, let me know.
> 

Hi Greg,

I took a look at your latest char-misc-testing tree and it needs to be
fixed up. IOMMU_IOVA should be inside the "if IOMMU_SUPPORT" block
instead of above it.

git revert 353649e5da in the char-misc-testing tree will fix everything
up or you could also apply the patch I sent earlier today which has the
same revert.

Thanks,
Sudeep Dutt

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/