From: Christophe Saout <christophe@saout.de>

- acpi_pci_link_get_irq() returns 0 on error, not -ENODEV.

- Fix mpparse.c tpyo.

This printk doesn't impart any information.

From: Jaroslav Kysela <perex@suse.cz>

The do_no_page() function in mm/memory.c does accounting for reserved pages
(++mm->rss), but in zap_pte_range() we don't decrement rss if the page was
reserved.

So don't account for PageReserved pages in the rss.  (Maybe it would be
better to fix zap_pte_range in the opposite direction..)

From: Adrian Bunk <bunk@fs.tum.de>

Remove CONFIG_KCORE_AOUT: the ability to present /proc/kcore in a.out
format.

I've checked with various arch maintainers.  It won't be missed.

We get a linkage error with CONFIG_KCORE_AOUT because there is no
implementation of kclist_add() and kclist_del().

Also fix a warning in the a.out version of read_kcore().

Maybe we should just remove kcore a.out support.  m68knommu and h8300 are
setting CONFIG_KCORE_AOUT in their defconfigs though.

From: <ffrederick@prov-liege.be>

Flesh out the bad_inode file and inode operations tables with new
additions.

From: Stephen Smalley <sds@epoch.ncsc.mil>

This patch corrects a typo in an ifdef that enables xattr operations for
special files in the ext2 code; otherwise, extended attributes cannot be
obtained or set on such inodes.

From: Stephen Smalley <sds@epoch.ncsc.mil>

This patch reworks the SELinux binprm hook functions to use a security
structure for the linux_binprm rather than directly stuffing the security
identifier into the void* security field.  It also performs some cleanup of
the SELinux binprm hook functions, and one miscellaneous fix.

From: Stephen Smalley <sds@epoch.ncsc.mil>, James Morris <jmorris@redhat.com>

This patch corrects several format specifiers in the SELinux security server
code.

From: Stephen Smalley <sds@epoch.ncsc.mil>, Arnd Bergmann <arnd@arndb.de>

This patch changes the SELinux avtab to use vmalloc/vfree; the table is too
large for kmalloc on s390.

From: Stephen Smalley <sds@epoch.ncsc.mil>, James Morris <jmorris@redhat.com>

This patch adds the appropriate #if around the F_*64 commands in the
selinux_file_fcntl hook function.

From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>

current bk 2.6.0 corrupts my ext3 filesystems, usually in the RESYNC dir
during a bk pull.  Checking the recent changes I noticed that the one in
fs/ext3/namei.c misses an endian conversion.  The attached patch fixes that
and works fine for me since 2 days now on PPC.

From: Andrey Panin <pazke@donpac.ru>

attached trivial patch fixes visws subarch kernel build.  It was broken by
2.6.0-test4 cpumask_t changes.

From: Oleg Drokin <green@namesys.com>

The conversion of reiserfs to not return errors from
writepage-outside-i_size was incorrect.  Fix.

The `user_specified' variable is used in cleanup_module() and hence cannot be
dropped from memory after module initialisation.

From: David Mosberger <davidm@napali.hpl.hp.com>,
	"Sharma, Arun" <arun.sharma@intel.com>

The truncate race fix assumed that a non-zero vma->vm_ops->nopage implies a
non-zero vma->vm_file.

The ia64 x86 emulation code breaks this assumption, so teach do_no_page() to
handle it.

From: Vinay K Nallamothu <vinay-rc@naturesoft.net>

drivers/net/ni5010.c:
This patch replaces cli/sti with spinlocks. Compiles fine though
untested.

From: <ffrederick@prov-liege.be>

Update the abi sysctl documentation.

From: <ffrederick@prov-liege.be>

The expected case is (sysctl_overcommit_memory == 0), so put that first.

From: <ffrederick@prov-liege.be>

Here's an _important_ kobject doc patch.

From: Rusty Russell <rusty@rustcorp.com.au>

Change the permissions on /proc/kallsyms.  As David M-T points out,
it's nice for analysis tools not to need root.  Place
cond_resched() to avoid starvation problems on non-preempt.

From: Rusty Russell <rusty@rustcorp.com.au>

Out by one error broke caching of results in /proc/kallsyms, slowing
reading to a crawl.

From: Thomas Schlichter <schlicht@uni-mannheim.de>

Make the `pci=noacpi' command line option work correctly.  It fixes
interrupt routing probems for (at least 3) people with broken ACPI BIOSes.

From: CaT <cat@zip.com.au>

Convert a whole bunch of struct initialisers into c99 format.

From: Domen Puncer <domen@coderock.org>

The problem in pcnet32 is, that it doesn't unregister pci, if there's no
hardware.

This patch solves the problem.

From: "Krishnakumar. R" <krishnakumar@naturesoft.net>

This patch removes the warning:

drivers/char/pcxx.c:124:8: warning: extra tokens at end of #endif directive

From: Geert Uytterhoeven <geert@linux-m68k.org>

On Fri, 22 Aug 2003, Linus Torvalds wrote:
> Javier Achirica:
>   o [wireless airo] Fix PCI unregister code

This patch causes a regression: if CONFIG_PCI is not set, it doesn't compile
anymore. Here's a fix. I also killed a dead variable and its corresponding
warning:

From: Ronald Bultje <rbultje@ronald.bitfreak.net>

I suddenly noticed that 2.6.0-test4 seems to have removed the struct
device->name field, apparently for memory consumption reasons. Linus
changed this to pci_name((zr)->pci_dev) in my driver, and that's almost
correct, except that it is the PCI device ID, and I'm not supposed to
touch it. Also, since it's only 4 bytes, all my device names now show
like 'DC1' (this should be 'DC10plus') and alike.

The attached patch fixes this by going back to the behaviour that we
used in 2.4.x: we use a separate name field in our private driver
struct.

From: Ronald Bultje <rbultje@ronald.bitfreak.net>

This patch adds some newlines between variable declarations and function
bodies. This was done on request by Francois Romieu.

From: Ronald Bultje <rbultje@ronald.bitfreak.net>

This patch changes some funky coding style (a.k.a. indent artifact) in
the function zoran_irq() to a somewhat more conservative coding style.
It was noticed by Francois Romieu.

From: Ronald Bultje <rbultje@ronald.bitfreak.net>

This patch adds pci_disable_device() to the card release function; we
already used pci_enable_device() in the card detection function.  This was
noticed by Francois Romieu.

From: Ronald Bultje <rbultje@ronald.bitfreak.net>

This patch adds a release callback which frees the video_device struct.
This is needed to prevent freeing memory before it's not in use anymore,
as described in http://lwn.net/Articles/36850/. Without this, the driver
will give a warning when loaded. It might crash when unloading (see
article), too. The video4linux patch (by Gerd Knorr) was accepted a week
(or 2?) ago, but I forgot to adapt my driver to it.

From: Ronald Bultje <rbultje@ronald.bitfreak.net>

This patch renames the debug symbol to zr_debug because debug is already
defined somewhere else. Without it, it will cause a symbol conflict when
compiling this driver statically into the kernel. This was noticed by
several people, including Linus himself.

From: Ronald Bultje <rbultje@ronald.bitfreak.net>

This patch fixes several memleaks in error cases when the setup of i2c
client drivers for video encoders/decoders fails. We forgot to free some
memory in various places. This was noticed by Francois Romieu.

From: Vinay K Nallamothu <vinay-rc@naturesoft.net>

s/spin_lock_irqrestore/spin_unlock_irqrestore/

It has no callers, is using the non-existent spin_lock_irqrestore(), and is
obviously very untested.  Kill.

I had second thoughts on this.

Reporting background writeout errors via close() only really makes sense if
allthe IO has completed anyway: ie, the app has had the fd open without
writing to it for many tens of seconds.

It would be OK if it was harmless, but it is not.  Changes are, applications
ignore errors from close().  So if an application does a fork/exit and the
child correctly does an fsync() of the fd, the close-on-exit will have wiped
out any accumulated EIO/ENOSPC errors.

Or if someone does dup()/close()/fsync(), the fsync() could fail to detect
earlier errors, thanks to the close.


So.  The clear-and-report of errors on close() makes the reporting of errors
on fsync/msync/fdatasync less reliable.

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>

The patch below fixes a 2.6 mm problem.  Without this patch, zeromapped
pages are not flushed properly when they are swapped out.

What happens is that the page->index field is zero for page table pages
corresponding to the zeromapped range.  This causes ptep_to_address() to
return an incorrect virtual address with the result that PTEs are never
invalidated at swap-out...

The fix below mirrors the remap_pmd_range() case.