linux-kernel - Re: [PATCH] fix UIO with device tree but no assigned interrupt

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 18 Jun 2013 22:37:12 +0200
From:	Pavel Machek <pavel@...x.de>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	Detlev Zundel <dzu@...x.de>, "Hans J. Koch" <hjk@...sjkoch.de>,
	Rob Herring <rob.herring@...xeda.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	trivial <trivial@...nel.org>
Subject: Re: [PATCH] fix UIO with device tree but no assigned interrupt

Hi!

> > If device is initialized from device tree, but has no interrupt
> > assigned, uio will still try to request and interrupt old way,
> > fails, and fails registration.
> > 
> > This is wrong; don't try initializing irq using platform data if
> > device tree is available.
> > 
> > Simplified code based on suggestion by Grant Likely.
> > 
> > Fixed memory leak in "irq can not be registered" error path.
> > 
> > Signed-off-by: Pavel Machek <pavel@...x.de>
> > Reported-by: Detlev Zundel <dzu@...x.de>
> 
> I see a ton of patches in this thread, and have no idea which one is
> "newest" and correct.
> 
> Please resend, in a format that I do not have to edit at all (hint, the
> subject line counts), that I can apply properly.

I resent both patches, hopefully I got subject lines right this time.

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/