From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: David Grothe <dave@gcom.com>
Cc: linux-kernel@vger.kernel.org,
LiS <linux-streams@gsyc.escet.urjc.es>,
davem@redhat.com, bidulock@openss7.org
Subject: Re: [Linux-streams] Re: [PATCH] Re: export of sys_call_tabl
Date: Thu, 10 Oct 2002 18:25:14 +0200 [thread overview]
Message-ID: <438353D513A@vcnet.vc.cvut.cz> (raw)
On 10 Oct 02 at 11:01, David Grothe wrote:
>
> Does this patch address your suggestions? This has been tested on 2.4.19.
Well, it can be that way. But if you are allowing
register_streams_calls(NULL, NULL), maybe you can move
unregister_streams_calls() to the headers and make it inline.
And you are returning while holding streams_call_sem semaphore
when failing with -EBUSY. It is not good idea.
Petr Vandrovec
vandrove@vc.cvut.cz
+int register_streams_calls(int (*putpmsg) (int, void *, void *, int, int),
+ int (*getpmsg) (int, void *, void *, int, int))
+{
+ down_write(&streams_call_sem) ; /* should return int, but doesn't */
+ if ( (putpmsg != NULL && do_putpmsg != NULL)
+ || (getpmsg != NULL && do_getpmsg != NULL)
+ )
+ return -EBUSY;
+ do_putpmsg = putpmsg;
+ do_getpmsg = getpmsg;
+ up_write(&streams_call_sem);
+ return 0 ;
+}
+
+void unregister_streams_calls(void)
+{
+ register_streams_calls(NULL, NULL);
+}
+
asmlinkage long sys_ni_syscall(void)
{
return -ENOSYS;
next reply other threads:[~2002-10-10 16:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 16:25 Petr Vandrovec [this message]
2002-10-10 16:30 ` [Linux-streams] Re: [PATCH] Re: export of sys_call_tabl David Grothe
-- strict thread matches above, loose matches on Subject: below --
2002-10-10 16:32 David Grothe
2002-10-10 16:38 Petr Vandrovec
2002-10-10 16:57 ` David Grothe
2002-10-10 17:27 ` Christoph Hellwig
2002-10-10 19:07 ` David Grothe
2002-10-10 19:33 ` Arjan van de Ven
2002-10-10 20:31 ` David Grothe
[not found] ` <20021011180209.A30671@infradead.org>
[not found] ` <20021011142657.B32421@openss7.org>
2002-10-12 2:29 ` Ole Husgaard
2002-10-12 9:32 ` Arjan van de Ven
2002-10-12 9:54 ` Brian F. G. Bidulock
2002-10-12 9:56 ` Brian F. G. Bidulock
2002-10-12 11:51 ` Alan Cox
2002-10-12 15:29 ` Ole Husgaard
2002-10-10 19:41 Petr Vandrovec
2002-10-11 14:22 ` David Grothe
2002-10-11 14:49 ` Alan Cox
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=438353D513A@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=bidulock@openss7.org \
--cc=dave@gcom.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-streams@gsyc.escet.urjc.es \
/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