From: Mandeep Singh Baines <msb@chromium.org>
To: Valdis.Kletnieks@vt.edu
Cc: Will Drewry <wad@chromium.org>,
Mandeep Singh Baines <msb@chromium.org>,
Alasdair G Kergon <agk@redhat.com>, Milan Broz <mbroz@redhat.com>,
dm-devel@redhat.com, Elly Jones <ellyjones@chromium.org>,
Olof Johansson <olofj@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dm: verity target
Date: Thu, 29 Sep 2011 10:31:03 -0700 [thread overview]
Message-ID: <20110929173103.GA22515@google.com> (raw)
In-Reply-To: <21505.1317245414@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu (Valdis.Kletnieks@vt.edu) wrote:
> On Tue, 27 Sep 2011 14:02:05 CDT, Will Drewry said:
>
> > I was just curious if there is any interest in pulling this change, or
> > if not, if there is any particular set of concerns, fixes, etc.
>
> Out of curiosity, how much of the stack does this end up eating? My root
> filesystem is already ext4 on an LVM partition that's on a LUKS/dm-crypt
> partition on a hard drive, and I'm sure somebody out there will have used xfs
> instead - and then exported it via NFS or something. Are we going to get weird
> stack overflows if people throw dm-verity into this sort of mix?
>
No. dm-verity uses very little stack since most of the code is running
in a separate workqueue context. The _map call is pretty light.
> > realize it's not a small amount of code to digest (though it is
> > smaller than the post from last year[1]). Would re-posting with an
> > added blob explaining the name be useful,
>
> Probably will need it to be merged, unless you set up an auto-reply that says
> "Patch rejected, 'verity' is *not* a typo for 'verify'" ;)
>
> I'll hopefully have some more comments over the weekend if I get some spare
> cycles.
>
next prev parent reply other threads:[~2011-09-29 17:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 18:45 [PATCH] dm: verity target Mandeep Singh Baines
2011-09-16 17:54 ` Valdis.Kletnieks
2011-09-27 19:02 ` Will Drewry
2011-09-27 19:13 ` Alasdair G Kergon
2011-09-27 19:31 ` Will Drewry
2011-09-27 19:31 ` Will Drewry
2011-09-28 21:30 ` Valdis.Kletnieks
2011-09-29 1:07 ` John Stoffel
2011-09-29 17:31 ` Mandeep Singh Baines [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-15 22:02 Wesley Miaw
2011-11-10 5:18 Mandeep Singh Baines
2011-11-10 5:18 ` Mandeep Singh Baines
2011-11-10 7:44 ` Steffen Klassert
2011-11-10 14:42 ` Will Drewry
2011-12-22 0:36 Mandeep Singh Baines
2011-12-22 0:36 ` Mandeep Singh Baines
2012-01-04 21:49 Mandeep Singh Baines
2012-01-04 21:49 ` Mandeep Singh Baines
2012-01-04 22:42 ` Mandeep Singh Baines
2012-01-04 22:42 ` Mandeep Singh Baines
2012-02-28 22:57 Mandeep Singh Baines
2012-02-29 21:16 ` Mikulas Patocka
2012-03-01 6:24 ` Mandeep Singh Baines
2012-02-29 21:30 ` Andrew Morton
2012-03-02 0:33 Mandeep Singh Baines
2012-03-02 16:08 ` Mandeep Singh Baines
2012-03-02 16:08 ` Mandeep Singh Baines
2012-03-10 0:03 Mandeep Singh Baines
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110929173103.GA22515@google.com \
--to=msb@chromium.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ellyjones@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=olofj@chromium.org \
--cc=wad@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.