There are currently two definitions of load_cr3, that essentially do the
same thing. This patch moves them all to processor.h.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/mmu_context_64.h |5 -
include/asm-x86/processor.h |7 +++
Paravirt guests need to inform the underlying hypervisor whenever the sp0
tss field changes. i386 already has such a function, and we use it for
x86_64 too. There's an unnecessary (for 64-bit) msr handling part in the
original
version, and it is placed around an ifdef. Making no more sense in
The thread_struct is not fundamentally different between architectures, and
this patch puts it in the common header. What's really unique for each of
them is enclosed in ifdefs.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/processor.h| 44
I hate to bring this again, but what if the admin in the container
mounts an external file system (eg. nfs, usb, loop mount from a file,
or via fuse), and that file system already has a device that we would
like to ban inside that container ?
Since anyway we will have to keep a white- (or
This patch moves the mm_segment_t structure definition to processor.h
This makes mmsegment.h file useless, and it is deleted.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/mmsegment.h |8
include/asm-x86/processor.h |5 +
This patch moves i387 definitions from processor_32.h and processor_64.h
to processor.h. They are different. Very different. And there's appearently
nothing we can do about it, so they're enclosed inside ifdefs.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
This patch moves the TASK_ALIGN constraints to common header.
The base of it is the same for x86_64 and i386. The only difference
is the presence of vSMP in x86_64. As it's not a worry in i386, we can
safely use the same code for both.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
What's left in processor_32.h and processor_64.h cannot be cleanly
integrated. However, it's just a couple of definitions. They are moved
to processor.h around ifdefs, and the original files are deleted. Note that
there's much less headers included in the final version.
Signed-off-by: Glauber de
x86_cpuinfo is one more to the family of not fundamentally different
structs. It's unified in processor.h, with very specific fields enclosed
around ifdefs.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/cpu/common.c |6 +-
include/asm-x86/processor.h|
Mark Lord wrote:
Improve the existing boot/load time warnings from sata_mv
for Highpoint RocketRAID 23xx cards, based on new knowledge
about where the BIOS likes to overwrite sectors with metadata.
Harmless to us, but very useful for end users.
Signed-off-by: Mark Lord [EMAIL PROTECTED]
---
This patch removes definitions and macros that are not used anymore
from processor_64.h
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/processor_64.h | 14 --
1 files changed, 0 insertions(+), 14 deletions(-)
Index:
This patch changes the bitwise operations in bitops.h to get
a void pointers as a parameter. Before this patch, a lot of warnings
can be seen. They're gone after it.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/bitops.h | 39
This patch moves the prefetch[w]? functions to processor.h
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/processor.h| 30 ++
include/asm-x86/processor_32.h | 25 -
include/asm-x86/processor_64.h |8
There's only one difference between the NOPs used in asm code for i386 and
x86_64:
i386 has a lot more variants. The code is moved to processor.h, and adjusted
accordingly.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
include/asm-x86/processor.h| 85
On Tue, 18 Dec 2007 10:38:13 +0900
KAMEZAWA Hiroyuki [EMAIL PROTECTED] wrote:
Is there a way to avoid it except turning off the swap?
Maybe...no.
Ah, sorry. If too much dirty page by ftp is trouble, tuning
/proc/sys/vm/dirty_ratio
/proc/sys/vm/dirty_writeback/centisecs
etc..
may work for
This patch moves definitions that are present in only one of the files
(between processor_32.h and processor_64.h), to processor.h. They're mostly
structures and function definitions.
Signed-off-by: Glauber de Oliveira Costa [EMAIL PROTECTED]
---
arch/x86/kernel/cpu/common.c |2 +-
Well, I guess it would be a smooth path if we rename the
drivers/i2c/chips/pca9539.c
since that's old style I2C driver, which means the driver name is not
so useful external
so the impact is actually minimum.
On Dec 18, 2007 4:29 AM, Jean Delvare [EMAIL PROTECTED] wrote:
Hi David,
On Mon, 17
Quoting Serge E. Hallyn ([EMAIL PROTECTED]):
Quoting Tetsuo Handa ([EMAIL PROTECTED]):
Hello.
Serge E. Hallyn wrote:
CAP_MKNOD will be removed from its capability
I think it is not enough because the root can rename/unlink device files
(mv /dev/sda1 /dev/tmp; mv /dev/sda2 /dev/sda1;
Avoid adding the same type of cap multiple times, otherwise we will see dead
loop.
Signed-off-by: Shaohua Li [EMAIL PROTECTED]
Index: linux/drivers/pci/pci.c
===
--- linux.orig/drivers/pci/pci.c2007-12-18 09:37:12.0
In 2.6.24, we turned on ACPI support in libata. This is needed in order
to support suspend/resume and BIOS passworded drives, but it inevitably
brought with it a host of new regressions -- which is what happens
anytime you blindly accept ATA commands the BIOS has decided to toss
your way. :)
A couple serious fixes (wireless, e100, sky2) and a bevy of minor ones.
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-linus
to receive the following updates:
MAINTAINERS|6 ++
save_state-cap_nr should be correctly set, otherwise we can't find the
saved cap at resume.
Signed-off-by: Shaohua Li [EMAIL PROTECTED]
Index: linux/drivers/pci/pci.c
===
--- linux.orig/drivers/pci/pci.c2007-12-18
pci_save/store_state has multiple bugs, which will cause cap can't be
saved/restored correctly. Below 3 patches fix them.
fix the typo in pci_save_pcix_state
Signed-off-by: Shaohua Li [EMAIL PROTECTED]
Index: linux/drivers/pci/pci.c
On Mon, 17 Dec 2007 14:56:44 PST, Andrew Morton said:
(Adding Al Viro to the list, he's listed as file systems and MAINTAINERS
doesn't list 'isofs' anyplace. Will Al or Andrew please vector to whoever
actually does that code?)
I try it again, and it reports it died at the same exact place,
Quoting Oren Laadan ([EMAIL PROTECTED]):
I hate to bring this again, but what if the admin in the container
mounts an external file system (eg. nfs, usb, loop mount from a file,
or via fuse), and that file system already has a device that we would
like to ban inside that container ?
Miklos'
Hello.
Serge E. Hallyn wrote:
But your requirements are to ensure that an application accessing a
device at a well-known location get what it expect.
Yes. That's the purpose of this filesystem.
So then the main quesiton is still the one I think Al had asked - what
keeps a rogue
Chao cac ban,
Ban nhan duoc email nay la do ban hoac mot ai do da dang ky dia chi
email cua ban tai trang web: www.nhaban.net.tf, www.nhaban.vnn.bz,
www.nhadep.us de nhan cac thong tin nha dat moi nhat cua chung toi.
Nay chung toi han hanh thong bao voi cac ban cac can ho cao cap chung
toi dang
On Mon, 17 Dec 2007, Joe Perches wrote:
Signed-off-by: Joe Perches [EMAIL PROTECTED]
drivers/scsi/qla4xxx/ql4_def.h|2 +-
drivers/scsi/qla4xxx/ql4_init.c |2 +-
Acked-by: David Somayajulu [EMAIL PROTECTED]
--
To unsubscribe from this list: send the line unsubscribe
On Mon, Dec 17, 2007 at 04:21:12PM -0800, Linus Torvalds wrote:
which also gets bonus points for being totally unreadable, and thus 100%
in the spirit of uuid's.
Heh. UUID's don't have to be readable; just universally unique. Code
on the other hand should be readable. :-)
If you want
On Mon, Dec 17, 2007 at 09:07:56PM -0500, [EMAIL PROTECTED] wrote:
On Mon, 17 Dec 2007 14:56:44 PST, Andrew Morton said:
(Adding Al Viro to the list, he's listed as file systems and MAINTAINERS
doesn't list 'isofs' anyplace. Will Al or Andrew please vector to whoever
actually does that
On Dec 17, 2007 8:16 PM, Larry Finger [EMAIL PROTECTED] wrote:
I hope that you have now convinced yourself that you should be using b43 and
not messing around
forcing b43legacy to use a device for which it was not intended.
I was convinced the moment I realized it worked exactly the same as
Another rework of the i2c for powerpc device tree patch. This version
implements standard alias naming only on the powerpc platform and only for the
device tree names. The old naming mechanism of i2c_client.name,driver_name is
left in place and not changed for non-powerpc platforms. This patch
Temporarily copy the mpc-i2c driver to continue support for the ppc
architecture until it is removed in mid-2008. This file should be deleted as
part of ppc's final removal.
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL
Convert MPC i2c driver from being a platform_driver to an open firmware
version. Error returns were improved. Routine names were changed from fsl_ to
mpc_ to make them match the file name.
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon
This patch allows new style i2c chip drivers to have alias names using
the official kernel aliasing system and MODULE_DEVICE_TABLE(). I've
tested it on PowerPC and x86. This change is required for PowerPC
device tree support.
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl
Return errors that were being ignored in the mpc-i2c driver
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
drivers/i2c/busses/i2c-mpc.c | 30 +-
1 files changed, 17
Follow on to: Series to add device tree naming to i2c
Teach module-init-tools about the i2c subsystem.
diff --git a/depmod.c b/depmod.c
index 0281c79..209eb0c 100644
--- a/depmod.c
+++ b/depmod.c
@@ -793,6 +793,7 @@ static struct depfile depfiles[] = {
{ modules.inputmap,
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
Makefile |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Makefile b/Makefile
index c1825aa..15ada3f 100644
--- a/Makefile
+++ b/Makefile
@@ -35,6 +35,9 @@ MAKEFLAGS += -rR
Ignore this patch, I forgot to remove it before mailing the series.
On 12/17/07, Jon Smirl [EMAIL PROTECTED] wrote:
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
Makefile |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git
On Mon, Dec 17, 2007 at 11:24:57AM -0800, Randy Dunlap wrote:
On Sun, 16 Dec 2007 21:55:20 + Mel Gorman wrote:
Just using cp to read the file is enough to cause problems but I
included
a very basic program below that produces the BUG_ON checks. Is this a
known
issue or
From: Divy Le Ray [EMAIL PROTECTED]
Add parity initialization for T3C adapters.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
---
drivers/net/cxgb3/adapter.h |1
drivers/net/cxgb3/cxgb3_main.c| 82
drivers/net/cxgb3/cxgb3_offload.c | 15 ++
From: Divy Le Ray [EMAIL PROTECTED]
set_pci_drvdata() stores a pointer to the adapter,
not the net device.
Add missing softirq blocking in t3_mgmt_tx.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
---
drivers/net/cxgb3/cxgb3_main.c | 14 --
drivers/net/cxgb3/sge.c|7
Hello,
[EMAIL PROTECTED] wrote:
--- sata_nv.c.orig2007-12-17 21:08:12.0 +0530
+++ sata_nv.c 2007-12-17 21:08:25.0 +0530
@@ -2407,6 +2407,12 @@
type = GENERIC;
}
+ /* set 64bit dma masks, may fail */
+ if (type == ADMA) {
+
On Tue, 18 Dec 2007 10:37:32 +0800 Dave Young [EMAIL PROTECTED] wrote:
On Mon, Dec 17, 2007 at 09:07:56PM -0500, [EMAIL PROTECTED] wrote:
On Mon, 17 Dec 2007 14:56:44 PST, Andrew Morton said:
(Adding Al Viro to the list, he's listed as file systems and MAINTAINERS
doesn't list 'isofs'
Quoting Tetsuo Handa ([EMAIL PROTECTED]):
Hello.
Serge E. Hallyn wrote:
But your requirements are to ensure that an application accessing a
device at a well-known location get what it expect.
Yes. That's the purpose of this filesystem.
So then the main quesiton is still the one I
Serge E. Hallyn wrote:
Quoting Oren Laadan ([EMAIL PROTECTED]):
I hate to bring this again, but what if the admin in the container
mounts an external file system (eg. nfs, usb, loop mount from a file,
or via fuse), and that file system already has a device that we would
like to ban inside
Hi Steven,
I posted a suspend-to-ram fix to sched-devel earlier today:
http://lkml.org/lkml/2007/12/17/445
This fix should also be applied to -rt as I introduced the same regression
there. Here is a version of the fix for 23-rt13. I can submit a version for
24-rc5-rt1 at your request.
From: Chris Newport [EMAIL PROTECTED]
Date: Tue, 18 Dec 2007 02:58:29 + (GMT)
On Tue, 18 Dec 2007, Stefan Richter wrote:
It's a 100% reproducible oops on Sparc (with FireWire controller) for
2.6.23 and 2.6.24 kernels, but not 2.6.22. The reporter confirmed that
the bug also happens
Divy Le Ray wrote:
From: Divy Le Ray [EMAIL PROTECTED]
Add parity initialization for T3C adapters.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
applied 1-2 to #upstream
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
On Mon, Dec 17, 2007 at 07:52:53PM -0500, Andy Lutomirski wrote:
It runs on a freshly booted machine (no
DSA involved, so we're not automatically hosed), so an attacker knows the
initial pool state.
Not just a freshly booted system. The system has to be a freshly
booted, AND freshly
On Tue, 18 Dec 2007, Stefan Richter wrote:
It's a 100% reproducible oops on Sparc (with FireWire controller) for
2.6.23 and 2.6.24 kernels, but not 2.6.22. The reporter confirmed that
the bug also happens
How do you achieve a sparc system with firewire ?
AFAIK there is no SBUS firewire card.
Signed-off-by: Harvey Harrison [EMAIL PROTECTED]
---
Replacement for the last patch in the kprobes series I just sent.
arch/x86/kernel/kprobes.c | 45 +
1 files changed, 21 insertions(+), 24 deletions(-)
diff --git a/arch/x86/kernel/kprobes.c
Theodore Tso wrote:
On Mon, Dec 17, 2007 at 07:52:53PM -0500, Andy Lutomirski wrote:
It runs on a freshly booted machine (no
DSA involved, so we're not automatically hosed), so an attacker knows the
initial pool state.
Not just a freshly booted system. The system has to be a
Chris Friesen [EMAIL PROTECTED] wrote:
However, if I specifically try to print out one of the missing entries,
it shows up:
[EMAIL PROTECTED]:/root /tmp/ip neigh show 192.168.24.81
192.168.24.81 dev bond2 lladdr 00:01:af:14:e9:8a REACHABLE
What about
ip -4 neigh show
Thanks,
--
Gregory Haskins wrote:
Hi Steven,
I posted a suspend-to-ram fix to sched-devel earlier today:
http://lkml.org/lkml/2007/12/17/445
This fix should also be applied to -rt as I introduced the same regression
there. Here is a version of the fix for 23-rt13. I can submit a version for
This patch modifies the ds1307, ds1374, and rs5c372 i2c drivers to support
device tree names using the new i2c mod alias support
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
arch/powerpc/sysdev/fsl_soc.c |
Convert pfc8563 i2c driver from old style to new style. The
driver is also modified to support device tree names via the
i2c mod alias mechanism.
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
Signed-off-by: Jon Smirl [EMAIL PROTECTED]
---
Hello.
Serge E. Hallyn wrote:
Nope, try
touch /root/hda1
ls -l /root/hda1
mount --bind /dev/hda1 /root/hda1
ls -l /root/hda1
[EMAIL PROTECTED] ~]# touch /root/hda1
[EMAIL PROTECTED] ~]# ls -l /root/hda1
-rw-r--r-- 1 root root 0 Dec 18 12:04 /root/hda1
[EMAIL PROTECTED] ~]# mount
On Tue, Dec 18, 2007 at 01:43:28PM +1030, David Newall wrote:
On a server, keyboard and mouse are rarely used. As you've described it,
that leaves only the disk, and during the boot process, disk accesses and
timing are somewhat predictable. Whether this is sufficient to break the
RNG is
Please apply the attached patch and try to use cdrom w/o specifying any
parameter and report kernel log.
Thanks.
--
tejun
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 4753a18..acaa8b8 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -4537,6
Theodore Tso wrote:
On Tue, Dec 18, 2007 at 01:43:28PM +1030, David Newall wrote:
On a server, keyboard and mouse are rarely used. As you've described it,
that leaves only the disk, and during the boot process, disk accesses and
timing are somewhat predictable. Whether this is sufficient
Adam isn't a maintainer anymore.
His old email address bounces.
Update to new email address.
On Mon, Dec 17, 2007 at 01:03:48PM -0800, Joe Perches wrote:
You seem to have an old email address in the
linux-kernel MAINTAINERS file.
Should it be deleted or changed?
On Mon, 2007-12-17 at 19:27
On Tue, Dec 18, 2007 at 02:39:00PM +1030, David Newall wrote:
Thus, the entropy saved at shutdown can be known at boot-time. (You can
examine the saved entropy on disk.)
If you can examine the saved entropy on disk, you can also introduce a
trojan horse kernel that logs all keystrokes and
On Mon, 17 Dec 2007 20:12:06 -0800 Joe Perches [EMAIL PROTECTED] wrote:
Adam isn't a maintainer anymore.
His old email address bounces.
Update to new email address.
On Mon, Dec 17, 2007 at 01:03:48PM -0800, Joe Perches wrote:
You seem to have an old email address in the
linux-kernel
Andi Kleen [EMAIL PROTECTED] writes:
On Mon, Dec 17, 2007 at 08:57:50AM +1100, Paul Mackerras wrote:
Greg KH writes:
Ok, sorry, it wasn't blindingly obvious that this was for pci sysfs
devices that are mmaped, that makes a bit more sense.
But I'd like to see what ioctl is wanted here
On Saturday 01 December 2007 07:02:43 Adam Jackson wrote:
These types define the size of data read from /dev/apm_bios. They
should not be hidden behind #ifdef __KERNEL__.
Acked-by: Rusty Russell [EMAIL PROTECTED]
My mistake, sorry.
Rusty.
--
To unsubscribe from this list: send the line
H. Peter Anvin [EMAIL PROTECTED] writes:
This is directly analogous to how we treat identity information in IDE, or PCI
configuration space -- some fields are pre-digested, but the entire raw
information is also available.
Add to that a totally unchanged value can just be easier to get
Andi Kleen [EMAIL PROTECTED] writes:
I do know we need to use the low 4 pat mappings to avoid most of the PAT
errata issues.
They don't really matter. These are all very old systems who have run
fine for many years without PAT. It is no problem to let them
continue to do so and just
On Mon, 2007-12-17 at 20:28 -0800, Andrew Morton wrote:
Please: just replace all instances with plain old Adam Fritzler and then
ensure that the lookup key Adam Fritzler has an accurate (and
non-duplicated anywhere else!) entry in MAINTAINERS or CREDITS or whatever.
Sure. See new patch below
I hit a bug in 2.6.24-rc looks to be in 2.6.23 also so not sure how
long it's been there
with an xfs filesystem pbuilder has an issue using device files it
makes for chroot
the mknod command looks to work fine the file is created
however when attempting to use one of the created files you see
Venki Pallipadi [EMAIL PROTECTED] writes:
Checking the manual for this. You are right, we had missed some steps here.
Actually, manual says on MP, PAT MSR on all CPUs must be consistent (even when
they are not really using it in their page tables.
So, this will change the init and shutdown
On Friday 14 December 2007 18:51:06 Ananth N Mavinakayanahalli wrote:
On Thu, Dec 13, 2007 at 11:09:16PM -0800, Andrew Morton wrote:
regular_kernel_text_address()? Dunno.
Sounds better :-)
The better answer was to invert it and use discarded_kernel_text_address(),
which is what you actually
Eric W. Biederman wrote:
_00FD_FC00_h - _00FD_FDFF_h On a hypertransport based
system should work. There is a 32MB window for it.
It doesn't. The termination on MMIO and IOIO transaction is different,
and poking this memory window with an MMIO transaction will lock the
Has anyone *proven* that using uninitialized data this way is safe?
You can probably find dozens of things in the Linux kernel that have not
been proven to be safe. That means nothing.
As
a *user* of this stuff, I'm *very* hesitant to trust Linux's RNG when I
hear things like this. (Hint:
On Tuesday 18 December 2007 09:52:26 Glauber de Oliveira Costa wrote:
+static inline int desc_empty(const void *ptr)
+{
+ const u32 *desc = ptr;
+ return !(desc[0] | desc[1]);
+}
Erk. This really needs to be a union, not a void *. I guess we can clean it
later.
Rusty.
--
To
Intel IOMMU (a.k.a VT-d) is under rapid deployment on desktop
and mobile platforms. As platform provides multiple dma remap
engines for devices like those lives on south bridge (net, sound,
etc.), and we also have one engine specific to graphics device.
If this engine is functioning, the access
[PATCH] [intel_iommu] explicit export current graphics dmar status
To make it possbile to tell other modules about curent
graphics dmar engine status, that could decide if graphics
driver should remap physical address to dma address.
Also this one trys to make dmar_disabled really present
[PATCH] [AGP] Add generic support for graphics dma remapping
New driver hooks for support graphics memory dma remapping
are introduced in this patch. It makes generic code can
tell if current device needs dma remapping, then call driver
provided interfaces for mapping and unmapping. Change has
On Tuesday 18 December 2007 09:52:36 Glauber de Oliveira Costa wrote:
This patch changes the bitwise operations in bitops.h to get
a void pointers as a parameter. Before this patch, a lot of warnings
can be seen. They're gone after it.
No, this is a backwards step! These warnings are
[PATCH] [AGP] intel_agp: add support for graphics dma remapping on G33
When graphics dma remapping engine is active, we must fill
gart table with dma address from dmar engine, as now graphics
device access to graphics memory must go through dma remapping
table to get real physical address.
Add
diff --git a/kernel/Makefile b/kernel/Makefile
index dfa9695..749825a 100644
--- a/kernel/Makefile
+++ b/kernel/Makefile
@@ -80,3 +80,11 @@ quiet_cmd_ikconfiggz = IKCFG $@
targets += config_data.h
$(obj)/config_data.h: $(obj)/config_data.gz FORCE
$(call if_changed,ikconfiggz)
+
I'll have a TLS cleanup patch soon that makes the (only) use of desc_empty
pass a struct user_desc pointer.
Thanks,
Roland
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Greetings!
System details:
Board: DTSP-ARM926Ej-S(new board)
Cross-toolchain: ELDK4.1
Linux kernel: 2.6.18
u-boot: 1.1.6
I have been able to successfully run u-boot and linux kernel with root file
system but when kernel is start the following error message
come..kobject_add failed
Rusty Russell wrote:
On Tuesday 18 December 2007 09:52:36 Glauber de Oliveira Costa wrote:
This patch changes the bitwise operations in bitops.h to get
a void pointers as a parameter. Before this patch, a lot of warnings
can be seen. They're gone after it.
No, this is a backwards step! These
what the heck, applied
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Mon, Dec 17, 2007 at 08:11:05AM +0100, Borislav Petkov wrote:
A slightly microoptimized version 1.1:
---
From: Borislav Petkov [EMAIL PROTECTED]
Check the patch level of the single hunks in a patch file, however only when
checkpatch.pl is called from within the kernel tree.
Signed-off-by:
When the conversion factor between jiffies and milli- or microseconds
is not a single multiply or divide, as for the case of HZ == 300, we
currently do a multiply followed by a divide. The intervening
result, however, is subject to overflows, especially since the
fraction is not simplified (for
I'll have a TLS cleanup patch soon that makes the (only) use of desc_empty
pass a struct user_desc pointer.
Oops, I meant struct desc_struct of course. But in fact the only use is
already using the right struct pointer, so we can clean up desc_empty now
(in x86/mm).
Thanks,
Roland
--
To
This cleans up the x86 TLS code to use desc_struct in place of hand-coded
bit-twiddling, and cleans up a few of the inlines for the type too.
Signed-off-by: Roland McGrath [EMAIL PROTECTED]
---
arch/x86/kernel/tls.c | 89
include/asm-x86/desc.h
On Tue, Dec 18, 2007 at 10:05:45AM +0900, KAMEZAWA Hiroyuki wrote:
On Thu, 13 Dec 2007 15:03:07 +
+ if (mm != active_mm) {
+ /* Restore region IDs for mm */
+ if (mm active_mm) {
+ activate_context(mm);
+ }
On Dec 17, 2007 9:29 AM, Eric Dumazet [EMAIL PROTECTED] wrote:
Parag, could you please try this patch ?
[NET] ARP : Convert neigh garbage collection from softirq to workqueue
I will - a little later.
Thanks
Parag
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
There is no need to set the decryption key every time eCryptfs decrypts
an extent.
Trevor
0001-eCryptfs-Load-each-file-decryption-key-only-once.patch
Description: application/mbox
On Tue, 18 Dec 2007 01:00:15 -0500
Kyle McMartin [EMAIL PROTECTED] wrote:
On Tue, Dec 18, 2007 at 10:05:45AM +0900, KAMEZAWA Hiroyuki wrote:
On Thu, 13 Dec 2007 15:03:07 +
+ if (mm != active_mm) {
+ /* Restore region IDs for mm */
+ if (mm
Only one byte of cipher_code is being written to the file header so it
should be of type u8.
Trevor
0001-Change-the-type-of-cipher_code-from-u16-to-u8.txt
Description: application/mbox
Rusty Russell wrote:
On Friday 14 December 2007 18:51:06 Ananth N Mavinakayanahalli wrote:
On Thu, Dec 13, 2007 at 11:09:16PM -0800, Andrew Morton wrote:
regular_kernel_text_address()? Dunno.
Sounds better :-)
The better answer was to invert it and use discarded_kernel_text_address(),
From: [EMAIL PROTECTED] (Eric W. Biederman)
Date: Mon, 17 Dec 2007 15:44:08 -0700
Signed-off-by: Eric W. Biederman [EMAIL PROTECTED]
Applied, thanks Eric.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
Please pull from the for-linus branch:
git pull git://oss.sgi.com:8090/xfs/xfs-2.6.git for-linus
This will update the following files:
fs/xfs/linux-2.6/xfs_file.c |4 ++--
fs/xfs/xfs_dir2_block.c |6 ++
fs/xfs/xfs_dir2_leaf.c |2 +-
fs/xfs/xfs_dir2_sf.c|
On Tuesday 18 December 2007 09:36, David Howells wrote:
Nick Piggin [EMAIL PROTECTED] wrote:
I'd much prefer if you would handle this in the filesystem, and have it
set PG_private whenever fscache needs to receive a callback, and DTRT
depending on whether PG_fscache etc. is set or not.
Theodore Tso wrote:
On Mon, Dec 17, 2007 at 04:21:12PM -0800, Linus Torvalds wrote:
which also gets bonus points for being totally unreadable, and thus 100%
in the spirit of uuid's.
Heh. UUID's don't have to be readable; just universally unique. Code
on the other hand should be readable.
On Tuesday 18 December 2007 09:42, David Howells wrote:
Nick Piggin [EMAIL PROTECTED] wrote:
This is pretty nasty.
Why? If the fs doesn't set PG_private or PG_fscache on any pages before
calling read_cache_pages(), there's no difference.
It is conceptually wrong.
Furthermore, the
501 - 600 of 1228 matches
Mail list logo
