From: Olaf Kirch <okir@suse.de>
To: netdev@oss.sgi.com
Cc: lksctp-developers@lists.sourceforge.net
Subject: [PATCH] Propagate error from sctp_proc_init
Date: Wed, 14 Apr 2004 15:41:48 +0200 [thread overview]
Message-ID: <20040414134148.GC16591@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 193 bytes --]
The following patch makes sure that an error in sctp_proc_init()
causes module initialization to fail.
Olaf
--
Olaf Kirch | The Hardware Gods hate me.
okir@suse.de |
---------------+
[-- Attachment #2: sctp-initfail --]
[-- Type: text/plain, Size: 581 bytes --]
--- linux-2.6.4/net/sctp/protocol.c.initfail 2004-02-19 11:36:37.000000000 +0100
+++ linux-2.6.4/net/sctp/protocol.c 2004-04-14 15:36:19.000000000 +0200
@@ -1001,7 +1001,9 @@
goto err_init_mibs;
/* Initialize proc fs directory. */
- sctp_proc_init();
+ status = sctp_proc_init();
+ if (status)
+ goto err_init_proc;
/* Initialize object count debugging. */
sctp_dbg_objcnt_init();
@@ -1165,6 +1167,7 @@
sizeof(struct sctp_hashbucket)));
err_ahash_alloc:
sctp_dbg_objcnt_exit();
+err_init_proc:
sctp_proc_exit();
cleanup_sctp_mibs();
err_init_mibs:
next reply other threads:[~2004-04-14 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 13:41 Olaf Kirch [this message]
2004-04-14 22:09 ` [PATCH] Propagate error from sctp_proc_init Sridhar Samudrala
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=20040414134148.GC16591@suse.de \
--to=okir@suse.de \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).