public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] vfs patches
Date: Sat, 17 May 2008 08:19:07 +0100	[thread overview]
Message-ID: <20080517071907.GY13907@ZenIV.linux.org.uk> (raw)

	Misc VFS fixes.  Please, pull from 
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ for-linus

Summary:
Al Viro (8):
      take init_files to fs/file.c
      dup_fd() fixes, part 1
      dup_fd() part 2
      dup_fd() - part 3
      dup_fd() part 4 - race fix
      avoid multiplication overflows and signedness issues for max_fds
      get rid of leak in compat_execve()
      return to old errno choice in mkdir() et.al.

WANG Cong (2):
      [Patch] fs/binfmt_elf.c: fix a wrong free
      [Patch] fs/binfmt_elf.c: fix wrong return values

Diffstat:
 arch/alpha/kernel/init_task.c     |    1 -
 arch/arm/kernel/init_task.c       |    1 -
 arch/avr32/kernel/init_task.c     |    1 -
 arch/blackfin/kernel/init_task.c  |    1 -
 arch/cris/kernel/process.c        |    1 -
 arch/frv/kernel/init_task.c       |    1 -
 arch/h8300/kernel/init_task.c     |    1 -
 arch/ia64/kernel/init_task.c      |    1 -
 arch/m32r/kernel/init_task.c      |    1 -
 arch/m68k/kernel/process.c        |    1 -
 arch/m68knommu/kernel/init_task.c |    1 -
 arch/mips/kernel/init_task.c      |    1 -
 arch/mn10300/kernel/init_task.c   |    1 -
 arch/parisc/kernel/init_task.c    |    1 -
 arch/powerpc/kernel/init_task.c   |    1 -
 arch/s390/kernel/init_task.c      |    1 -
 arch/sh/kernel/init_task.c        |    1 -
 arch/sparc/kernel/init_task.c     |    1 -
 arch/sparc64/kernel/init_task.c   |    1 -
 arch/um/kernel/init_task.c        |    1 -
 arch/v850/kernel/init_task.c      |    1 -
 arch/x86/kernel/init_task.c       |    1 -
 arch/xtensa/kernel/init_task.c    |    1 -
 fs/binfmt_elf.c                   |    9 +-
 fs/compat.c                       |    4 +-
 fs/exec.c                         |   12 ++-
 fs/file.c                         |  152 ++++++++++++++++++++++++++++++++++++-
 fs/namei.c                        |   12 ++-
 include/linux/binfmts.h           |    1 +
 include/linux/fdtable.h           |    1 +
 include/linux/init_task.h         |   23 +------
 kernel/fork.c                     |  130 -------------------------------
 kernel/sysctl.c                   |    5 +-
 33 files changed, 180 insertions(+), 192 deletions(-)


             reply	other threads:[~2008-05-17  7:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-17  7:19 Al Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-23  9:52 [git pull] vfs patches Al Viro
2008-08-01 15:36 Al Viro
2008-08-03 14:08 ` Roland Dreier
2008-08-03 14:53   ` Al Viro
2008-06-25  3:32 Al Viro
2008-04-26  2:02 [git pull] VFS patches Al Viro
2008-04-26 11:01 ` Ingo Molnar
2008-04-26 13:35   ` Matthew Wilcox
2008-04-26 13:44     ` Ingo Molnar
2008-04-26 15:43       ` Ingo Molnar
2008-04-26 19:02     ` Mike Galbraith
2008-05-20 12:04 ` hooanon05
2008-03-25  8:17 [git pull] vfs patches Al Viro
2008-03-25 16:05 ` Linus Torvalds
2008-03-25 18:00   ` Al Viro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080517071907.GY13907@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox