Eric Lee / smarc-fsl-linux-kernel

09 Nov, 2011

1 commit

20 Oct, 2011

1 commit

27 Aug, 2011

1 commit

21 Jul, 2011

1 commit

  • b12acf163   MIPS: Wire up sendmmsg and renumber setns syscall. ... Browse Code »

    Renumbering was necessary because I had already wired up setns(2) in the
    linux-mips.org tree in commit c3fce54644cabbb90700cc3acc040718a377f609
    [MIPS: Wire up new sendmmsg syscall.] but the same syscall numbers were
    used by 7b21fddd087678a70ad64afc0f632e0f1071b092 [ns: Wire up the setns
    system call] resulting in a conflict.

    Signed-off-by: Ralf Baechle

    Ralf Baechle
     

29 May, 2011

1 commit

  • 7b21fddd0   ns: Wire up the setns system call ... Browse Code »

    32bit and 64bit on x86 are tested and working. The rest I have looked
    at closely and I can't find any problems.

    setns is an easy system call to wire up. It just takes two ints so I
    don't expect any weird architecture porting problems.

    While doing this I have noticed that we have some architectures that are
    very slow to get new system calls. cris seems to be the slowest where
    the last system calls wired up were preadv and pwritev. avr32 is weird
    in that recvmmsg was wired up but never declared in unistd.h. frv is
    behind with perf_event_open being the last syscall wired up. On h8300
    the last system call wired up was epoll_wait. On m32r the last system
    call wired up was fallocate. mn10300 has recvmmsg as the last system
    call wired up. The rest seem to at least have syncfs wired up which was
    new in the 2.6.39.

    v2: Most of the architecture support added by Daniel Lezcano
    v3: ported to v2.6.36-rc4 by: Eric W. Biederman
    v4: Moved wiring up of the system call to another patch
    v5: ported to v2.6.39-rc6
    v6: rebased onto parisc-next and net-next to avoid syscall conflicts.
    v7: ported to Linus's latest post 2.6.39 tree.

    >  arch/blackfin/include/asm/unistd.h     |    3 ++-
    >  arch/blackfin/mach-common/entry.S      |    1 +
    Acked-by: Mike Frysinger

    Oh - ia64 wiring looks good.
    Acked-by: Tony Luck

    Signed-off-by: Eric W. Biederman
    Signed-off-by: Linus Torvalds

    Eric W. Biederman
     

19 May, 2011

1 commit

11 May, 2011

1 commit

26 Mar, 2011

2 commits

19 Oct, 2010

1 commit

  • 547af560d   Merge branch 'upstream' of git://git.linux-mips.org/pub/scm/upstream-linus ... Browse Code »

    * 'upstream' of git://git.linux-mips.org/pub/scm/upstream-linus:
    MIPS: Enable ISA_DMA_API config to fix build failure
    MIPS: 32-bit: Fix build failure in asm/fcntl.h
    MIPS: Remove all generated vmlinuz* files on "make clean"
    MIPS: do_sigaltstack() expects userland pointers
    MIPS: Fix error values in case of bad_stack
    MIPS: Sanitize restart logics
    MIPS: secure_computing, syscall audit: syscall number should in r2, not r0.
    MIPS: Don't block signals if we'd failed to setup a sigframe

    Linus Torvalds
     

18 Oct, 2010

2 commits

  • 5b89c0044   MIPS: Fix error values in case of bad_stack ... Browse Code »

    We want EFAULT, not -

    Signed-off-by: Al Viro
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-arch@vger.kernel.org
    Cc: linux-mips@linux-mips.org
    Patchwork: https://patchwork.linux-mips.org/patch/1699/
    Signed-off-by: Ralf Baechle

    Al Viro
     
  • 8f5a00eb4   MIPS: Sanitize restart logics ... Browse Code »

    Put the original syscall number into ->regs[0] when we leave syscall
    with error. Use it in restart logics. Everything else will have
    it 0 since we pass through SAVE_SOME on all the ways in. Note that
    in places like bad_stack and inllegal_syscall we leave it 0 - it's not
    restartable.

    Signed-off-by: Al Viro
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-arch@vger.kernel.org
    Cc: linux-mips@linux-mips.org
    Patchwork: https://patchwork.linux-mips.org/patch/1698/
    Signed-off-by: Ralf Baechle

    Al Viro
     

05 Oct, 2010

1 commit

13 Oct, 2009

1 commit

  • a2e272554   net: Introduce recvmmsg socket syscall ... Browse Code »

    Meaning receive multiple messages, reducing the number of syscalls and
    net stack entry/exit operations.

    Next patches will introduce mechanisms where protocols that want to
    optimize this operation will provide an unlocked_recvmsg operation.

    This takes into account comments made by:

    . Paul Moore: sock_recvmsg is called only for the first datagram,
    sock_recvmsg_nosec is used for the rest.

    . Caitlin Bestler: recvmmsg now has a struct timespec timeout, that
    works in the same fashion as the ppoll one.

    If the underlying protocol returns a datagram with MSG_OOB set, this
    will make recvmmsg return right away with as many datagrams (+ the OOB
    one) it has received so far.

    . Rémi Denis-Courmont & Steven Whitehouse: If we receive N < vlen
    datagrams and then recvmsg returns an error, recvmmsg will return
    the successfully received datagrams, store the error and return it
    in the next call.

    This paves the way for a subsequent optimization, sk_prot->unlocked_recvmsg,
    where we will be able to acquire the lock only at batch start and end, not at
    every underlying recvmsg call.

    Signed-off-by: Arnaldo Carvalho de Melo
    Signed-off-by: David S. Miller

    Arnaldo Carvalho de Melo
     

21 Sep, 2009

1 commit

  • cdd6c482c   perf: Do the big rename: Performance Counters -> Performance Events ... Browse Code »

    Bye-bye Performance Counters, welcome Performance Events!

    In the past few months the perfcounters subsystem has grown out its
    initial role of counting hardware events, and has become (and is
    becoming) a much broader generic event enumeration, reporting, logging,
    monitoring, analysis facility.

    Naming its core object 'perf_counter' and naming the subsystem
    'perfcounters' has become more and more of a misnomer. With pending
    code like hw-breakpoints support the 'counter' name is less and
    less appropriate.

    All in one, we've decided to rename the subsystem to 'performance
    events' and to propagate this rename through all fields, variables
    and API names. (in an ABI compatible fashion)

    The word 'event' is also a bit shorter than 'counter' - which makes
    it slightly more convenient to write/handle as well.

    Thanks goes to Stephane Eranian who first observed this misnomer and
    suggested a rename.

    User-space tooling and ABI compatibility is not affected - this patch
    should be function-invariant. (Also, defconfigs were not touched to
    keep the size down.)

    This patch has been generated via the following script:

    FILES=$(find * -type f | grep -vE 'oprofile|[^K]config')

    sed -i \
    -e 's/PERF_EVENT_/PERF_RECORD_/g' \
    -e 's/PERF_COUNTER/PERF_EVENT/g' \
    -e 's/perf_counter/perf_event/g' \
    -e 's/nb_counters/nb_events/g' \
    -e 's/swcounter/swevent/g' \
    -e 's/tpcounter_event/tp_event/g' \
    $FILES

    for N in $(find . -name perf_counter.[ch]); do
    M=$(echo $N | sed 's/perf_counter/perf_event/g')
    mv $N $M
    done

    FILES=$(find . -name perf_event.*)

    sed -i \
    -e 's/COUNTER_MASK/REG_MASK/g' \
    -e 's/COUNTER/EVENT/g' \
    -e 's/\/event_id/g' \
    -e 's/counter/event/g' \
    -e 's/Counter/Event/g' \
    $FILES

    ... to keep it as correct as possible. This script can also be
    used by anyone who has pending perfcounters patches - it converts
    a Linux kernel tree over to the new naming. We tried to time this
    change to the point in time where the amount of pending patches
    is the smallest: the end of the merge window.

    Namespace clashes were fixed up in a preparatory patch - and some
    stylistic fallout will be fixed up in a subsequent patch.

    ( NOTE: 'counters' are still the proper terminology when we deal
    with hardware registers - and these sed scripts are a bit
    over-eager in renaming them. I've undone some of that, but
    in case there's something left where 'counter' would be
    better than 'event' we can undo that on an individual basis
    instead of touching an otherwise nicely automated patch. )

    Suggested-by: Stephane Eranian
    Acked-by: Peter Zijlstra
    Acked-by: Paul Mackerras
    Reviewed-by: Arjan van de Ven
    Cc: Mike Galbraith
    Cc: Arnaldo Carvalho de Melo
    Cc: Frederic Weisbecker
    Cc: Steven Rostedt
    Cc: Benjamin Herrenschmidt
    Cc: David Howells
    Cc: Kyle McMartin
    Cc: Martin Schwidefsky
    Cc: "David S. Miller"
    Cc: Thomas Gleixner
    Cc: "H. Peter Anvin"
    Cc:
    LKML-Reference:
    Signed-off-by: Ingo Molnar

    Ingo Molnar
     

18 Sep, 2009

1 commit

04 Aug, 2009

1 commit

03 Jul, 2009

1 commit

03 Apr, 2009

1 commit

28 Feb, 2009

1 commit

14 Jan, 2009

1 commit

05 Dec, 2008

2 commits

  • 08d30879a   MIPS: o32: Fix number of arguments to splice(2). ... Browse Code »

    The syscall code was assuming splice only takes 4 arguments so no stack
    arguments were being copied from the userspace stack to the kernel stack.
    As the result splice was likely to fail with EINVAL.

    Signed-off-by: Ralf Baechle

    Ralf Baechle
     
  • e807f9574   MIPS: Fix potential DOS by untrusted user app. ... Browse Code »

    On a 64 bit kernel if an o32 syscall was made with a syscall number less
    than 4000, we would read the function from outside of the bounds of the
    syscall table. This led to non-deterministic behavior including system
    crashes.

    While we were at it we reworked the 32 bit version as well to use fewer
    instructions. Both 32 and 64 bit versions are use the same code now.

    Signed-off-by: Vlad Malov
    Signed-off-by: David Daney
    Signed-off-by: Ralf Baechle

    Vlad Malov
     

28 Oct, 2008

2 commits

26 Aug, 2008

1 commit

20 Jul, 2008

1 commit

16 Jul, 2008

1 commit

20 Feb, 2008

1 commit

  • 6783fe625   [MIPS] Wire up the timerfd_*() o32 system calls ... Browse Code »

    This patch enables the system calls timerfd_create(), timerfd_settime()
    and timerfd_gettime() for MIPS architecture.

    Please see the following Bugzilla entry for more details:

    http://bugzilla.kernel.org/show_bug.cgi?id=10038

    This was tested using a Malta 4Kc board in both little-endian and
    big-endian modes. The unit test program is available from the URL
    above.

    Signed-off-by: Dmitri Vorobiev

    [Ralf: Added N64, N32 and O32 bits on 64-bit kernels.]
    Signed-off-by: Ralf Baechle

    Dmitri Vorobiev
     

06 Feb, 2008

1 commit

  • 4d672e7ac   timerfd: new timerfd API ... Browse Code »

    This is the new timerfd API as it is implemented by the following patch:

    int timerfd_create(int clockid, int flags);
    int timerfd_settime(int ufd, int flags,
    const struct itimerspec *utmr,
    struct itimerspec *otmr);
    int timerfd_gettime(int ufd, struct itimerspec *otmr);

    The timerfd_create() API creates an un-programmed timerfd fd. The "clockid"
    parameter can be either CLOCK_MONOTONIC or CLOCK_REALTIME.

    The timerfd_settime() API give new settings by the timerfd fd, by optionally
    retrieving the previous expiration time (in case the "otmr" parameter is not
    NULL).

    The time value specified in "utmr" is absolute, if the TFD_TIMER_ABSTIME bit
    is set in the "flags" parameter. Otherwise it's a relative time.

    The timerfd_gettime() API returns the next expiration time of the timer, or
    {0, 0} if the timerfd has not been set yet.

    Like the previous timerfd API implementation, read(2) and poll(2) are
    supported (with the same interface). Here's a simple test program I used to
    exercise the new timerfd APIs:

    http://www.xmailserver.org/timerfd-test2.c

    [akpm@linux-foundation.org: coding-style cleanups]
    [akpm@linux-foundation.org: fix ia64 build]
    [akpm@linux-foundation.org: fix m68k build]
    [akpm@linux-foundation.org: fix mips build]
    [akpm@linux-foundation.org: fix alpha, arm, blackfin, cris, m68k, s390, sparc and sparc64 builds]
    [heiko.carstens@de.ibm.com: fix s390]
    [akpm@linux-foundation.org: fix powerpc build]
    [akpm@linux-foundation.org: fix sparc64 more]
    Signed-off-by: Davide Libenzi
    Cc: Michael Kerrisk
    Cc: Thomas Gleixner
    Cc: Davide Libenzi
    Cc: Michael Kerrisk
    Cc: Martin Schwidefsky
    Signed-off-by: Heiko Carstens
    Cc: Michael Kerrisk
    Cc: Davide Libenzi
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Davide Libenzi
     

01 Aug, 2007

1 commit

12 Jun, 2007

1 commit

07 Mar, 2007

1 commit

30 Nov, 2006

1 commit

31 Oct, 2006

1 commit

20 Oct, 2006

1 commit

02 Oct, 2006

1 commit

27 Sep, 2006

1 commit

14 Jul, 2006

2 commits