linux-kernel - Re: [PATCH] Fix blktrace setup 32-bit ioctl on 64-bit kernels

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, 5 Oct 2007 12:41:42 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-kernel@...r.kernel.org, davem@...emloft.net, hch@....de,
	Al Viro <viro@....linux.org.uk>
Subject: Re: [PATCH] Fix blktrace setup 32-bit ioctl on 64-bit kernels

On Thu, Oct 04 2007, Arnd Bergmann wrote:
> On Thursday 04 October 2007, you wrote:
> > This looks a lot better! I don't mind seperating the block bits, when we
> > get the whole bunch in there. Just seemed overly silly and complicated
> > to do it for just one ioctl command. When you are happy with this patch,
> > I'll add it to the pending block stuff for 2.6.24. The blktrace fix
> > isn't a regression so need not go into 2.6.23.
> 
> ok.
> 
> > It seems some bits are missing though (like BLKTRACESETUP32), did you
> > send the whole thing?
> 
> I did the large patch on top of the blktrace patch I sent earlier,
> so it doesn't apply cleanly. When doing the final version, I'll use
> a more sensible patch order.

Ah I see, can you generate one against current git?

-- 
Jens Axboe

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