Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 22 6月, 2006 4 次提交
  3. 20 6月, 2006 4 次提交
  5. 18 6月, 2006 5 次提交
    • M
      [ARM] 3407/1: lpd7x: documetation update · 51cb21a9
      由 Marc Singer 提交于 
      Patch from Marc Singer

New documentation for the touchscreen controllers and LCD panels.
Signed-off-by: NMarc Singer <elf@buici.com>
Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      51cb21a9
    • D
      [TCP]: Add tcp_slow_start_after_idle sysctl. · 35089bb2
      由 David S. Miller 提交于 
      A lot of people have asked for a way to disable tcp_cwnd_restart(),
and it seems reasonable to add a sysctl to do that.
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      35089bb2
    • H
      [NET]: Add netif_tx_lock · 932ff279
      由 Herbert Xu 提交于 
      Various drivers use xmit_lock internally to synchronise with their
transmission routines.  They do so without setting xmit_lock_owner.
This is fine as long as netpoll is not in use.

With netpoll it is possible for deadlocks to occur if xmit_lock_owner
isn't set.  This is because if a printk occurs while xmit_lock is held
and xmit_lock_owner is not set can cause netpoll to attempt to take
xmit_lock recursively.

While it is possible to resolve this by getting netpoll to use
trylock, it is suboptimal because netpoll's sole objective is to
maximise the chance of getting the printk out on the wire.  So
delaying or dropping the message is to be avoided as much as possible.

So the only alternative is to always set xmit_lock_owner.  The
following patch does this by introducing the netif_tx_lock family of
functions that take care of setting/unsetting xmit_lock_owner.

I renamed xmit_lock to _xmit_lock to indicate that it should not be
used directly.  I didn't provide irq versions of the netif_tx_lock
functions since xmit_lock is meant to be a BH-disabling lock.

This is pretty much a straight text substitution except for a small
bug fix in winbond.  It currently uses
netif_stop_queue/spin_unlock_wait to stop transmission.  This is
unsafe as an IRQ can potentially wake up the queue.  So it is safer to
use netif_tx_disable.

The hamradio bits used spin_lock_irq but it is unnecessary as
xmit_lock must never be taken in an IRQ handler.
Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      932ff279
    • J
      [SECMARK]: Add new packet controls to SELinux · 4e5ab4cb
      由 James Morris 提交于 
      Add new per-packet access controls to SELinux, replacing the old
packet controls.

Packets are labeled with the iptables SECMARK and CONNSECMARK targets,
then security policy for the packets is enforced with these controls.

To allow for a smooth transition to the new controls, the old code is
still present, but not active by default.  To restore previous
behavior, the old controls may be activated at runtime by writing a
'1' to /selinux/compat_net, and also via the kernel boot parameter
selinux_compat_net.  Switching between the network control models
requires the security load_policy permission.  The old controls will
probably eventually be removed and any continued use is discouraged.

With this patch, the new secmark controls for SElinux are disabled by
default, so existing behavior is entirely preserved, and the user is
not affected at all.

It also provides a config option to enable the secmark controls by
default (which can always be overridden at boot and runtime).  It is
also noted in the kconfig help that the user will need updated
userspace if enabling secmark controls for SELinux and that they'll
probably need the SECMARK and CONNMARK targets, and conntrack protocol
helpers, although such decisions are beyond the scope of kernel
configuration.
Signed-off-by: NJames Morris <jmorris@namei.org>
Signed-off-by: NAndrew Morton <akpm@osdl.org>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4e5ab4cb
    • R
      IPoIB: Mention RFC numbers in documentation · ac83cbaa
      由 Roland Dreier 提交于 
      Now that the IETF has released RFCs covering IPoIB, give the numbers in
the documentation for IPoIB.
Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      ac83cbaa
  7. 13 6月, 2006 1 次提交
  9. 11 6月, 2006 1 次提交
    • D
      [PATCH] Further alterations for memory barrier document · 670bd95e
      由 David Howells 提交于 
      From: David Howells <dhowells@redhat.com>

Apply some alterations to the memory barrier document that I worked out
with Paul McKenney of IBM, plus some of the alterations suggested by Alan
Stern.

The following changes were made:

 (*) One of the examples given for what can happen with overlapping memory
     barriers was wrong.

 (*) The description of general memory barriers said that a general barrier is
     a combination of a read barrier and a write barrier.  This isn't entirely
     true: it implies both, but is more than a combination of both.

 (*) The first example in the "SMP Barrier Pairing" section was wrong: the
     loads around the read barrier need to touch the memory locations in the
     opposite order to the stores around the write barrier.

 (*) Added a note to make explicit that the loads should be in reverse order to
     the stores.

 (*) Adjusted the diagrams in the "Examples Of Memory Barrier Sequences"
     section to make them clearer.  Added a couple of diagrams to make it more
     clear as to how it could go wrong without the barrier.

 (*) Added a section on memory speculation.

 (*) Dropped any references to memory allocation routines doing memory
     barriers.  They may do sometimes, but it can't be relied on.  This may be
     worthy of further documentation later.

 (*) Made the fact that a LOCK followed by an UNLOCK should not be considered a
     full memory barrier more explicit and gave an example.
Signed-off-by: NDavid Howells <dhowells@redhat.com>
Acked-by: NPaul E. McKenney <paulmck@us.ibm.com>
Signed-off-by: NAndrew Morton <akpm@osdl.org>
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      670bd95e
  11. 10 6月, 2006 2 次提交
  13. 09 6月, 2006 1 次提交
  15. 06 6月, 2006 1 次提交
  17. 03 6月, 2006 1 次提交
  19. 22 5月, 2006 1 次提交
  21. 18 5月, 2006 1 次提交
    • S
      [PATCH] sbp2: consolidate workarounds · 24d3bf88
      由 Stefan Richter 提交于 
      Grand unification of the three types of workarounds we have so far.

The "skip mode page 8" workaround is now limited to devices which
pretend to be of TYPE_DISK instead of TYPE_RBC. This workaround is no
longer enabled for Initio bridges.

Patch update in anticipation of more workarounds:
 - Add module parameter "workarounds".
 - Deprecate parameter "force_inquiry_hack".
 - Compose the blacklist of a compound type for better readability and
   extensibility.
 - Remove a now unused #define.
Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      24d3bf88
  23. 17 5月, 2006 2 次提交
  25. 16 5月, 2006 3 次提交
  27. 13 5月, 2006 1 次提交
  29. 10 5月, 2006 1 次提交
  31. 28 4月, 2006 6 次提交
  33. 26 4月, 2006 1 次提交
  35. 25 4月, 2006 2 次提交
  37. 20 4月, 2006 2 次提交