linux-kernel - Re: [GIT PULL] Block IO core changes for 3.10

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: <20130508163843.GQ7800@kernel.dk>
Date:	Wed, 8 May 2013 18:38:43 +0200
From:	Jens Axboe <axboe@...nel.dk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Block IO core changes for 3.10

On Wed, May 08 2013, Linus Torvalds wrote:
> On Wed, May 8, 2013 at 9:03 AM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> > On Wed, May 8, 2013 at 8:11 AM, Jens Axboe <axboe@...nel.dk> wrote:
> >>
> >> Frankly the pull is just late since I have been busy with that and
> >> company bits. If you look at the history, there's been no changes in
> >> more than a week.
> >
> > Ok, good. The timing made me nervous..
> 
> Oh, and should I made BIO_RESET_BITS and BIO_OWNS_VEC be 13? We have a

The numbers aren't important, as long as they are different.

> new BIO_SNAP_STABLE that is 12, and I'm really hoping these values
> aren't exposed anywhere to users..

Strictly in-kernel stuff, so no problems there. No bio flags are
propagated to user space.

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