linux-kernel - Re: [PATCH] Chaining sg lists for big IO commands v5

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:	Thu, 24 May 2007 10:39:44 -0500
From:	James Bottomley <James.Bottomley@...elEye.com>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	jens.axboe@...cle.com, pbadari@...il.com,
	linux-kernel@...r.kernel.org, bhalevy@...asas.com,
	akpm@...ux-foundation.org, michaelc@...wisc.edu
Subject: Re: [PATCH] Chaining sg lists for big IO commands v5

On Thu, 2007-05-24 at 21:44 +0900, FUJITA Tomonori wrote:
> (cc's added)
> 
> From: Jens Axboe <jens.axboe@...cle.com>
> Subject: Re: [PATCH] Chaining sg lists for big IO commands v5
> Date: Thu, 24 May 2007 14:05:54 +0200
> 
> > On Thu, May 24 2007, Jens Axboe wrote:
> > > > http://git.kernel.org/?p=linux/kernel/git/tomo/linux-2.6-bidi.git;a=commitdiff;h=fb2747a9f2465ac4a1ea9e3533b92510fbcaae0c
> > > 
> > > Neat, will take a look! I should be able to just reuse that.
> > 
> > BTW, when do you plan on pushing the SCSI sg update? I'd love for it to
> > be soon, so I can just rebase the sglist branch on that and get rid of
> > the SCSI stuff in there.
> 
> Well, all I can say is that I'd love James to push the cleanups
> patchset soon too.

I'll put the accessor one into scsi-misc.  I'll try to get the other 40
reviewed via the scsi-pending tree that Mark Salyzyn suggested ... give
me some time on that.

James


-
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/