Eric Lee / smarc-fsl-linux-kernel

11 Sep, 2007

1 commit

16 Jul, 2007

1 commit

  • 56a68a500   more ACSI removal ... Browse Code »

    This patch removes some code that became dead code after the ATARI_ACSI
    removal.

    It also indirectly fixes the following bug introduced by
    commit c2bcf3b8978c291e1b7f6499475c8403a259d4d6:

    config ATARI_SLM
    tristate "Atari SLM laser printer support"
    - depends on ATARI && ATARI_ACSI!=n
    + depends on ATARI

    Acked-by: Geert Uytterhoeven
    Signed-off-by: Adrian Bunk
    Signed-off-by: Jens Axboe

    Adrian Bunk
     

15 Jul, 2007

1 commit

14 Jul, 2007

1 commit

  • e030dbf91   Merge branch 'ioat-md-accel-for-linus' of git://lost.foo-projects.org/~dwillia2/git/iop ... Browse Code »

    * 'ioat-md-accel-for-linus' of git://lost.foo-projects.org/~dwillia2/git/iop: (28 commits)
    ioatdma: add the unisys "i/oat" pci vendor/device id
    ARM: Add drivers/dma to arch/arm/Kconfig
    iop3xx: surface the iop3xx DMA and AAU units to the iop-adma driver
    iop13xx: surface the iop13xx adma units to the iop-adma driver
    dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines
    md: remove raid5 compute_block and compute_parity5
    md: handle_stripe5 - request io processing in raid5_run_ops
    md: handle_stripe5 - add request/completion logic for async expand ops
    md: handle_stripe5 - add request/completion logic for async read ops
    md: handle_stripe5 - add request/completion logic for async check ops
    md: handle_stripe5 - add request/completion logic for async compute ops
    md: handle_stripe5 - add request/completion logic for async write ops
    md: common infrastructure for running operations with raid5_run_ops
    md: raid5_run_ops - run stripe operations outside sh->lock
    raid5: replace custom debug PRINTKs with standard pr_debug
    raid5: refactor handle_stripe5 and handle_stripe6 (v3)
    async_tx: add the async_tx api
    xor: make 'xor_blocks' a library routine for use with async_tx
    dmaengine: make clients responsible for managing channels
    dmaengine: refactor dmaengine around dma_async_tx_descriptor
    ...

    Linus Torvalds
     

13 Jul, 2007

2 commits

12 Jul, 2007

1 commit

11 Jul, 2007

6 commits

09 Jul, 2007

1 commit

09 Jun, 2007

1 commit

  • 64b85006f   USB: cxacru: add Documentation file ... Browse Code »

    The sysfs attributes for exposing cxacru statistics/status information with
    possible values is now explained in Documentation/networking/cxacru.txt
    including information on the writable adsl_state attribute's commands and a
    sample of the kernel log format.

    Signed-off-by: Simon Arlott
    Cc: Duncan Sands
    Signed-off-by: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Simon Arlott
     

31 May, 2007

1 commit

18 May, 2007

1 commit

09 May, 2007

2 commits

28 Apr, 2007

1 commit

27 Apr, 2007

2 commits

  • 651350d10   [AF_RXRPC]: Add an interface to the AF_RXRPC module for the AFS filesystem to use ... Browse Code »

    Add an interface to the AF_RXRPC module so that the AFS filesystem module can
    more easily make use of the services available. AFS still opens a socket but
    then uses the action functions in lieu of sendmsg() and registers an intercept
    functions to grab messages before they're queued on the socket Rx queue.

    This permits AFS (or whatever) to:

    (1) Avoid the overhead of using the recvmsg() call.

    (2) Use different keys directly on individual client calls on one socket
    rather than having to open a whole slew of sockets, one for each key it
    might want to use.

    (3) Avoid calling request_key() at the point of issue of a call or opening of
    a socket. This is done instead by AFS at the point of open(), unlink() or
    other VFS operation and the key handed through.

    (4) Request the use of something other than GFP_KERNEL to allocate memory.

    Furthermore:

    (*) The socket buffer markings used by RxRPC are made available for AFS so
    that it can interpret the cooked RxRPC messages itself.

    (*) rxgen (un)marshalling abort codes are made available.

    The following documentation for the kernel interface is added to
    Documentation/networking/rxrpc.txt:

    =========================
    AF_RXRPC KERNEL INTERFACE
    =========================

    The AF_RXRPC module also provides an interface for use by in-kernel utilities
    such as the AFS filesystem. This permits such a utility to:

    (1) Use different keys directly on individual client calls on one socket
    rather than having to open a whole slew of sockets, one for each key it
    might want to use.

    (2) Avoid having RxRPC call request_key() at the point of issue of a call or
    opening of a socket. Instead the utility is responsible for requesting a
    key at the appropriate point. AFS, for instance, would do this during VFS
    operations such as open() or unlink(). The key is then handed through
    when the call is initiated.

    (3) Request the use of something other than GFP_KERNEL to allocate memory.

    (4) Avoid the overhead of using the recvmsg() call. RxRPC messages can be
    intercepted before they get put into the socket Rx queue and the socket
    buffers manipulated directly.

    To use the RxRPC facility, a kernel utility must still open an AF_RXRPC socket,
    bind an addess as appropriate and listen if it's to be a server socket, but
    then it passes this to the kernel interface functions.

    The kernel interface functions are as follows:

    (*) Begin a new client call.

    struct rxrpc_call *
    rxrpc_kernel_begin_call(struct socket *sock,
    struct sockaddr_rxrpc *srx,
    struct key *key,
    unsigned long user_call_ID,
    gfp_t gfp);

    This allocates the infrastructure to make a new RxRPC call and assigns
    call and connection numbers. The call will be made on the UDP port that
    the socket is bound to. The call will go to the destination address of a
    connected client socket unless an alternative is supplied (srx is
    non-NULL).

    If a key is supplied then this will be used to secure the call instead of
    the key bound to the socket with the RXRPC_SECURITY_KEY sockopt. Calls
    secured in this way will still share connections if at all possible.

    The user_call_ID is equivalent to that supplied to sendmsg() in the
    control data buffer. It is entirely feasible to use this to point to a
    kernel data structure.

    If this function is successful, an opaque reference to the RxRPC call is
    returned. The caller now holds a reference on this and it must be
    properly ended.

    (*) End a client call.

    void rxrpc_kernel_end_call(struct rxrpc_call *call);

    This is used to end a previously begun call. The user_call_ID is expunged
    from AF_RXRPC's knowledge and will not be seen again in association with
    the specified call.

    (*) Send data through a call.

    int rxrpc_kernel_send_data(struct rxrpc_call *call, struct msghdr *msg,
    size_t len);

    This is used to supply either the request part of a client call or the
    reply part of a server call. msg.msg_iovlen and msg.msg_iov specify the
    data buffers to be used. msg_iov may not be NULL and must point
    exclusively to in-kernel virtual addresses. msg.msg_flags may be given
    MSG_MORE if there will be subsequent data sends for this call.

    The msg must not specify a destination address, control data or any flags
    other than MSG_MORE. len is the total amount of data to transmit.

    (*) Abort a call.

    void rxrpc_kernel_abort_call(struct rxrpc_call *call, u32 abort_code);

    This is used to abort a call if it's still in an abortable state. The
    abort code specified will be placed in the ABORT message sent.

    (*) Intercept received RxRPC messages.

    typedef void (*rxrpc_interceptor_t)(struct sock *sk,
    unsigned long user_call_ID,
    struct sk_buff *skb);

    void
    rxrpc_kernel_intercept_rx_messages(struct socket *sock,
    rxrpc_interceptor_t interceptor);

    This installs an interceptor function on the specified AF_RXRPC socket.
    All messages that would otherwise wind up in the socket's Rx queue are
    then diverted to this function. Note that care must be taken to process
    the messages in the right order to maintain DATA message sequentiality.

    The interceptor function itself is provided with the address of the socket
    and handling the incoming message, the ID assigned by the kernel utility
    to the call and the socket buffer containing the message.

    The skb->mark field indicates the type of message:

    MARK MEANING
    =============================== =======================================
    RXRPC_SKB_MARK_DATA Data message
    RXRPC_SKB_MARK_FINAL_ACK Final ACK received for an incoming call
    RXRPC_SKB_MARK_BUSY Client call rejected as server busy
    RXRPC_SKB_MARK_REMOTE_ABORT Call aborted by peer
    RXRPC_SKB_MARK_NET_ERROR Network error detected
    RXRPC_SKB_MARK_LOCAL_ERROR Local error encountered
    RXRPC_SKB_MARK_NEW_CALL New incoming call awaiting acceptance

    The remote abort message can be probed with rxrpc_kernel_get_abort_code().
    The two error messages can be probed with rxrpc_kernel_get_error_number().
    A new call can be accepted with rxrpc_kernel_accept_call().

    Data messages can have their contents extracted with the usual bunch of
    socket buffer manipulation functions. A data message can be determined to
    be the last one in a sequence with rxrpc_kernel_is_data_last(). When a
    data message has been used up, rxrpc_kernel_data_delivered() should be
    called on it..

    Non-data messages should be handled to rxrpc_kernel_free_skb() to dispose
    of. It is possible to get extra refs on all types of message for later
    freeing, but this may pin the state of a call until the message is finally
    freed.

    (*) Accept an incoming call.

    struct rxrpc_call *
    rxrpc_kernel_accept_call(struct socket *sock,
    unsigned long user_call_ID);

    This is used to accept an incoming call and to assign it a call ID. This
    function is similar to rxrpc_kernel_begin_call() and calls accepted must
    be ended in the same way.

    If this function is successful, an opaque reference to the RxRPC call is
    returned. The caller now holds a reference on this and it must be
    properly ended.

    (*) Reject an incoming call.

    int rxrpc_kernel_reject_call(struct socket *sock);

    This is used to reject the first incoming call on the socket's queue with
    a BUSY message. -ENODATA is returned if there were no incoming calls.
    Other errors may be returned if the call had been aborted (-ECONNABORTED)
    or had timed out (-ETIME).

    (*) Record the delivery of a data message and free it.

    void rxrpc_kernel_data_delivered(struct sk_buff *skb);

    This is used to record a data message as having been delivered and to
    update the ACK state for the call. The socket buffer will be freed.

    (*) Free a message.

    void rxrpc_kernel_free_skb(struct sk_buff *skb);

    This is used to free a non-DATA socket buffer intercepted from an AF_RXRPC
    socket.

    (*) Determine if a data message is the last one on a call.

    bool rxrpc_kernel_is_data_last(struct sk_buff *skb);

    This is used to determine if a socket buffer holds the last data message
    to be received for a call (true will be returned if it does, false
    if not).

    The data message will be part of the reply on a client call and the
    request on an incoming call. In the latter case there will be more
    messages, but in the former case there will not.

    (*) Get the abort code from an abort message.

    u32 rxrpc_kernel_get_abort_code(struct sk_buff *skb);

    This is used to extract the abort code from a remote abort message.

    (*) Get the error number from a local or network error message.

    int rxrpc_kernel_get_error_number(struct sk_buff *skb);

    This is used to extract the error number from a message indicating either
    a local error occurred or a network error occurred.

    Signed-off-by: David Howells
    Signed-off-by: David S. Miller

    David Howells
     
  • 17926a793   [AF_RXRPC]: Provide secure RxRPC sockets for use by userspace and kernel both ... Browse Code »

    Provide AF_RXRPC sockets that can be used to talk to AFS servers, or serve
    answers to AFS clients. KerberosIV security is fully supported. The patches
    and some example test programs can be found in:

    http://people.redhat.com/~dhowells/rxrpc/

    This will eventually replace the old implementation of kernel-only RxRPC
    currently resident in net/rxrpc/.

    Signed-off-by: David Howells
    Signed-off-by: David S. Miller

    David Howells
     

26 Apr, 2007

6 commits

25 Apr, 2007

1 commit

26 Mar, 2007

1 commit

  • 954b2e7f4   [NET] AX.25 Kconfig and docs updates and fixes ... Browse Code »

    o The AX.25 Howto is unmaintained since several years. I've replaced it
    with a wiki at http://www.linux-ax25.org which provides more uptodate
    information.
    o Change default for AX25_DAMA_SLAVE to Y. AX25_DAMA_SLAVE only compiles
    in support for DAMA but doesn't activate it. I hope this gets Linux
    distributions to ship their AX.25 kernels with AX25_DAMA_SLAVE enabled.
    The price for this would be very small.
    o Delete historic changelog from comments, that's what SCM systems are
    meant to do.
    o ---help--- in Kconfig looks so yellingly eye insulting. Use just help.
    o Rewrite the commented out piece of old Linux 2.4 configuration language
    to Kconfig for consistency.
    o Fixup dependencies.

    Signed-off-by: Ralf Baechle
    Signed-off-by: David S. Miller

    Ralf Baechle
     

01 Mar, 2007

1 commit

12 Dec, 2006

1 commit

  • 5fce9a2da   [DCCP]: Update documentation ... Browse Code »

    As Eddie Kohler points out the RFC is Proposed Standard not experimental.
    Also removed documentation about deprecated socket option.

    Signed-off-by: Ian McDonald
    Signed-off-by: Gerrit Renker
    Signed-off-by: Arnaldo Carvalho de Melo

    Ian McDonald
     

07 Dec, 2006

1 commit

03 Dec, 2006

7 commits

  • 2b5f6dcce   [XFRM]: Fix aevent structuring to be more complete. ... Browse Code »

    aevents can not uniquely identify an SA. We break the ABI with this
    patch, but consensus is that since it is not yet utilized by any
    (known) application then it is fine (better do it now than later).

    Signed-off-by: Jamal Hadi Salim
    Signed-off-by: David S. Miller

    Jamal Hadi Salim
     
  • 82e3ab9db   [DCCP]: Adds the tx buffer sysctls ... Browse Code »

    This one got lost on the way from Ian to Gerrit to me, fix it.

    Signed-off-by: Ian McDonald
    Signed-off-by: Arnaldo Carvalho de Melo

    Ian McDonald
     
  • ddfe10b82   [DCCP]: Update Documentation ... Browse Code »

    This patch just updates DCCP documentation a bit.

    Signed-off-by: Ian McDonald
    Signed-off-by: Arnaldo Carvalho de Melo

    Ian McDonald
     
  • ba4e58eca   [NET]: Supporting UDP-Lite (RFC 3828) in Linux ... Browse Code »

    This is a revision of the previously submitted patch, which alters
    the way files are organized and compiled in the following manner:

    * UDP and UDP-Lite now use separate object files
    * source file dependencies resolved via header files
    net/ipv{4,6}/udp_impl.h
    * order of inclusion files in udp.c/udplite.c adapted
    accordingly

    [NET/IPv4]: Support for the UDP-Lite protocol (RFC 3828)

    This patch adds support for UDP-Lite to the IPv4 stack, provided as an
    extension to the existing UDPv4 code:
    * generic routines are all located in net/ipv4/udp.c
    * UDP-Lite specific routines are in net/ipv4/udplite.c
    * MIB/statistics support in /proc/net/snmp and /proc/net/udplite
    * shared API with extensions for partial checksum coverage

    [NET/IPv6]: Extension for UDP-Lite over IPv6

    It extends the existing UDPv6 code base with support for UDP-Lite
    in the same manner as per UDPv4. In particular,
    * UDPv6 generic and shared code is in net/ipv6/udp.c
    * UDP-Litev6 specific extensions are in net/ipv6/udplite.c
    * MIB/statistics support in /proc/net/snmp6 and /proc/net/udplite6
    * support for IPV6_ADDRFORM
    * aligned the coding style of protocol initialisation with af_inet6.c
    * made the error handling in udpv6_queue_rcv_skb consistent;
    to return `-1' on error on all error cases
    * consolidation of shared code

    [NET]: UDP-Lite Documentation and basic XFRM/Netfilter support

    The UDP-Lite patch further provides
    * API documentation for UDP-Lite
    * basic xfrm support
    * basic netfilter support for IPv4 and IPv6 (LOG target)

    Signed-off-by: Gerrit Renker
    Signed-off-by: David S. Miller

    Gerrit Renker
     
  • 2e2e9e92b   [DCCP]: Add sysctls to control retransmission behaviour ... Browse Code »

    This adds 3 sysctls which govern the retransmission behaviour of DCCP control
    packets (3way handshake, feature negotiation).

    It removes 4 FIXMEs from the code.

    The close resemblance of sysctl variables to their TCP analogues is emphasised
    not only by their name, but also by giving them the same initial values.
    This is useful since there is not much practical experience with DCCP yet.

    Furthermore, with regard to the previous patch, it is now possible to limit
    the number of keepalive-Responses by setting net.dccp.default.request_retries
    (also a bit like in TCP).

    Lastly, added documentation of all existing DCCP sysctls.

    Signed-off-by: Gerrit Renker
    Signed-off-by: Arnaldo Carvalho de Melo

    Gerrit Renker
     
  • 6f4e5fff1   [DCCP]: Support for partial checksums (RFC 4340, sec. 9.2) ... Browse Code »

    This patch does the following:
    a) introduces variable-length checksums as specified in [RFC 4340, sec. 9.2]
    b) provides necessary socket options and documentation as to how to use them
    c) basic support and infrastructure for the Minimum Checksum Coverage feature
    [RFC 4340, sec. 9.2.1]: acceptability tests, user notification and user
    interface

    In addition, it

    (1) fixes two bugs in the DCCPv4 checksum computation:
    * pseudo-header used checksum_len instead of skb->len
    * incorrect checksum coverage calculation based on dccph_x
    (2) removes dccp_v4_verify_checksum() since it reduplicates code of the
    checksum computation; code calling this function is updated accordingly.
    (3) now uses skb_checksum(), which is safer than checksum_partial() if the
    sk_buff has is a non-linear buffer (has pages attached to it).
    (4) fixes an outstanding TODO item:
    * If P.CsCov is too large for the packet size, drop packet and return.

    The code has been tested with applications, the latest version of tcpdump now
    comes with support for partial DCCP checksums.

    Signed-off-by: Gerrit Renker
    Signed-off-by: Arnaldo Carvalho de Melo

    Gerrit Renker
     
  • ef56e622c   [NET] ip-sysctl.txt: Alphabetize. ... Browse Code »

    Rearrange TCP entries in alpha order.

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

    Stephen Hemminger