Hi Thomas,
On Wed, Oct 26, 2016 at 11:51 AM, Thomas Graf wrote:
> On 10/24/16 at 02:11pm, Geert Uytterhoeven wrote:
>> On m68k/ARAnyM, test_rhashtable fails with:
>>
>> Test failed: thread 0 returned: -4
>>
>> (-4 = -EINTR)
>
> The error is returned by kthread_stop(), I suspect we are running
On 10/24/16 at 02:11pm, Geert Uytterhoeven wrote:
> Hi Phil,
>
> On m68k/ARAnyM, test_rhashtable fails with:
>
> Test failed: thread 0 returned: -4
>
> (-4 = -EINTR)
The error is returned by kthread_stop(), I suspect we are running into
this:
static int kthread(void *_create)
{
[..
On Wed, Oct 26, 2016 at 9:33 AM, Phil Sutter wrote:
> On Mon, Oct 24, 2016 at 02:11:32PM +0200, Geert Uytterhoeven wrote:
>> On m68k/ARAnyM, test_rhashtable fails with:
>>
>> Test failed: thread 0 returned: -4
>>
>> (-4 = -EINTR)
>
> How reproducible is this? I wonder why out of the ten thread
Hi Geert,
On Mon, Oct 24, 2016 at 02:11:32PM +0200, Geert Uytterhoeven wrote:
> On m68k/ARAnyM, test_rhashtable fails with:
>
> Test failed: thread 0 returned: -4
>
> (-4 = -EINTR)
How reproducible is this? I wonder why out of the ten threads only the
first one fails.
> I traced this back
Hi Phil,
On m68k/ARAnyM, test_rhashtable fails with:
Test failed: thread 0 returned: -4
(-4 = -EINTR)
I traced this back to your commit f4a3e90ba5739cfd ("rhashtable-test: extend
to test concurrency"), which added that part of the test.
Diff of the test output between the failing commit an
