From: Jens Axboe <jens.axboe@oracle.com>
To: "Ricardo M. Correia" <Ricardo.M.Correia@Sun.COM>
Cc: fio@vger.kernel.org
Subject: Re: Verification failures with mixed read/write case
Date: Tue, 23 Feb 2010 14:59:43 +0100 [thread overview]
Message-ID: <20100223135942.GD1025@kernel.dk> (raw)
In-Reply-To: <1266932889.3379.19.camel@cfslap.wizy.org>
On Tue, Feb 23 2010, Ricardo M. Correia wrote:
> Yup, that seems to have worked.
>
> Thanks :)
No problem, apparently sha256 verifies aren't that widely used :-)
>
> On Ter, 2010-02-23 at 10:36 +0100, Jens Axboe wrote:
> > OK, so this seems to be just a bug in sha256, it's working as expected
> > here. Can you try the below patch?
> >
> > diff --git a/verify.c b/verify.c
> > index 59f1ddf..c894b60 100644
> > --- a/verify.c
> > +++ b/verify.c
> > @@ -212,7 +212,7 @@ static int verify_io_u_sha256(struct verify_header *hdr, struct io_u *io_u,
> > {
> > void *p = io_u_verify_off(hdr, io_u, header_num);
> > struct vhdr_sha256 *vh = hdr_priv(hdr);
> > - uint8_t sha256[128];
> > + uint8_t sha256[64];
> > struct sha256_ctx sha256_ctx = {
> > .buf = sha256,
> > };
> > diff --git a/verify.h b/verify.h
> > index c12bc7d..be98c54 100644
> > --- a/verify.h
> > +++ b/verify.h
> > @@ -37,7 +37,7 @@ struct vhdr_sha512 {
> > uint8_t sha512[128];
> > };
> > struct vhdr_sha256 {
> > - uint8_t sha256[128];
> > + uint8_t sha256[64];
> > };
> > struct vhdr_sha1 {
> > uint32_t sha1[5];
> >
>
>
--
Jens Axboe
prev parent reply other threads:[~2010-02-23 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 1:20 Verification failures with mixed read/write case Ricardo M. Correia
2010-02-18 1:35 ` Ricardo M. Correia
2010-02-23 9:28 ` Jens Axboe
2010-02-23 9:36 ` Jens Axboe
2010-02-23 13:48 ` Ricardo M. Correia
2010-02-23 13:59 ` Jens Axboe [this message]
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=20100223135942.GD1025@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Ricardo.M.Correia@Sun.COM \
--cc=fio@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox