linux-kernel - Re: [PATCH v2] pci: Allow read/write access to sysfs I/O port resources

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 23 Jul 2010 09:28:06 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Alex Williamson <alex.williamson@...hat.com>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	chrisw@...hat.com, ddutile@...hat.com, bjorn.helgaas@...com,
	eike-kernel@...tec.de
Subject: Re: [PATCH v2] pci: Allow read/write access to sysfs I/O port
 resources

On Fri, 23 Jul 2010 09:10:27 -0600
Alex Williamson <alex.williamson@...hat.com> wrote:

> On Mon, 2010-07-19 at 09:45 -0600, Alex Williamson wrote:
> > PCI sysfs resource files currently only allow mmap'ing.  On x86 this
> > works fine for memory backed BARs, but doesn't work at all for I/O
> > port backed BARs.  Add read/write to I/O port PCI sysfs resource
> > files to allow userspace access to these device regions.
> > 
> > Signed-off-by: Alex Williamson <alex.williamson@...hat.com>
> > ---
> 
> Any thoughts on this for -next?  Thanks,

Yeah, I like it.  Unless there are objections I'll pull it in.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/