linux-kernel - Re: NBD and 2.6 kernel MIPS problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=sgeLzBpfDHquf7zMpdgSq_0qy0WF4YEMMNVqN@mail.gmail.com>
Date:	Sun, 28 Nov 2010 20:39:19 -0500
From:	Paul Clements <paul.clements@...eleye.com>
To:	Hans Beckerus <hans.beckerus@...ia.com>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	Pavel Machek <pavel@....cz>
Subject: Re: NBD and 2.6 kernel MIPS problem

> Hi!
>
>> Hi, I recently compiled the NBD kernel module for a 2.6 ucLibc
>> kernel and are experiencing
>> some crash problems. Are there any known issues with the 2.6 range
>> of kernels together with NBD?
>
> Nothing known to me, but I no longer maintain nbd. I suggest you ask
> lkml and Paul...
>
>									Pavel
>
>> The nbd-server and nbd-client seems ok though and handshaking works.
>> The platform is MIPS based.
>>
>> I also get these syslog entries when doing insmod:
>>
>> nbd: no version for "struct_module" found: kernel tainted.
>> nbd: registered device at major 43

The struct_module warning means you compiled nbd and the kernel with
different config options. Can you try reconciling that and see if
things work better?

--
Paul

>> The major device information I understand but not the first one.
>>
>> Best regards,
>> Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/