10 Sep, 2005
20 commits
-
This patch modifies ext2 to call the inode_init_security LSM hook to obtain
the security attribute for a newly created inode and to set the resulting
attribute on the new inode. This parallels the existing processing for
setting ACLs on newly created inodes.Signed-off-by: Stephen Smalley
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
The following patch set enables atomic security labeling of newly created
inodes by altering the fs code to invoke a new LSM hook to obtain the security
attribute to apply to a newly created inode and to set up the incore inode
security state during the inode creation transaction. This parallels the
existing processing for setting ACLs on newly created inodes. Otherwise, it
is possible for new inodes to be accessed by another thread via the dcache
prior to complete security setup (presently handled by the
post_create/mkdir/... LSM hooks in the VFS) and a newly created inode may be
left unlabeled on the disk in the event of a crash. SELinux presently works
around the issue by ensuring that the incore inode security label is
initialized to a special SID that is inaccessible to unprivileged processes
(in accordance with policy), thereby preventing inappropriate access but
potentially causing false denials on legitimate accesses. A simple test
program demonstrates such false denials on SELinux, and the patch solves the
problem. Similar such false denials have been encountered in real
applications.This patch defines a new inode_init_security LSM hook to obtain the security
attribute to apply to a newly created inode and to set up the incore inode
security state for it, and adds a corresponding hook function implementation
to SELinux.Signed-off-by: Stephen Smalley
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Support for the new RBHMA4500 eval board for the TX4938. General update
from the 8250 ancestor of this driver. Replace use of deprecated
interfaces.Signed-off-by: Ralf Baechle
Signed-off-by: Atsushi Nemoto
Acked-by: Russell King
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Update the file systems in fs/ implementing a delete_inode() callback to
call truncate_inode_pages(). One implementation note: In developing this
patch I put the calls to truncate_inode_pages() at the very top of those
filesystems delete_inode() callbacks in order to retain the previous
behavior. I'm guessing that some of those could probably be optimized.Signed-off-by: Mark Fasheh
Acked-by: Christoph Hellwig
Signed-off-by: Hugh Dickins
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Allow file systems supporting ->delete_inode() to call
truncate_inode_pages() on their own. OCFS2 wants this so it can query the
cluster before making a final decision on whether to wipe an inode from
disk or not. In some corner cases an inode marked on the local node via
voting may not actually get orphaned. A good example is node death before
the transaction moving the inode to the orphan dir commits to the journal.
Without this patch, the truncate_inode_pages() call in
generic_delete_inode() would discard valid data for such inodes.During earlier discussion in the 2.6.13 merge plan thread, Christoph
Hellwig indicated that other file systems might also find this useful.IMHO, the best solution would be to just allow ->drop_inode() to do the
cluster query but it seems that would require a substantial reworking of
that section of the code. Assuming it is safe to call write_inode_now() in
ocfs2_delete_inode() for those inodes which won't actually get wiped, this
solution should get us by for now.Trivial testing of this patch (and a related OCFS2 update) has shown this
to avoid the corruption I'm seeing.Signed-off-by: Mark Fasheh
Acked-by: Christoph Hellwig
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Looks like the help comment for MPC834x got merged incorrectly.
Signed-off-by: Kumar Gala
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Fix a typo involving CONFIG_ACPI_SRAT.
Signed-off-by: Magnus Damm
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
An oversight. We don't want to carry the IO scheduler's "we hold exclusive fs
resources" hint over to the child across fork().Acked-by: Jens Axboe
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
Remove the weird and apparently unnecessary logic in MP_processor_info() which
assumes that the BSP is the first one to run MP_processor_info(). On one of
my boxes that isn't true and cpu_possible_map gets the wrong value.Cc: Zwane Mwaikambo
Cc: Alexander Nyberg
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds -
This makes ACPI_BLACKLIST_YEAR be consistently defined when ACPI is
enabled, regardless of whether we're on x86 or not, and thus avoids
bogus -Wundef warnings on ia64.Signed-off-by: Linus Torvalds
-
The legacy PIC's name is "i8259".
Signed-off-by: Karsten Wiese
Signed-off-by: Vojtech Pavlik
Signed-off-by: Linus Torvalds -
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
Passes -m64 to sparse on uml/amd64, tells sparse to stay out of
USER_OBJS.Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
Removed gratuitous includes of asm/serial.h in synklinkmp and ip2main.
Allows to remove the rest of "broken on sparc32" in drivers/char - this
stuff doesn't break the build anymore. Since it got zero testing, it almost
certainly won't work there, though...Signed-off-by: Al Viro
Acked-by: Russell King
Signed-off-by: Linus Torvalds -
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
void * is not the same as void *...
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
Previous INTx cleanup patch had a bug that was not caught. I found
this last night during testing and can confirm that it is now 100%
working.Signed-off-by: Brett Russ
Signed-off-by: Greg Kroah-Hartman
Acked-by: Jeff Garzik
Signed-off-by: Linus Torvalds
09 Sep, 2005
20 commits
-
The pciconfig_iobase, pciconfig_read and pciconfig_write system calls
were only implemented for 32-bit processes; for 64-bit processes they
returned an ENOSYS error. This allows them to be used by 64-bit
processes as well. The X server uses pciconfig_iobase at least, and
this change is necessary to allow a 64-bit X server to work on my G5.Signed-off-by: Paul Mackerras
-
I/O memory accessors. Big-endian version. For those busses/devices
that do export big-endian I/O memory.Of notable relevance/reference:
http://lwn.net/Articles/132804/
http://ozlabs.org/pipermail/linuxppc-embedded/2005-August/019798.html
http://ozlabs.org/pipermail/linuxppc-embedded/2005-August/019752.htmlSigned-Off-By: Arthur Othieno
Signed-off-by: Paul Mackerras -
This patch pulls the PCI-related junk out of struct device_node and
puts it in a separate structure, struct pci_dn. The device_node now
just has a void * pointer in it, which points to a struct pci_dn for
nodes that represent PCI devices. It could potentially be used in
future for device-specific data for other sorts of devices, such as
virtual I/O devices.Signed-off-by: Paul Mackerras
-
Remove asm-ppc64/segment.h now that all users are gone.
Signed-off-by: Kumar Gala
Signed-off-by: Paul Mackerras -
In PPC64 there are number of problems in arch/ppc64/boot/main.c that
prevent a kernel from making use of a large (greater than ~16MB) INITRD.
This is 64 bit architecture and really large INITRD images should be
possible.Simply put the existing code has a fixed reservation (claim) address and
once the kernel plus initrd image are large enough to pass this address
all sorts of bad things occur. The fix is the dynamically establish the
first claim address above the loaded kernel plus initrd (plus some
"padding" and rounding). If PROG_START is defined this will be used as
the minimum safe address - currently known to be 0x01400000 for the
firmwares tested so far.Signed-off-by: Mark Bellon
Signed-off-by: Paul Mackerras -
Fix __power64__ typo that should be __powerpc64__ instead.
Signed-off-by: Jon Loeliger
Signed-off-by: Kumar Gala
Signed-off-by: Paul Mackerras -
This patch cleans up the output generated by ppc64 builds.
Signed-off-by: Geoff Levand
Signed-off-by: Paul Mackerras -
Signed-off-by: Geoff Levand
Signed-off-by: Paul Mackerras -
Merge a few asm-ppc and asm-ppc64 header files.
Note: the merge of setup.h intentionally does not carry
forward the m68k cruft. That means this patch continues
to break the already broken amiga on the ppc32.Signed-off-by: Jon Loeliger
Signed-off-by: Kumar Gala
Signed-off-by: Paul Mackerras -
Make check_bugs() static inline and remove it from syscalls.c.
Signed-off-by: Jon Loeliger
Signed-off-by: Kumar Gala
Signed-off-by: Paul Mackerras -
Standardize on _ASM_POWERPC_... prefix for all #include
exclusion symbols. Fixup all the non-compilers.Signed-off-by: Jon Loeliger
Signed-off-by: Kumar Gala
Signed-off-by: Paul Mackerras -
The earlier commit 8d9273918635f0301368c01b56c03a6f339e8d51
(Consolidate early console and PPCDBG code) broke iSeries because
it caused unregister_console(&udbg_console) to be called
unconditionally. iSeries never registers the udbg_console.This just reverts part of the change.
Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
The SPARSEMEM EXTREME code (802f192e4a600f7ef84ca25c8b818c8830acef5a) that
went in yesterday broke PPC64 for !CONFIG_NUMA.The problem is that (free|reserve)_bootmem don't take a page number as their
first argument, they take an address. Ruh roh.Booted on P5 LPAR, iSeries and G5.
Signed-off-by: Michael Ellerman
Signed-off-by: Paul Mackerras -
This fixes a severe bug in the bpa_iic driver that caused
all sorts of problems.We had been using incorrect priority values for inter processor
interrupts, which resulted in always doing CALL_FUNCTION
instead of RESCHEDULE or DEBUGGER_BREAK.The symptoms cured by this patch include bad performance on
SMP systems spurious kernel panics in the IPI code.Signed-off-by: Arnd Bergmann
Signed-off-by: Paul Mackerras -
* sata_mv: remove pci_intx(), now that the same function is in PCI core
* sata_sis: fix variable initialization bug, trim trailing whitespace -
Signed-off-by: Nathan Scott
-
Rework the 68x328 configuration and setup code. All 68x328 varients
share the same timer hardware. So extract that into its own file,
instead of keeping copies in each processors setup code.Signed-off-by: Greg Ungerer
Signed-off-by: Linus Torvalds
