From: Tim Gardner <tim.gardner@canonical.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, Miklos Szeredi <mszeredi@suse.cz>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: Regression caused by commit cc56f7de7f00d188c7c4da1e9861581853b9e92f
Date: Mon, 28 Jun 2010 07:53:57 -0600 [thread overview]
Message-ID: <4C28A975.1040709@canonical.com> (raw)
In-Reply-To: <AANLkTim6O4EjVYIrta6bbnir-Idj_yj9mZnBDyQkgzSj@mail.gmail.com>
On 06/27/2010 09:11 PM, Changli Gao wrote:
> On Sat, Jun 26, 2010 at 4:18 AM, Tim Gardner<tim.gardner@canonical.com> wrote:
>> Fat fingered the original email and didn't get the fsdevel address correct.
>>
>> -----------------------
>> Hi,
>>
>> I have bisected a strange regression down to this commit that you made. If I
>> apply the attached patch (which restores the original 2 lines of code), then
>> everything works correctly. I apologize, but I don't have a simple
>> reproducer. The gist of the problem is that Java cannot decrypt a file under
>> certain circumstances, e.g., "ERROR javax.crypto.BadPaddingException: pad
>> block corrupted". There is more information in the bug report at
>> http://bugs.launchpad.net/bugs/588861 , but not all of it is helpful.
>>
>> Any thoughts?
>>
>
> It seems the target of sendfile(2) isn't a socket, and the current
> sendfile(2) code can't handle non-socket target correctly. Please try
> this patch: http://marc.info/?l=linux-fsdevel&m=127488508224173&w=2 .
>
Thanks - this patch appears to have fixed 'pad block corrupted' error.
Is it queued for 2.6.35-rc4 ?
rtg
--
Tim Gardner tim.gardner@canonical.com
next prev parent reply other threads:[~2010-06-28 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 20:18 Regression caused by commit cc56f7de7f00d188c7c4da1e9861581853b9e92f Tim Gardner
2010-06-28 3:11 ` Changli Gao
2010-06-28 13:53 ` Tim Gardner [this message]
2010-06-28 13:58 ` Changli Gao
-- strict thread matches above, loose matches on Subject: below --
2010-06-25 20:11 Tim Gardner
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=4C28A975.1040709@canonical.com \
--to=tim.gardner@canonical.com \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=xiaosuo@gmail.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.