From: Rusty Russell <rusty@rustcorp.com.au>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Denis Cheng <crquan@gmail.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Dave Young <hidave.darkstar@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/params.c: fix the module name length in param_sysfs_builtin
Date: Wed, 23 Jan 2008 12:54:26 +1100 [thread overview]
Message-ID: <200801231254.26918.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0801230011300.9183@fbirervta.pbzchgretzou.qr>
On Wednesday 23 January 2008 10:13:37 Jan Engelhardt wrote:
> On Jan 21 2008 22:16, Rusty Russell wrote:
> >On Monday 21 January 2008 20:08:25 Denis Cheng wrote:
> >> the original code use KOBJ_NAME_LEN for built-in module name length,
> >> that's defined to 20 in linux/kobject.h, but this is not enough
> >> appearntly, many module names are longer than this;
> >> #define KOBJ_NAME_LEN 20
> >
> >Thanks, applied. I was surprisedto learn that we have a 35-char source
> >filename in the kernel.
> >
> >And congratulations to nf_conntrack_l3proto_ipv4_compat.c!
>
> But nf..dada_compat.c gets linked into nf_conntrack_ipv4.ko,
> and that is what is used in /sys/module - and it fits the 20.
> Any place where nf_conntrack_l3proto_ipv4_compat would still be used?
Of course, but my point was that we already have a 35 char filename in the
kernel, and lots of > 22 chars, so increasing it is not unreasonable.
FYI make allmodconfig here gives me the following of 21 chars or longer:
dvb-usb-af9005-remote
dvb-usb-dibusb-common
nf_conntrack_netbios_ns
nf_conntrack_proto_udplite
nf_conntrack_proto_sctp
nf_conntrack_proto_gre
Cheers,
Rusty.
next prev parent reply other threads:[~2008-01-23 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 9:08 Denis Cheng
2008-01-21 11:16 ` Rusty Russell
2008-01-22 23:13 ` Jan Engelhardt
2008-01-23 1:53 ` rae l
2008-01-23 1:54 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-21 9:20 Denis Cheng
2008-01-19 5:46 rae l
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=200801231254.26918.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=crquan@gmail.com \
--cc=gregkh@suse.de \
--cc=hidave.darkstar@gmail.com \
--cc=jengelh@computergmbh.de \
--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
Powered by JetHome