From: Denys Vlasenko <vda.linux@googlemail.com>
To: busybox@busybox.net
Cc: Saravanan Chanemouganandam <schane@osmozis.com>,
netfilter@vger.kernel.org
Subject: Re: modprobe: cannot parse modules.dep error
Date: Tue, 18 Dec 2007 11:08:23 +0000 [thread overview]
Message-ID: <200712181108.23892.vda.linux@googlemail.com> (raw)
In-Reply-To: <200712181032.17947.schane@osmozis.com>
On Tuesday 18 December 2007 09:32, Saravanan Chanemouganandam wrote:
> Hi all,
>
> I am running into the following problem when invoking a netfilter iptables
> ( v1.3.8) and xtables support in the buildroot's busybox (v1.7.2) system.
> The netfilter packet configuration and support modules are compiled and
> built into the linux-2.6.16 kernel image.
>
> When a 'C++' application code calls the iptables through
> sprintf(buff, "%s -t mangle -A PREROUTING %s -j MARK --set-mark 512",
> Config.iptables, Config.link[i]);
> it throws the modprobe error.
>
> iptables -t mangle -A PREROUTING -d 88.160.215.156 -p icmp -j MARK
> --set-mark 512
> modprobe: cannot parse modules.dep
> modprobe: cannot parse modules.dep
> iptables -t mangle -A PREROUTING -s 88.160.215.156 -p icmp -j MARK
> --set-mark 512
> modprobe: cannot parse modules.dep
> modprobe: cannot parse modules.dep
> iptables -t mangle -A PREROUTING -d 88.160.215.156 -p tcp --dport http -j
> MARK --set-mark 512
> modprobe: cannot parse modules.dep
Can you try the following in modprobe.c?
static struct dep_t *build_dep(void)
{
...
filename = xasprintf("/lib/modules/%s/modules.dep", un.release);
fd = open(filename, O_RDONLY);
if (ENABLE_FEATURE_CLEAN_UP)
free(filename);
if (fd < 0) {
/* Ok, that didn't work. Fall back to looking in /lib/modules */
fd = open("/lib/modules/modules.dep", O_RDONLY);
if (fd < 0) {
- bb_error_msg_and_die("cannot parse modules.dep");
+ bb_error_msg("cannot parse modules.dep");
+ return NULL;
}
}
...
--
vda
prev parent reply other threads:[~2007-12-18 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 9:32 modprobe: cannot parse modules.dep error Saravanan Chanemouganandam
2007-12-18 11:08 ` Denys Vlasenko [this message]
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=200712181108.23892.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=busybox@busybox.net \
--cc=netfilter@vger.kernel.org \
--cc=schane@osmozis.com \
/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