litmus-rt.git/drivers/connector, branch v2.6.32-rc6

connector: Fix incompatible pointer type warning

2009-10-06T08:39:51+00:00

Commit 7069331 (connector: Provide the sender's credentials to the
callback, 2009-10-02) changed callbacks to take two arguments but missed
this one.

drivers/connector/cn_proc.c: In function ‘cn_proc_init’:
drivers/connector/cn_proc.c:263: warning: passing argument 3 of
‘cn_add_callback’ from incompatible pointer type

Signed-off-by: Stephen Boyd 
Signed-off-by: David S. Miller

connector: Removed the destruct_data callback since it is always kfree_skb()

2009-10-02T17:54:05+00:00

Signed-off-by: Philipp Reisner 
Acked-by: Lars Ellenberg 
Acked-by: Evgeniy Polyakov 
Signed-off-by: David S. Miller

connector: Provide the sender's credentials to the callback

2009-10-02T17:54:01+00:00

Signed-off-by: Philipp Reisner 
Acked-by: Lars Ellenberg 
Acked-by: Evgeniy Polyakov 
Signed-off-by: David S. Miller

connector: Keep the skb in cn_callback_data

2009-10-02T17:53:58+00:00

Signed-off-by: Philipp Reisner 
Acked-by: Lars Ellenberg 
Acked-by: Evgeniy Polyakov 
Signed-off-by: David S. Miller

proc connector: add event for process becoming session leader

2009-09-23T14:39:29+00:00

The act of a process becoming a session leader is a useful signal to a
supervising init daemon such as Upstart.

While a daemon will normally do this as part of the process of becoming a
daemon, it is rare for its children to do so.  When the children do, it is
nearly always a sign that the child should be considered detached from the
parent and not supervised along with it.

The poster-child example is OpenSSH; the per-login children call setsid()
so that they may control the pty connected to them.  If the primary daemon
dies or is restarted, we do not want to consider the per-login children
and want to respawn the primary daemon without killing the children.

This patch adds a new PROC_SID_EVENT and associated structure to the
proc_event event_data union, it arranges for this to be emitted when the
special PIDTYPE_SID pid is set.

[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Scott James Remnant 
Acked-by: Matt Helsley 
Cc: Oleg Nesterov 
Cc: Evgeniy Polyakov 
Acked-by: "David S. Miller" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6

2009-07-24T02:03:51+00:00

Conflicts:
	drivers/net/wireless/iwmc3200wifi/netdev.c
	net/wireless/scan.c

connector: maintainer/mail update.

2009-07-21T19:43:51+00:00

Signed-off-by: Evgeniy Polyakov 
Signed-off-by: David S. Miller

connector: make callback argument type explicit

2009-07-17T17:13:21+00:00

The connector documentation states that the argument to the callback
function is always a pointer to a struct cn_msg, but rather than encode it
in the API itself, it uses a void pointer everywhere.  This doesn't make
much sense to encode the pointer in documentation as it prevents proper C
type checking from occurring and can easily allow people to use the wrong
pointer type.  So convert the argument type to an explicit struct cn_msg
pointer.

Signed-off-by: Mike Frysinger 
Signed-off-by: David S. Miller

trivial: Kconfig: .ko is normally not included in module names

2009-06-12T16:01:50+00:00

.ko is normally not included in Kconfig help, make it consistent.

Signed-off-by: Pavel Machek 
Signed-off-by: Jiri Kosina

connector: create connector workqueue only while needed once

2009-02-03T07:22:04+00:00

The netlink connector uses its own workqueue to relay the datas sent
from userspace to the appropriate callback.  If you launch the test
from Documentation/connector and change it a bit to send a high flow
of data, you will see thousands of events coming to the "cqueue"
workqueue by looking at the workqueue tracer.

This flow of events can be sent very quickly. So, to not encumber the
kevent workqueue and delay other jobs, the "cqueue" workqueue should
remain.

But this workqueue is pointless most of the time, it will always be
created (assuming you have built it of course) although only
developpers with specific needs will use it.

So avoid this "most of the time useless task", this patch proposes to
create this workqueue only when needed once.  The first jobs to be
sent to connector callbacks will be sent to kevent while the "cqueue"
thread creation will be scheduled to kevent too.

The following jobs will continue to be scheduled to keventd until the
cqueue workqueue is created, and then the rest of the jobs will
continue to perform as usual, through this dedicated workqueue.

Each time I tested this patch, only the first event was sent to
keventd, the rest has been sent to cqueue which have been created
quickly.

Also, this patch fixes some trailing whitespaces on the connector files.

Signed-off-by: Frederic Weisbecker 
Acked-by: Evgeniy Polyakov 
Signed-off-by: David S. Miller