On Fri, Jan 17, 2014 at 10:51:07AM +, Will Deacon wrote:
> Actually, I have removed strnlen_user for 3.14. Could you try your test case
> with our for-next branch please?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
>
This will work fine, I believe (I
Hi Kyle,
On Thu, Jan 16, 2014 at 11:48:17PM +, Kyle McMartin wrote:
> I received a bug report about the ruby test-suite failing on AArch64 when
> attempting to pass MAX_ARG_STRLEN sized args to execv[1]. It was
> expecting an E2BIG returned, but instead was receiving ENOMEM, and
>
Hi Kyle,
On Thu, Jan 16, 2014 at 11:48:17PM +, Kyle McMartin wrote:
I received a bug report about the ruby test-suite failing on AArch64 when
attempting to pass MAX_ARG_STRLEN sized args to execv[1]. It was
expecting an E2BIG returned, but instead was receiving ENOMEM, and
concatenating
On Fri, Jan 17, 2014 at 10:51:07AM +, Will Deacon wrote:
Actually, I have removed strnlen_user for 3.14. Could you try your test case
with our for-next branch please?
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
This will work fine, I believe (I can't
I received a bug report about the ruby test-suite failing on AArch64 when
attempting to pass MAX_ARG_STRLEN sized args to execv[1]. It was
expecting an E2BIG returned, but instead was receiving ENOMEM, and
concatenating the argument strings in funky ways.
The problem appeared to be in
I received a bug report about the ruby test-suite failing on AArch64 when
attempting to pass MAX_ARG_STRLEN sized args to execv[1]. It was
expecting an E2BIG returned, but instead was receiving ENOMEM, and
concatenating the argument strings in funky ways.
The problem appeared to be in
6 matches
Mail list logo