From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 668] New: Wrong xfer_funcs initialization in drivers/block/loop.c
Date: Tue, 06 May 2003 08:00:47 -0700 [thread overview]
Message-ID: <12770000.1052233247@[10.10.2.4]> (raw)
http://bugme.osdl.org/show_bug.cgi?id=668
Summary: Wrong xfer_funcs initialization in drivers/block/loop.c
Kernel Version: 2.5.68 and 2.5.69 (at least)
Status: NEW
Severity: normal
Owner: bugme-janitors@lists.osdl.org
Submitter: Reimar.Doeffinger@stud.uni-karlsruhe.de
Distribution: SuSE Linux Professional 8.1
Software Environment: gcc 3.2.2 (but should be independant of that...)
Problem Description:
In drivers/block/loop.c loop_register_transfer always fails because all entries
(instead of only first and seond) of the xfer_funcs array (in same file) are
initialized to non-zero values (&xor_funcs).
Solution:
Change
struct loop_func_table *xfer_funcs[MAX_LO_CRYPT] = {
&none_funcs,
&xor_funcs
};
to
struct loop_func_table *xfer_funcs[MAX_LO_CRYPT] = {
&none_funcs,
&xor_funcs,
0
};
in kernel version 2.4.20 there was only a comma after &xor_funcs:
struct loop_func_table *xfer_funcs[MAX_LO_CRYPT] = {
&none_funcs,
&xor_funcs,
};
which worked as well, but I guess it's better when the code doesn't depend on a
single comma.
reply other threads:[~2003-05-06 14:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='12770000.1052233247@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®