- 09 Nov, 2005 40 commits
-
-
Linus Torvalds authored
-
-
Linus Torvalds authored
-
Ken-ichirou MATSUZAWA authored
From: Ken-ichirou MATSUZAWA <chamas@h4.dion.ne.jp> Signed-off-by:David S. Miller <davem@davemloft.net>
-
Peter Chubb authored
Trying to build today's 2.6.14+git snapshot gives undefined references to use_tempaddr Looks like an ifdef got left out. Signed-off-by:
Peter Chubb <peterc@gelato.unsw.edu.au> Signed-off-by:
-
Krzysztof Piotr Oledzki authored
Signed-off-by:
Krzysztof Piotr Oledzki <ole@ans.pl> Signed-off-by:
Pablo Neira Ayuso <pablo@netfilter.org> Signed-off-by:
Harald Welte <laforge@netfilter.org> Signed-off-by:
-
Krzysztof Piotr Oledzki authored
This patch fixes an userspace triggered oops. If there is no ICMP_ID info the reference to attr will be NULL. Signed-off-by:
-
Pablo Neira Ayuso authored
Signed-off-by:
-
Pablo Neira Ayuso authored
Propagate the error to userspace instead of returning -EPERM if the get conntrack operation fails. Signed-off-by:
-
Pablo Neira Ayuso authored
Return -EINVAL if the size isn't OK instead of -EPERM. Signed-off-by:
-
Yasuyuki Kozakai authored
Currently connection tracking handles ICMP error like normal packets if it failed to get related connection. But it fails that after all. This makes connection tracking stop tracking ICMP error at early point. Signed-off-by:
Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp> Signed-off-by:
-
Harald Welte authored
Without this patch, any user can cause nfnetlink subsystems to be autoloaded. Those subsystems however could add significant processing overhead to packet processing, and would refuse any configuration messages from non-CAP_NET_ADMIN processes anyway. This patch follows a suggestion from Patrick McHardy. Signed-off-by:
-
Philip Craig authored
The reply tuple of the PNS->PAC expectation was using the wrong call id. So we had the following situation: - PNS behind NAT firewall - PNS call id requires NATing - PNS->PAC gre packet arrives first then the PNS->PAC expectation is matched, and the other expectation is deleted, but the PAC->PNS gre packets do not match the gre conntrack because the call id is wrong. We also cannot use ip_nat_follow_master(). Signed-off-by:
Philip Craig <philipc@snapgear.com> Signed-off-by:
-
Pablo Neira Ayuso authored
ctnetlink_get_conntrack is always called from user context, so GFP_KERNEL is enough. Signed-off-by:
-
Pablo Neira Ayuso authored
Kill some useless headers included in ctnetlink. They aren't used in any way. Signed-off-by:
-
Pablo Neira Ayuso authored
Add missing module alias. This is a must to load ctnetlink on demand. For example, the conntrack tool will fail if the module isn't loaded. Signed-off-by:
-
Pablo Neira Ayuso authored
This patch adds support for conntrack marking from user space. Signed-off-by:
-
Pablo Neira Ayuso authored
This fixes an oops triggered from userspace. If we don't pass information about the private protocol info, the reference to attr will be NULL. This is likely to happen in update messages. Signed-off-by:
-
Harald Welte authored
nfattr_parse (and thus nfattr_parse_nested) always returns success. So we can make them 'void' and remove all the checking at the caller side. Based on original patch by Pablo Neira Ayuso <pablo@netfilter.org> Signed-off-by:
-
Yasuyuki Kozakai authored
Signed-off-by:
-
Yasuyuki Kozakai authored
The packet counter variable of conntrack was changed to 32bits from 64bits. This follows that change. Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
Christoph Hellwig <hch@lst.de> Signed-off-by:
-
David S. Miller authored
Noticed by Eric Brower. Signed-off-by: -
Tobias Klauser authored
Use ARRAY_SIZE macro instead of sizeof(x)/sizeof(x[0]) and remove a duplicate of ARRAY_SIZE which is never used anyways. Signed-off-by:
Tobias Klauser <tklauser@nuerscht.ch> Signed-off-by:
-
Tobias Klauser authored
Use ARRAY_SIZE macro instead of sizeof(x)/sizeof(x[0]) and remove a duplicate of ARRAY_SIZE which is never used anyways. Signed-off-by:
-
Linus Torvalds authored
-
Linus Torvalds authored
Before we did CLONE_THREAD, the way to check whether we were attaching to ourselves was to just check "current == task", but with CLONE_THREAD we should check that the thread group ID matches instead. Signed-off-by:Linus Torvalds <torvalds@osdl.org>
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
-
Adrian Bunk authored
This patch makes a needlessly global function static. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Acked-by:
William Irwin <wli@holomorphy.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
Adrian Bunk authored
This patch makes the following previously global and EXPORT_SYMBOL'ed code static: - struct mpt_proc_root_dir - int mpt_stm_index Signed-off-by:
-
Adrian Bunk authored
This patch makes two needlessly global functions static. Signed-off-by:
-
Adrian Bunk authored
This patch makes the needlessly global function path_lookup_create() static. Signed-off-by:
Trond Myklebust <trond.myklebust@fys.uio.no> Signed-off-by:
-
NeilBrown authored
Document in Documentation/md.txt the files that now appear in sysfs, and make a couple of small refinements to exactly when 'level' and 'raid_disks' are empty, to make it match the documentation. Signed-off-by:
Neil Brown <neilb@suse.de> Acked-by:
Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by:
-
NeilBrown authored
The current sync_action for an array can be one of idle - nothing happening resync - reduncancy being recalcualted recover - missing device being recoverred to spare check - user initiated check of redundancy repair - like resync but user-initiated and ignores bitmap optimisation. Each of these strings can also be written to the 'sync_action' file to cause that action to happen (if appropriate). While 'sync' is not technically correct, as a recovery is *not* a 'sync', I think it is the most servicable word here. Also 'action' is a strong word than 'mode'. Signed-off-by: -
NeilBrown authored
There are a few loose ends following the conversion of md to use kthreads: - Some fields in mdk_thread_t that aren't needed (kthreads does it's own completion and manages it's own name). - thread->run is now never NULL, so no need to check - Some tests for signal_pending that aren't needed (As we don't use signals to stop threads any more) - Some flush_signals are not needed - Some waits are interruptible and don't need to be. Signed-off-by:
-
NeilBrown authored
The 'auto-readonly' flag (which suppresses resync and superblock updates until the first write) is not meaningful for personalities that don't support resync or superblock writes (raid0, linear, etc). So clear the setting early to avoid it confusing anything - e.g. appearing in /proc/mdstat Signed-off-by:
-
NeilBrown authored
The introduction of 'resync=PENDING' (for read-only devices) caused that message to appear for non-syncable arrays like raid0 and linear. Simplest thing is to not try to print any resync info unless the personality clearly supports it. Signed-off-by:
-
