From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Question on LUKS master key digest and its effect on security
Date: Sun, 20 Sep 2009 20:11:11 +0200 [thread overview]
Message-ID: <4AB6703F.90804@redhat.com> (raw)
In-Reply-To: <20090920150945.GA8432@fancy-poultry.org>
Heinz Diehl wrote:
> On 20.09.2009, Heinz Diehl wrote:
>
>> Today I upgraded to the latest device-mapper, and the buffer i/o errors
>> are completely gone.
>
> Have to correct myself, after some hours there are some buffer i/o errors
> in the logs again. It's a lot less errors as it has been before, but they
> are not gone...
Sure, because libdevmapper is still not completely udev aware:-)
Anyway, because I do not want to spent too much time with this bug
(I am sure you are not only one who see this) I moved that
error workaround after first 1 sec waiting, this should be similar to
behaviour in 1.07 but do not adds sleep when not needed)
Please can you retest with current svn code?
And btw code should be in stable state, I just need to find some time
to implement some new features before releasing stable candidate.
Milan
next prev parent reply other threads:[~2009-09-20 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 17:39 [dm-crypt] Question on LUKS master key digest and its effect on security Tero Pesonen
2009-09-18 18:16 ` Milan Broz
2009-09-18 20:18 ` Tero Pesonen
2009-09-22 15:08 ` Tero Pesonen
2009-09-22 15:47 ` Milan Broz
2009-09-22 17:47 ` Tero Pesonen
2009-09-22 16:14 ` [dm-crypt] Question on LUKS master key digest and its effect on?security Heinz Diehl
2009-09-22 16:21 ` Milan Broz
2009-09-19 16:51 ` [dm-crypt] Question on LUKS master key digest and its effect on security Heinz Diehl
2009-09-19 19:00 ` Milan Broz
2009-09-20 11:28 ` Heinz Diehl
2009-09-20 15:09 ` Heinz Diehl
2009-09-20 18:11 ` Milan Broz [this message]
2009-09-20 21:03 ` Heinz Diehl
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=4AB6703F.90804@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox