From: Alan Cox <alan.cox@intel.com>
To: "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>
Cc: Alasdair G Kergon <agk@redhat.com>, <dm-devel@redhat.com>,
<akpm@linux-foundation.org>, <linux-fsdevel@vger.kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Milan Broz <mbroz@redhat.com>
Subject: Re: dm-integrity: integrity protection device-mapper target
Date: Mon, 21 Jan 2013 13:51:57 +0000 [thread overview]
Message-ID: <20130121135157.47a68a57@bob.linux.org.uk> (raw)
In-Reply-To: <CALLzPKZS6WgBxPcXJ1Eoe09QD_-T98E4x29qUo-fNAAt1ajTrw@mail.gmail.com>
> This is not to provide reliability.
> Default is to return error. But zero might be desirable.
There are cases where being able to force blocks to all zeros is itself
a security attack and it seems an odd behaviour. Error on read/allow
write seems sensible enough.
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <alan.cox@intel.com>
To: "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
dm-devel@redhat.com, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org,
Mikulas Patocka <mpatocka@redhat.com>,
Milan Broz <mbroz@redhat.com>
Subject: Re: dm-integrity: integrity protection device-mapper target
Date: Mon, 21 Jan 2013 13:51:57 +0000 [thread overview]
Message-ID: <20130121135157.47a68a57@bob.linux.org.uk> (raw)
In-Reply-To: <CALLzPKZS6WgBxPcXJ1Eoe09QD_-T98E4x29qUo-fNAAt1ajTrw@mail.gmail.com>
> This is not to provide reliability.
> Default is to return error. But zero might be desirable.
There are cases where being able to force blocks to all zeros is itself
a security attack and it seems an odd behaviour. Error on read/allow
write seems sensible enough.
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2013-01-21 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 4:54 dm-integrity: integrity protection device-mapper target Mikulas Patocka
2013-01-18 21:43 ` Kasatkin, Dmitry
2013-01-18 23:16 ` Alasdair G Kergon
2013-01-18 23:58 ` Kasatkin, Dmitry
2013-01-21 13:51 ` Alan Cox [this message]
2013-01-21 13:51 ` Alan Cox
2013-01-21 10:37 ` Kasatkin, Dmitry
2013-01-21 10:38 ` Kasatkin, Dmitry
2013-01-23 1:29 ` Mikulas Patocka
2013-01-23 6:09 ` [dm-devel] " Will Drewry
2013-01-23 10:20 ` Kasatkin, Dmitry
2013-01-28 1:43 ` Will Drewry
2013-01-23 9:15 ` Spelic
2013-01-23 10:19 ` Kasatkin, Dmitry
2013-01-23 10:19 ` Kasatkin, Dmitry
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=20130121135157.47a68a57@bob.linux.org.uk \
--to=alan.cox@intel.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mbroz@redhat.com \
--cc=mpatocka@redhat.com \
/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.