From: Ric Wheeler <rwheeler@redhat.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: Re: [Bug 13909] md5sum on 3GB file is constantly hanging
Date: Mon, 17 Aug 2009 10:31:21 -0400 [thread overview]
Message-ID: <4A8969B9.7000905@redhat.com> (raw)
In-Reply-To: <200908151354.n7FDsmWp001652@demeter.kernel.org>
On 08/15/2009 09:54 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13909
>
>
>
>
>
> --- Comment #28 from Roland Kletzing<devzero@web.de> 2009-08-15 13:54:43 ---
> rus,any chance to try the attached patch and confirm if it is the real fix for
> the problem ?
>
>
>
> We're now able to duplicate this bug. Not sure why it only affects ext4.
>
> ima: kernel_read parm integer overflow bugfix
>
> Reading large files>2G causes process to loop.
> (http://bugzilla.kernel.org/show_bug.cgi?id=13909)
>
> Signed-off-by: Mimi Zohar<zohar@us.ibm.com>
>
> Index: security-testing-2.6/security/integrity/ima/ima_crypto.c
> ===================================================================
> --- security-testing-2.6.orig/security/integrity/ima/ima_crypto.c
> +++ security-testing-2.6/security/integrity/ima/ima_crypto.c
> @@ -47,7 +47,8 @@ int ima_calc_hash(struct file *file, cha
> struct scatterlist sg[1];
> loff_t i_size;
> char *rbuf;
> - int rc, offset = 0;
> + unsigned long offset = 0;
> + int rc;
>
> rc = init_desc(&desc);
> if (rc != 0)
>
>
I suspect that you will need to use the official offset type to avoid
overflow at 4GB - loff_t should be more consistent,
Ric
next prev parent reply other threads:[~2009-08-17 14:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 10:44 [Bug 13909] New: md5sum on 3GB file is constantly hanging bugzilla-daemon
2009-08-04 17:10 ` [Bug 13909] " bugzilla-daemon
2009-08-05 4:27 ` bugzilla-daemon
2009-08-08 10:03 ` bugzilla-daemon
2009-08-08 17:10 ` bugzilla-daemon
2009-08-08 19:41 ` bugzilla-daemon
2009-08-08 19:41 ` bugzilla-daemon
2009-08-08 19:42 ` bugzilla-daemon
2009-08-08 19:54 ` bugzilla-daemon
2009-08-08 20:38 ` bugzilla-daemon
2009-08-10 9:31 ` bugzilla-daemon
2009-08-10 13:33 ` bugzilla-daemon
2009-08-10 13:58 ` bugzilla-daemon
2009-08-10 14:11 ` bugzilla-daemon
2009-08-10 14:13 ` bugzilla-daemon
2009-08-10 14:34 ` bugzilla-daemon
2009-08-10 15:11 ` bugzilla-daemon
2009-08-10 15:58 ` bugzilla-daemon
2009-08-10 17:41 ` bugzilla-daemon
2009-08-10 18:21 ` bugzilla-daemon
2009-08-10 18:39 ` bugzilla-daemon
2009-08-10 20:11 ` bugzilla-daemon
2009-08-10 20:13 ` bugzilla-daemon
2009-08-10 21:13 ` bugzilla-daemon
2009-08-10 21:24 ` bugzilla-daemon
2009-08-10 21:59 ` bugzilla-daemon
2009-08-11 18:47 ` bugzilla-daemon
2009-08-11 22:35 ` bugzilla-daemon
2009-08-15 13:54 ` bugzilla-daemon
2009-08-17 14:31 ` Ric Wheeler [this message]
2009-08-17 10:23 ` bugzilla-daemon
2009-08-17 14:29 ` bugzilla-daemon
[not found] <bug-13909-13602@https.bugzilla.kernel.org/>
2012-06-13 14:35 ` bugzilla-daemon
2012-06-13 14:35 ` bugzilla-daemon
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=4A8969B9.7000905@redhat.com \
--to=rwheeler@redhat.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 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.