From: Steve French <smfltc@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: Re: upcall sample patch]
Date: Thu, 07 Dec 2006 13:08:47 -0600 [thread overview]
Message-ID: <457866BF.6070503@us.ibm.com> (raw)
In-Reply-To: <457865F6.7050204@us.ibm.com>
Steve French wrote:
> For the CIFS Kerberos/SPNEGO case the Kerberos ticket can end up
> almost 64K in size and need to be passed down by Samba userspace
> helpers to kernel (for sending over the kernel socket to the server in
> the data area of the smb that the kernel cifs code formats).
>
> Is the limit on the Linux kernel connector really 1K for passing down
> to kernel?
>
> On Wed, 2006-12-06 at 17:55 -0600, Steve French wrote:
>
>> simo wrote:
>>
>>> Steve,
>>> I am experimenting using netlink.
>>>
>>> I could v. easily send messages from user space to the kernel module,
>>> adapting the provided examples. I am finding some difficulty in
>>> understanding how the other way around is supposed to work though.
>>>
>>> However while digging into headers, I found that currently the maximum
>>> message size is set to 1024 bytes. That's a bit annoying.
>>>
>>>
>>>
>> Linux kernel connector is the preferred netlink wrapper and it has
>> sample programs that I found.
>> Not sure the maximum size
>>
>
> Steve I looked into the sample programs in 2.6.19, cn_test.c and ucon.c
> are provided. Unfortunately it is not clear from them how to make
> upcalls. It is very easy to make downcalls, but I found it hard to find
> out what's the right way to catch messages sent from the kernel in the
> user space. Do you have nay other examples?
>
> For the limit, just look in linux/connector.h there you can find a
> define that sets the MAX LEN of the message to 1024.
>
> Simo.
>
parent reply other threads:[~2006-12-07 19:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <457865F6.7050204@us.ibm.com>]
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=457866BF.6070503@us.ibm.com \
--to=smfltc@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.