linux-kernel - Re: [PATCH] CRIS: Wire up syscalls signalfd4 to writev.

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]

Message-ID: <20090428160846.GO21811@axis.com>
Date:	Tue, 28 Apr 2009 18:08:46 +0200
From:	Jesper Nilsson <Jesper.Nilsson@...s.com>
To:	Christoph Hellwig <hch@....de>
Cc:	Mikael Starvik <mikael.starvik@...s.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] CRIS: Wire up syscalls signalfd4 to writev.

On Tue, Apr 28, 2009 at 06:01:07PM +0200, Christoph Hellwig wrote:
> On Tue, Apr 28, 2009 at 05:58:56PM +0200, Jesper Nilsson wrote:
> > On Mon, Apr 27, 2009 at 10:13:56AM +0200, Christoph Hellwig wrote:
> > > 2.6.30 added the new preadv/pwritev system calls.  The following
> > > architectures still haven't wired them up:
> > > 
> > > 	alpha, avr32, blackfin, cris, frv, h8300, m32r, xtensa
> > > 
> > > Can you maintainers please look into wiring these system calls up?
> > 
> > I've just added the following patch to the CRIS tree:
> > 
> > 
> > Adds sys_signalfd4, sys_eventfd2, sys_epoll_create1, sys_dup3,
> > sys_pipe2, sys_inotify_init1, sys_preadv, sys_pwritev
> > for both CRISv10 and CRISv32.
> 
> Care to send this and your current stack of patches upsteam before
> 2.6.30 is out?

Will do, I'll let it sit for a day in linux-next first.

/^JN - Jesper Nilsson
-- 
               Jesper Nilsson -- jesper.nilsson@...s.com
--
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/