On Mon, 2007-07-30 at 22:40 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > This patch adds document for EFI x86_64 support. The boot parameters
> > added are documented in Documentation/i386/zero-page.txt. The setup
> > and operation guide of EFI based system is
Hi,
A year ago, commit abf75a5033d4da7b8a7e92321d74021d1fcfb502 was included
to fix a security vulnerability that is related to prctl privilege
escalation, and suid_dumpable (CVE-2006-2451). But the commit was just a
quick fix to prevent users from calling prctl(PR_SET_DUMPABLE, 2).
This patch se
This patch removes documentation that is related to suidsafe core dump
mode.
Signed-off-by: Eugene Teo <[EMAIL PROTECTED]>
---
Documentation/sysctl/fs.txt |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/Documentation/sysctl/fs.txt b/Documentation/sysctl/fs.txt
index
This patch removes suidsafe core dump mode related dead code.
Signed-off-by: Eugene Teo <[EMAIL PROTECTED]>
---
fs/exec.c | 16 +---
include/linux/binfmts.h |3 ---
2 files changed, 1 insertions(+), 18 deletions(-)
diff --git a/fs/exec.c b/fs/exec.c
index 7bdea79.
Hidehiro-san re-implemented suid_dumpable using a pair of bit flags. But
since we no longer permitting users to call prctl(PR_SET_DUMPABLE, 2),
there is no need to waste a bit of mm_struct.flags for something that will
never be used.
Signed-off-by: Eugene Teo <[EMAIL PROTECTED]>
---
fs/exec.c
I want implement some sort of snapshot dev.
In order to do this i've replaced original q->make_request_fn
with specific one which cowed all write requests.
My first attempt looks like this:
static int mysnap_make_request(request_queue_t *q, struct bio *bio)
{
struct bio cl_bio;
make
KVM: x86 emulator: disable writeback for debug register instructions
These are handled internally by the instruction.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
diff --git a/drivers/kvm/x86_emulate.c b/drivers/kvm/x86_emulate.c
index 1a90ba0..2136da5 100644
--- a/drivers/k
On Tue, Jul 31 2007, Dmitry Monakhov wrote:
> I want implement some sort of snapshot dev.
> In order to do this i've replaced original q->make_request_fn
> with specific one which cowed all write requests.
> My first attempt looks like this:
> static int mysnap_make_request(request_queue_t *q, stru
On Mon, 2007-07-30 at 22:37 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > Changelog between v2 and v3:
> >
> > 1. The EFI callwrapper is re-implemented in assembler.
> >
> > ---
> >
> > This patch adds basic support for EFI x86_64 system. The main file of
> > th
On Mon, 2007-07-30 at 16:57 -0700, Andrew Morton wrote:
> On Sun, 29 Jul 2007 20:56:46 -0400
> Ulrich Drepper <[EMAIL PROTECTED]> wrote:
>
> > Is there a reason why the "online" file in the subdirectories for the CPUs
> > in /sys/devices/system isn't world-readable?
>
> No sane one which I can th
On 09:29 Втр 31 Июл , Jens Axboe wrote:
> On Tue, Jul 31 2007, Dmitry Monakhov wrote:
> > I want implement some sort of snapshot dev.
> > In order to do this i've replaced original q->make_request_fn
> > with specific one which cowed all write requests.
> > My first attempt looks like this:
> >
On Tue, Jul 31 2007, Dmitry Monakhov wrote:
> On 09:29 ?? 31 ?? , Jens Axboe wrote:
> > On Tue, Jul 31 2007, Dmitry Monakhov wrote:
> > > I want implement some sort of snapshot dev.
> > > In order to do this i've replaced original q->make_request_fn
> > > with specific one which cowed a
On Mon, Jul 30, Theodore Tso wrote:
> On Mon, Jul 30, 2007 at 06:13:35PM +0200, Jan Blunck wrote:
> > Introduce white-out support to ext2.
> >
> > Known Bugs:
> > - Needs a reserved inode number for white-outs
>
> You picked different reserved inodes for the ext2 and ext3
> filesystems. That's
On 7/24/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Tue, 24 Jul 2007 16:12:56 -0400 Robin Getz wrote:
> > On Tue 24 Jul 2007 14:12, Andrew Morton pondered:
> > > Oh well, it sounds like we need the super-duper fast version. Keep it
> > > as simple as possible, please.
> >
> > What about:
> >
Avi Kivity wrote:
KVM: x86 emulator: disable writeback for debug register instructions
These are handled internally by the instruction.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
Sorry, junk that. Fingers (or brain) slipped. Better one coming up.
--
error compil
More fallout from the writeback fixes: debug register transfer instructions
do their own writeback and thus need to disable the general writeback
mechanism. This fixes oopses and some guest failures on AMD machines (the
Intel variant decodes the instruction in hardware and thus does not need
emula
On Tue, 2007-07-31 at 03:47 -0400, Mike Frysinger wrote:
> On 7/24/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> > On Tue, 24 Jul 2007 16:12:56 -0400 Robin Getz wrote:
> > > On Tue 24 Jul 2007 14:12, Andrew Morton pondered:
> > > > Oh well, it sounds like we need the super-duper fast version. Kee
Hi David,
I have formulated a patch that prevents the update_mmu_cache from doing
enything if there is no context available. This apears to have no
immediate, undesirable side effects.
This worked better than the alternative of setting up a context to work with.
Can you for see any issues in
Hi!
> >Can you generate small testcase that demonstrates the problem?
> >
> >> Then what would be the correct way to handle resume process. The other
> >> way of course is to make all the applications check the errno in case of
> >> failure. But that seems more more problematic then system call ch
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> This patch uses memory policies to attempt to improve this. It
> requires that we ask the scheduler to suggest the child's new CPU
> earlier in the fork, but that is not a fundamental difference.
no fundamental objections, but i think we could simply
On Tue, 31 Jul 2007 15:03:40 +0800
Eugene Teo <[EMAIL PROTECTED]> wrote:
> This patch removes documentation that is related to suidsafe core dump
> mode.
>
> Signed-off-by: Eugene Teo <[EMAIL PROTECTED]>
NAK - this feature is actively used and can be set by the sysctl
interface. The PRCTL fixup
On Tue, 31 Jul 2007 15:04:58 +0800
Eugene Teo <[EMAIL PROTECTED]> wrote:
> This patch removes suidsafe core dump mode related dead code.
>
> Signed-off-by: Eugene Teo <[EMAIL PROTECTED]>
NAK: This feature is used by end users and people debugging complex
system problems.
-
To unsubscribe from th
On Tue, Jul 31, 2007 at 03:31:22AM +0530, Satyam Sharma wrote:
> Hi Rodolfo,
Hi :)
> Yup, this would avoid races, but then we will lose events. Why is that
> acceptable, when better alternative (above) exists?
Because is better lossign events then recording them delayed. In the
past we (LinuxPPS
On 28-07-2007 20:42, Gabriel C wrote:
> Andrew Morton wrote:
>> On Sat, 28 Jul 2007 17:44:45 +0200 Gabriel C <[EMAIL PROTECTED]> wrote:
>>
>>> Hi,
>>>
>>> I got this compile error with a randconfig (
>>> http://194.231.229.228/MM/randconfig-auto-82.broken.netpoll.c ).
>>>
>>> ...
>>>
>>> net/core/
On 7/31/07, Bryan Wu <[EMAIL PROTECTED]> wrote:
> why use attachment? You can just paste your patch in the email.
gmail eats inline text and my normal e-mail account is offline atm
-mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
I have several systems here where Linux tells me:
Local APIC disabled by BIOS -- you can enable it with "lapic"
As far as I understand, the Local APIC was integrated directly to the
CPU 12-15 years ago. Why would a BIOS implementor choose to disable it?
(And what does it mean to "disable" the
On Tue, 31 Jul 2007 15:05:38 +0800
Eugene Teo <[EMAIL PROTECTED]> wrote:
> Hidehiro-san re-implemented suid_dumpable using a pair of bit flags. But
> since we no longer permitting users to call prctl(PR_SET_DUMPABLE, 2),
> there is no need to waste a bit of mm_struct.flags for something that will
On Mon, 2007-07-30 at 22:30 -0600, Eric W. Biederman wrote:
> > This patch adds runtime service support for EFI x86_64 system.
> >
> > The EFI support for emergency_restart and RTC clock is added. The EFI
> > based implementation and legacy BIOS or CMOS based implementation are
> > put in separate
When CONFIG_USB_UHCI_HCD, CONFIG_USB_OHCI_HCD or CONFIG_USB_EHCI_HCD is
not configured we don't need to call the quirk_usb_handoff_ function
in driver/usb/host/pci_quiks.c.
I think the kernel shouldn't take the control over the usb controller
when we don't have the driver for it,
so with this
On Jul 31, 2007 09:44 +0200, Jan Blunck wrote:
> Ok, this is pretty similar to the way I implemented this for tmpfs. The
> problem is that the union mount code is explicitly checking if the filesystem
> is supporting whiteout. I used to use a new filesystem flag (FS_WHITEOUT) for
> this but though
* kriko <[EMAIL PROTECTED]> wrote:
> I'm trying to get kernel 2.6.22-ck and 2.6.23-rc1 work to test the new
> cfs scheduler, but I get broken system. Networking is totally broken
> (cannot find module for my marvell yukon gigabit ethernet in kconfig),
> firewall / routing doesn't work (a bunch
David Mosberger-Tang wrote:
This seems crazy to me. Flushing should occur according to the
*architecture*, not model-by-model. Even if we happen to get "lucky"
on pre-Montecito CPUs, that doesn't justify such ugly hacks. Or you
really want to debug this *again* come next CPU?
--david
O.K.
On Mon, 30 Jul 2007, Chr wrote:
> Ok, found it " hid_blacklist is alphabetically sorted blacklist by quirk
> type. " But is there a Order for the bitfields? e.g
> shouldn't: hid-quriks.c (line 439, 440)
> { USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_FOUNTAIN_ANSI,
> HID_QUIRK_POWERBOOK_HAS_FN | HI
* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> Hi Ingo, I'm forwading this report from a Planet CCRMA user, this is
> happening to him with 2.6.21.6-rt21...
thanks!
> BUG: sleeping function called from invalid context IRQ-219(2243) at
> kernel/rtmutex.c:613
> in_atomic():0 [], i
> After a successful mount, the NFS mount command tucks some options into
> /etc/mtab that reflect which mountd was used for the mount, and what
> protocol version and port was used for the mount request. Those options
> are not passed to the kernel, and do not appear in /proc/mounts today.
>
> This patch contains implementation of show_options method for UFS,
> it depend on add-in-sunos-41x-compatible-mode-for-ufs.patch and
> add-in-sunos-41x-compatible-mode-for-ufs-fix.patch.
>
>
> Signed-off-by: Evgeniy Dushistov <[EMAIL PROTECTED]>
Thanks. I'll quite these up and submit them in
On Mon, 2007-07-30 at 22:16 -0600, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
> > - The variable efi_enabled is used throughout across architecutres if
> > CONFIG_EFI option is enabled. The i386 code also uses this variable.
> > This is something that can be revisited wi
* Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-07-31 at 01:46 +0200, Kasper Sandberg wrote:
>
> > could perhaps be filesystem related, i have my maildir(extremely
> > large) on reiserfs, and /home on xfs. what my mail client will do is
> > download mail, spamasassin it(loading data
On Sun, 29 Jul 2007 23:41:05 +0200 Matthias Kaehlcke <[EMAIL PROTECTED]> wrote:
> --- a/include/linux/isdn.h
> +++ b/include/linux/isdn.h
> @@ -15,6 +15,7 @@
> #define __ISDN_H__
>
> #include
> +#include
Breaks `make headers_check'.
That was covered in sections 2 and 20 of Documentation/Su
From: Mark Fortescue <[EMAIL PROTECTED]>
Date: Tue, 31 Jul 2007 08:55:20 +0100 (BST)
> I have formulated a patch that prevents the update_mmu_cache from doing
> enything if there is no context available. This apears to have no
> immediate, undesirable side effects.
>
> This worked better than t
> code runs under the BKL, and the only other major kernel infrastructure
> that has BKL dependencies is the TTY code. Kasper, as a debugging
And half the ioctls some of which trigger long code sections.
For the tty layer I'm waiting for the revoke code to get finished up and
move from -mm into
On Tuesday, 31 July 2007 06:59, Len Brown wrote:
> On Sunday 29 July 2007 17:27, Rafael J. Wysocki wrote:
> > Still, there are many other files in which CONFIG_PM can be replaced
> > with CONFIG_PM_SLEEP or even with CONFIG_SUSPEND, but they can be updated in
> > the future.
>
> There is #ifdef CO
On Tue, Jul 31, Andreas Dilger wrote:
> On Jul 31, 2007 09:44 +0200, Jan Blunck wrote:
> > Ok, this is pretty similar to the way I implemented this for tmpfs. The
> > problem is that the union mount code is explicitly checking if the
> > filesystem
> > is supporting whiteout. I used to use a new
Hi!
> Index: kexec-tools-1.101/kexec/arch/i386/crashdump-x86.c
> ===
> --- kexec-tools-1.101.orig/kexec/arch/i386/crashdump-x86.c2007-07-08
> 23:00:25.0 +0800
> +++ kexec-tools-1.101/kexec/arch/i386/crashdump-x86.c 2007-
* Alan Cox <[EMAIL PROTECTED]> wrote:
> > code runs under the BKL, and the only other major kernel
> > infrastructure that has BKL dependencies is the TTY code. Kasper, as
> > a debugging
>
> And half the ioctls some of which trigger long code sections.
the tty layer has relatively short BKL
Am Dienstag 31 Juli 2007 schrieb Rafael J. Wysocki:
> Well, the people on linux-pm seem to agree that the .suspend() and .resume()
> callbacks are not suitable for runtime power management, so having them
> built without SUSPEND or HIBERNATION wouldn't be very useful. ;-)
These are what USB runti
On Tuesday 31 July 2007 07:41, Nick Piggin wrote:
> I haven't given this idea testing yet, but I just wanted to get some
> opinions on it first. NUMA placement still isn't ideal (eg. tasks with
> a memory policy will not do any placement, and process migrations of
> course will leave the memory be
Hi,
Attached patch deinlines and moves big functions from .h to .c files
in drivers/scsi/aic7xxx/*. I also had to add prototypes for ahc_lookup_scb
and ahd_lookup_scb to .h files.
No other code changes made.
Compile-tested on i386 and x86-64.
Total .text size reduction: ~60k in 64 bits, ~90k in
Ingo Molnar wrote:
For the tty layer I'm waiting for the revoke code to get finished up
and move from -mm into Linus tree. At that point the real evil
lock_kernel related stuff in the tty layer can switch to using the
revoke code for hangup paths and then other bits can be tackled.
oh,
Hi,
On Tue, 2007-07-31 at 13:46 +0800, Denis Cheng wrote:
> these struct *_operations are all method tables, thus should be const.
>
> Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
> ---
> fs/gfs2/eaops.c|8
> fs/gfs2/eaops.h|4 ++--
> fs/gfs2/glock.c|
[ mail re-sent with lkml Cc:-ed. _Please_ Cc: all patches to lkml too!
Unless you want -rt to suffer the fate of -ck, keep upstream involved
all the time. The recent /proc/interrupts-all discussion with upstream
folks showed the clear benefits of that approach. ]
* Gregory Haskins <[EMAI
On Tuesday, 31 July 2007 08:38, Pavel Machek wrote:
> Hi!
>
> > Without this change, it is possible to build CONFIG_HIBERNATE
> > on all !SMP architectures, but not necessarily their SMP versions.
>
> Did you want to say "CONFIG_SUSPEND"?
>
> > I don't know for sure if the architecture list unde
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> * Gregory Haskins <[EMAIL PROTECTED]> wrote:
>
> > This code allows FUNCTION_CALL IPIs to become preemptible by
> > executing them in kthread context instead of interrupt context.
> > They are referred to as "Virtual Function Call IPIs" (VFCIPI)
>
On Tue, 2007-07-31 at 11:10 +0200, Pavel Machek wrote:
> > Index: kexec-tools-1.101/kexec/arch/i386/crashdump-x86.c
> > ===
> > --- kexec-tools-1.101.orig/kexec/arch/i386/crashdump-x86.c 2007-07-08
> > 23:00:25.0 +0800
> > ++
Hello,
after my problems with my DVD drive, I've unplugged this device and
jumpered my burning device as master, to start my linux setup from there.
Now I don't longer get those silly DVD errors, but now I get something,
which is much more worrying for me:
http://pastebin.com/f6fc7552f
Aft
Hi!
>
> During VM oom condition, kill all threads in process group.
>
> We have had complaints where a threaded application is left in a bad
> state after one of it's threads is killed when we hit a VM: out_of_memory
> condition.
> Killing just one of the process threads can leave the applicatio
On 7/31/07, Steven Whitehouse <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Tue, 2007-07-31 at 13:46 +0800, Denis Cheng wrote:
> > these struct *_operations are all method tables, thus should be const.
> >
> > Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
> > ---
> > fs/gfs2/eaops.c|8 -
On my Acer Ferrari 1000 the tg3 ethernet no longer is available after a
suspend to ram with the latet 2.6.23-rc1-git9. The tg3 works fine with s2ram
in 2.6.22.1. The tell tail signs that is dead is this message from the
kernel log:
[6.754133] tg3: eth0: No firmware running.
[6.816140]
> > oh, wonderful! Alan, you are a true wizard :-) The tty layer is one of
> > the very few pieces of kernel code that scares the hell out of me :-)
I'm not too fond of the way it does some stuff either especially the open
v close v hangup paths but that is partly the fault of POSIX 8)
> Maybe i
Hello everybody,
here are some small documentation fixes - mostly typing errors.
Please take a look at the last chunk - I think that klibc.bkbits.net
is no longer the current version, but I'm not sure whether the
other link is better.
Whom should I CC for other documentation updates? Is the m
> After mounting my four LVs, formatted with XFS, here, I'm starting to
> delete all files on those LVs to be able to do a fresh linux install.
> While deleting, I get *many* DMA errors and "BAD CRC" messages.
Bad CRC indicates a data transfer problem between the drive and the
controller. The CR
* Kenneth Prugh <[EMAIL PROTECTED]> wrote:
> Alright, Just got done with some testing of UT2004 between 2.6.23-rc1
> CFS and 2.6.22-ck1 SD. This series of tests was run by spawning in a
> map while not moving at all and always facing the same direction,
> while slowing increasing the number of
Hi!
> This patch implement the functionality of jumping from kexeced kernel
> to original kernel.
>
> A new reboot command named LINUX_REBOOT_CMD_KJUMP is defined to
> trigger the jumping to (executing) the new kernel or jumping back to
> the original kernel.
Could we get two reboot commands? Ex
On Tuesday, 31 July 2007 11:16, Oliver Neukum wrote:
> Am Dienstag 31 Juli 2007 schrieb Rafael J. Wysocki:
>
> > Well, the people on linux-pm seem to agree that the .suspend() and .resume()
> > callbacks are not suitable for runtime power management, so having them
> > built without SUSPEND or HIB
On Tue, Jul 31, 2007 at 09:15:17AM +0800, Carlo Florendo wrote:
> And I think you are digressing from the main issue, which is the empirical
> comparison of SD vs. CFS and to determine which is best. The root of all
> the scheduler fuss was the emotional reaction of SD's author on why his
> sc
On Sun, Jul 29, 2007 at 04:18:18PM -0700, Linus Torvalds wrote:
> Ingo posted numbers. Look at those numbers, and then I would suggest some
> people could seriously consider just shutting up. I've seen too many
> idiotic people who claim that Con got treated unfairly, without those
> people admi
Hi!
This fixes few typos in kdump.txt. (Please check, I'm not native
speaker).
Also, the urls pointed out in kdump.txt seem a bit old, are there
better pointers these days?
Pavel
---
This fixes few typos in kdump.txt.
Signed-of
On Mon, 2007-07-30 at 12:09 +0200, Gabriel C wrote:
> BTW the wrong patch without the default y got merged.
Thanks. Linus, please apply.
Lguest drivers need to default to "Y" otherwise they're never selected
for new builds. We don't bother prompting, because they're less than
4k combined.
Sign
* remove space between * and symbol name in variable declaration.
* kill unnecessary new line.
* kill 'found' and test 'sd' instead.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/dir.c | 15 +--
1 files changed, 5 insertions(+), 10 deletions(-)
diff --git a/fs/sysfs/d
Hello, all.
This patchset contains a locking fix and cleanup patches for sysfs.
#01 locking fix
#02 shadow support removal from Eric adapted to apply after #01
#03-07 clean up patches
#01 should go mainline as it fixes a locking regression introduced by
-rc1 merge. The rest should stay
With the shadow directories gone, sysfs_remove_dir() can be simplified.
* parent doesn't need to be grabbed separately. Just access
old_dentry->d_parent.
* parent sd can never change. Remove code to move under the new
parent.
* Massage comments a bit.
Signed-off-by: Tejun Heo <[EMAIL PROT
sd children list walking in sysfs_lookup() and sd renaming in
sysfs_rename_dir() were left out during i_mutex -> sysfs_mutex
conversion. Fix them.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/dir.c | 21 -
1 files changed, 12 insertions(+), 9 deletions(-)
diff
Make sysfs_add_one() check for duplicate entry and return -EEXIST if
such entry exists. This simplifies node addition code a bit.
This patch doesn't introduce any noticeable behavior change.
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
---
fs/sysfs/dir.c | 25 -
fs
When adding or removing a sysfs_dirent, the user used to be required
to call link/unlink separately. It was for two reasons - code looked
like that before sysfs_addrm_cxt conversion and to avoid looping
through parent_sd->children list twice during removal.
Performance optimization during removal
With the previous sysfs_add_one() update, there is only one user of
the return value of sysfs_addrm_finish() and the user can switch to
testing @sd easily. Make sysfs_addrm_finish() return void for cleaner
semantics as suggested by Satyam Sharma.
This patch doesn't introduce any noticeable behavi
On Tue, 31 Jul 2007 10:38:48 +0200
Zoltan Menyhart <[EMAIL PROTECTED]> wrote:
> David Mosberger-Tang wrote:
> > This seems crazy to me. Flushing should occur according to the
> > *architecture*, not model-by-model. Even if we happen to get "lucky"
> > on pre-Montecito CPUs, that doesn't justify
Jarek Poplawski wrote:
> On 28-07-2007 20:42, Gabriel C wrote:
>> Andrew Morton wrote:
>>> On Sat, 28 Jul 2007 17:44:45 +0200 Gabriel C <[EMAIL PROTECTED]> wrote:
>>>
Hi,
I got this compile error with a randconfig (
http://194.231.229.228/MM/randconfig-auto-82.broken.netpoll.c
Cc: Alexey Dobriyan <[EMAIL PROTECTED]>
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
arch/blackfin/kernel/init_task.c |1 +
arch/blackfin/kernel/process.c |2 ++
arch/blackfin/kernel/sys_bfin.c |1 +
arch/blackfin/kernel/traps.c |1 +
4 files changed, 5 insertions(+), 0
On Tue, 31 Jul 2007, John Sigler wrote:
> As far as I understand, the Local APIC was integrated directly to the CPU
> 12-15 years ago. Why would a BIOS implementor choose to disable it?
Because they are lazy/incapable/out-of-time/select-your-favourite-excuse.
For the chip to work you have to p
Tejun Heo wrote:
> While shadow directories appear to be a good idea, the current scheme
> of controlling their creation and destruction outside of sysfs appears
> to be a locking and maintenance nightmare in the face of sysfs
> directories dynamically coming and going. Which can now occur for
> d
On Tue, Jul 31, 2007 at 12:09:08PM +0200, Pavel Machek wrote:
> Hi!
>
> This fixes few typos in kdump.txt. (Please check, I'm not native
> speaker).
>
> Also, the urls pointed out in kdump.txt seem a bit old, are there
> better pointers these days?
>
>
these struct *_operations are all method tables, thus should be const.
Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
---
fs/gfs2/eaops.c |8
fs/gfs2/eaops.h |4 ++--
fs/gfs2/glock.c |2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/fs/gfs2/eaops.c b/fs/gf
Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
---
fs/gfs2/ops_fstype.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index cf5aa50..9a5e840 100644
--- a/fs/gfs2/ops_fstype.c
+++ b/fs/gfs2/ops_fstype.c
@@ -28,6 +28,7 @@
#inc
these struct *_operations are all method tables, thus should be const.
Signed-off-by: Denis Cheng <[EMAIL PROTECTED]>
---
fs/gfs2/ops_dentry.c |3 +--
fs/gfs2/ops_dentry.h |2 +-
fs/gfs2/ops_vm.c |4 ++--
fs/gfs2/ops_vm.h |4 ++--
include/linux/dcache.h |2 +-
Hello everybody!
I have two machines which freeze during boot; this seems to be ACPI-related,
because with acpi=off they start.
The first one is the HP DC 7700; some summary can be seen on
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1081719
It hangs after a line
ACPI
Ph. Marek wrote:
[ added linux-acpi to CC ]
> Hello everybody!
>
> I have two machines which freeze during boot; this seems to be ACPI-related,
> because with acpi=off they start.
>
> The first one is the HP DC 7700; some summary can be seen on
> http://forums1.itrc.hp.com/service/forums/quest
Greg KH wrote:
> Rolled up patch is at:
> kernel.org/pub/linux/kernel/v2.6/stable-testing/patch-2.6.21.7-rc1.gz
^^
stable-review
--
Stefan Richter
-=-=-=== -=== =
http://arcgraph.de/sr/
-
To
On Tue, Jul 31, 2007 at 09:44:36AM +0200, Jan Blunck wrote:
> Ok, this is pretty similar to the way I implemented this for tmpfs. The
> problem is that the union mount code is explicitly checking if the filesystem
> is supporting whiteout. I used to use a new filesystem flag (FS_WHITEOUT) for
> thi
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> On Tue, 2007-07-31 at 11:10 +0200, Pavel Machek wrote:
>> > Index: kexec-tools-1.101/kexec/arch/i386/crashdump-x86.c
>> > ===
>> > --- kexec-tools-1.101.orig/kexec/arch/i386/crashdump-x86.c
On Dienstag, 31. Juli 2007, Gabriel C wrote:
> [ added linux-acpi to CC ]
Sorry, forgot to mention:
I'd like to use 2.6.20.1, but I already tested with 2.6.22.1.
IIUC if there's a problem with the ACPI tables, the blacklist won't help,
because to know whether the ACPI blacklist applies ACPI tabl
KAMEZAWA Hiroyuki wrote:
Could we discuss this in other thread as "optimization for some cpus" and
push bug-fix patches first ?
If take5 or part of take6(patch 1,2) are not acceptable, I'll continue this
work on -rc2.
Thanks,
-Kame
Sure.
Thanks,
Zoltan
-
To unsubscribe from this list: send
Hi,
Thanks for finding these bugs! I'll post an updated version soon (2 patches
with no separate Kconfig patches, one LRO and one eHEA patch). See comments
below.
Thanks,
Jan-Bernd
On Monday 30 July 2007 22:32, Andrew Gallatin wrote:
> I was working on testing the myri10ge patch, and I ran into
Hi!
> 3. Boot kernel compiled for normal usage, the reserved crash kernel
>memory region must be added to kernel command line as following:
>
>crashkernel=M@M
>
>Where, should be replaced by the real memory size and
> position.
I used [EMAIL PROTECTED] .
> 4. Load kernel compiled
Hi!
> >> >
> >> > +/* Adds the kexec_backup= command line parameter to command line. */
> >> > +static int cmdline_add_backup(char *cmdline, unsigned long addr)
> >> > +{
> >> > +int cmdlen, len, align = 1024;
> >> > +char str[30], *ptr;
> >> > +
> >> > +/* Passing in kex
Hi!
> > This part did not apply for me -- it seems crashdump related and I did
> > not have that applied. Is it critical?
>
> This is needed for kexec_jump to work properly. Which version of
> kexec-tools do you use? This patch is against 1.101. The kdump patch
> must be applied before this patch
У пн, 2007-07-30 у 22:25 +0200, <::.. Teresa_II ..::> пише:
> I am ready to provide any requested information to find issue.
Interesting Thing is that this seems to happen only on system idle. If
system is under load it behave correct.
And sometimes it doesn't appear even if system is idle.
Now
On Wed, 25 Jul 2007, Ulrich Kunitz wrote:
> The message looks like:
> sleep[7888]: segfault at 0004001C rip 0004001C rsp
> 7fff14776468 error 14
> Repeated calls get the same message with the stack pointer changing.
> Other binaries (mount) have a segmentation fault at anothe
> static unsigned long dma_reserve __initdata;
> +/* Flag indicating EFI runtime executable code area */
> +static int efi_runtime_code_area;
We don't normally use globals to modify function behaviour.
>
> DEFINE_PER_CPU(struct mmu_gather, mmu_gathers);
>
> @@ -199,7 +202,7 @@
> static __
У пн, 2007-07-30 у 22:25 +0200, <::.. Teresa_II ..::> пише:
Ok, hier is small testing:
I started gcc emerge. System load is between 1.47 and 1.61
I use SMP enabled 2.6.22.1-cfs-v19.1 kernel on ADM64 X2.
In gnome-terminal window i just type fast "d" and until i count 1,2 i
hold SHIFT, than i rele
On Tue, 2007-07-31 at 11:21 +0200, Ingo Molnar wrote:
> [ mail re-sent with lkml Cc:-ed. _Please_ Cc: all patches to lkml too!
> Unless you want -rt to suffer the fate of -ck, keep upstream involved
> all the time. The recent /proc/interrupts-all discussion with upstream
> folks showed the
1 - 100 of 647 matches
Mail list logo
