From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.kernel.org,
LiS <linux-streams@gsyc.escet.urjc.es>,
davem@redhat.com
Subject: Re: [PATCH] Re: export of sys_call_table
Date: Wed, 9 Oct 2002 13:54:42 -0600 [thread overview]
Message-ID: <20021009135442.E16773@openss7.org> (raw)
In-Reply-To: <41C1FEE0A55@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Wed, Oct 09, 2002 at 02:20:19PM +0200
Petr,
Thanks you for the constructive suggestions. I'll see if we
can add those in an test it up.
--brian
On Wed, 09 Oct 2002, Petr Vandrovec wrote:
> On 8 Oct 02 at 18:21, Brian F. G. Bidulock wrote:
> > --- kernel/sys.c.orig 2002-08-02 19:39:46.000000000 -0500
> > +++ kernel/sys.c 2002-10-08 16:46:55.000000000 -0500
> ...
>
> I believe that you should check that nobody else has registered its
> own streams module. You can also allow for multiple streams modules
> in parallel (and fall through when module returns on -ENOIOCTLCMD or -ENOTTY),
> but I believe that usually only one module will be registered.
>
> And I believe that export symbols should NOT be _GPL_ONLY: before
> (non-GPL) export of syscall_table was available, non-GPL modules were
> able to hook syscalls, and when _GPL_ONLY was introduced into kernel
> it was promised that we'll never make currently provided functionality
> GPL-only (as far as I remember).
> Best regards,
> Petr Vandrovec
>
> int register_streams_calls(...)
> > +void register_streams_calls(int (*putpmsg) (int, void *, void *, int, int),
> > + int (*getpmsg) (int, void *, void *, int, int))
> > +{
>
> int err;
> if (!putpmsg || !getpmsg) return -EINVAL;
>
> > + down_write(&streams_call_sem);
>
> err = -EBUSY;
> if (!do_putpmsg) {
> err = 0;
>
> > + do_putpmsg = putpmsg;
> > + do_getpmsg = getpmsg;
>
> }
>
> > + up_write(&streams_call_sem);
>
> return err;
>
> > +}
> > +
> > +void unregister_streams_calls(void)
> > +{
>
> down_write(&streams_call_sem);
> do_putpmsg = NULL;
> do_getpmsg = NULL;
> up_write(&streams_call_sem);
> }
>
--
Brian F. G. Bidulock ¦ The reasonable man adapts himself to the ¦
bidulock@openss7.org ¦ world; the unreasonable one persists in ¦
http://www.openss7.org/ ¦ trying to adapt the world to himself. ¦
¦ Therefore all progress depends on the ¦
¦ unreasonable man. -- George Bernard Shaw ¦
next prev parent reply other threads:[~2002-10-09 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 12:20 [PATCH] Re: export of sys_call_table Petr Vandrovec
2002-10-09 19:54 ` Brian F. G. Bidulock [this message]
2002-10-10 16:01 ` [Linux-streams] " David Grothe
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 19:15 Brian F. G. Bidulock
2002-10-04 22:21 ` David S. Miller
2002-10-04 22:41 ` Brian F. G. Bidulock
2002-10-04 22:38 ` David S. Miller
2002-10-08 22:20 ` [PATCH] " Brian F. G. Bidulock
2002-10-08 22:27 ` Brian F. G. Bidulock
2002-10-08 23:39 ` David S. Miller
2002-10-08 23:18 ` David S. Miller
2002-10-09 0:21 ` Brian F. G. Bidulock
2002-10-09 0:00 ` Robert Love
[not found] ` <mailman.1034119380.19047.linux-kernel2news@redhat.com>
2002-10-09 0:30 ` Pete Zaitcev
2002-10-09 0:40 ` Brian F. G. Bidulock
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=20021009135442.E16773@openss7.org \
--to=bidulock@openss7.org \
--cc=VANDROVE@vc.cvut.cz \
--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