* David Miller ([EMAIL PROTECTED]) wrote:
> From: Mathieu Desnoyers <[EMAIL PROTECTED]>
> Date: Thu, 8 Mar 2007 21:15:53 -0500
>
> > Fix atomicity of TIF update in flush_thread() for x86_64
> >
> > Race :
> >
> > parent process executing :
> > sys_ptrace()
> > (lock_kernel())
> >
From: Mathieu Desnoyers <[EMAIL PROTECTED]>
Date: Thu, 8 Mar 2007 21:15:53 -0500
> Fix atomicity of TIF update in flush_thread() for x86_64
>
> Race :
>
> parent process executing :
> sys_ptrace()
> (lock_kernel())
> (ptrace_get_task_struct(pid))
> arch_ptrace()
>ptrace_detach()
>
This patch applies against commit
704e0b01791bfcb75355f269a6f0054a75c9c563
of branch 'master' from davem/net-2.6.22
---
Summary:
Peter P. Waskiewicz Jr. <[EMAIL PROTECTED]>
NET: Add packet sock option to return orig_dev to userspace when
bonded
---
Add a packet socket option to allow
Fix atomicity of TIF update in flush_thread() for x86_64
Race :
parent process executing :
sys_ptrace()
(lock_kernel())
(ptrace_get_task_struct(pid))
arch_ptrace()
ptrace_detach()
ptrace_disable(child);
clear_singlestep(child);
clear_tsk_thread_flag(child,
On Wed, Mar 07, 2007 at 03:00:57PM -0800, Andrew Morton wrote:
> On Wed, 7 Mar 2007 23:41:16 +0100
> Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > On Tue, Mar 06, 2007 at 12:44:08AM -0800, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.20-rc2-mm1:
> > >...
> > > git-netdev-all.patch
> >
> What's the error you're trying to fix? scsi_dispatch_cmd() is only
> called from scsi_request_fn() which already has an equivalent of this
> check in it just prior to calling dispatch.
Yeah, I have saw the cheking at scsi_request_fn(), recently we got a crash
info as following at rhel4
On Mar 08, 2007, at 02:24:04, Eric Dumazet wrote:
Kyle Moffett a écrit :
Prefetching is also fairly critical on a Power4 or G5 PowerPC
system as they have a long memory latency; an L2-cache miss can
cost 200+ cycles. On such systems the "dcbt" prefetch instruction
brings in a single
> Actually, I think it would make the kernel (negligibly) faster to bump
> f_pos before the vfs_write() call. Unless fget_light sets fput_needed
> or the write doesn't complete cleanly, you won't have to touch the
> file table entry again after vfs_write() returns. You can adjust
Any number of
On Fri, 9 Mar 2007, Martin Drab wrote:
> On Thu, 8 Mar 2007, Martin Drab wrote:
>
> > On Thu, 8 Mar 2007, Carsten Otte wrote:
> >
> > > On 3/8/07, Martin Drab <[EMAIL PROTECTED]> wrote:
> > > >
> > > > The thing is that I'd like to prevent kernel to swap these pages out,
> > > > because then I
On 3/8/07, Roland Dreier <[EMAIL PROTECTED]> wrote:
> When ever I try and start a guest OS with kvm I get a lot of these rtc
> missing interupt messages from the kernel
>
> [ 468.510878] rtc: lost some interrupts at 1024Hz.
I started to debug this a little while ago but I never got too
On Fri, 9 Mar 2007, Oleg Nesterov wrote:
> Ugh. Still can't understand, probably I missed something or misread this
> patch.
>
> If we shift signalfd_notify() from
> specific_send_sig_info/__group_send_sig_info
> to send_signal(), we have the same "list_empty()" fastpath if no signalfds are
>
On Thu, Mar 08, 2007 at 05:00:54PM +0530, Srivatsa Vaddagiri wrote:
> On Thu, Mar 08, 2007 at 01:50:01PM +1300, Sam Vilain wrote:
> > 7. resource namespaces
>
> It should be. Imagine giving 20% bandwidth to a user X. X wants to
> divide this bandwidth further between multi-media (10%), kernel
>
On Wednesday 07 March 2007 18:13, Rafael J. Wysocki wrote:
> On Wednesday, 7 March 2007 23:49, Andrew Morton wrote:
> > On Wed, 7 Mar 2007 23:14:29 +0100
> > "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> > > On Wednesday, 7 March 2007 22:16, Andrew Morton wrote:
> > > > On Wed, 7 Mar 2007
This patch series implements the new signalfd() and signalfd_dequeue()
system calls. I took part of the original Linus code (and you know how
badly it can be broken :), and I added even more breakage ;)
Signals are fetched from the same signal queue used by the process,
so signalfd will compete
This patch wire the signalfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/arch/i386/kernel/syscall_table.S
===
--- linux-2.6.20.ep2.orig/arch/i386/kernel/syscall_table.S
This patch wire the signalfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/include/asm-x86_64/unistd.h
===
--- linux-2.6.20.ep2.orig/include/asm-x86_64/unistd.h
This patch implement the necessary compat code for the signalfd system call.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.20.ep2/fs/compat.c
===
--- linux-2.6.20.ep2.orig/fs/compat.c 2007-03-08 12:43:36.0
This patch add an anonymous inode source, to be used for files that need
and inode only in order to create a file*. We do not care of having an
inode for each file, and we do not even care of having different names in
the associated dentries (dentry names will be same for classes of file*).
Please don't put non-kernel software in /pub/linux/kernel and
/pub/scm/linux/kernel on kernel.org.
IN PARTICULAR, if Josh is the new sparse maintainer, please contact
[EMAIL PROTECTED] so we can either create a group or simply chown the
standard locations (/pub/software/devel/sparse,
Luong Ngo wrote:
Hi Thomas and Dick,
I appreciate all the responses. They are very good information to me.
Actually, it wasn't me working on the driver but it's been there long
time. I thought I just need to add the signal and signal handling
part, not expecting it would lead me to the driver
On Wed, Mar 07, 2007 at 11:44:58PM -0700, Eric W. Biederman wrote:
> Matt Helsley <[EMAIL PROTECTED]> writes:
>
> > On Thu, 2007-03-08 at 16:32 +-1300, Sam Vilain wrote:
> >
> > +ADw-snip+AD4
> >
> > +AD4 Kirill, 06032418:36+-03:
> > +AD4 +AD4 I propose to use +ACI-namespace+ACI naming.
> > +AD4
Hi,
Is there a faster way to access "/proc/*" other than open it as a file and
reading/parsing contents? e.g. fopen("/proc/stat", "r");
In BSD, there is the kvm method of access, which is relatively fast (light
weight)
In Linux, if I have a daemon that keeps track of these statistics, it's a
--- Michael Tokarev <[EMAIL PROTECTED]> wrote:
> Jan Engelhardt wrote:
> []
> > The other thing is, the bitmap is supposed to be
> written out at intervals,
> > not at every write, so the extra head movement for
> bitmap updates should
> > be really low, and not making the tar -xjf process
>
On Wed, Mar 07, 2007 at 05:35:58PM -0800, Paul Menage wrote:
> On 3/7/07, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
>> Pretty much. For most of the other cases I think we are safe
>> referring to them as resource controls or resource limits. I know
>> that roughly covers what cpusets and
On Wed, Mar 07, 2007 at 06:32:10PM -0700, Eric W. Biederman wrote:
> "Paul Menage" <[EMAIL PROTECTED]> writes:
>
>> On 3/7/07, Sam Vilain <[EMAIL PROTECTED]> wrote:
>>> But "namespace" has well-established historical semantics too - a way
>>> of changing the mappings of local * to global objects.
On Thu, 8 Mar 2007, Robert Hancock wrote:
> Martin Drab wrote:
> > Hi,
> >
> > I'm writing a driver for a sampling device that is constantly delivering a
> > relatively high amount of data (about 16 MB/s) and I need to deliver the
> > data to the user-space ASAP. To prevent data loss I create a
I started to debug this a little while ago but I never got too far.
However it doesn't seem connected with kvm -- it is something to do
with tun/tap or bridging holding a lock too long I think.
Try running your guest with -no-kvm (and even with the kvm module not
loaded, just to be sure). In my
On Thu, Mar 08, 2007 at 03:43:47PM +0530, Srivatsa Vaddagiri wrote:
> On Wed, Mar 07, 2007 at 08:12:00PM -0700, Eric W. Biederman wrote:
> > The review is still largely happening at the why level but no
> > one is addressing that yet. So please can we have a why.
>
> Here's a brief summary of
Am Donnerstag, 8. März 2007 17:02 schrieb Alan Stern:
> On Thu, 8 Mar 2007, Oliver Neukum wrote:
>
> > Hi,
> >
> > after a lightning bolt from high above I've been looking into refcounting
> > the data structures drivers use to provide the data used to refill sysfs
> > buffers. I've come to the
- point to the sparse webpage
- use git:// instead of rsync://
Signed-off-by: Dave Jones <[EMAIL PROTECTED]>
--- linux-2.6.20.noarch/Documentation/sparse.txt~ 2007-03-08
19:40:30.0 -0500
+++ linux-2.6.20.noarch/Documentation/sparse.txt2007-03-08
19:43:01.0 -0500
On 3/8/07, Eric Dumazet <[EMAIL PROTECTED]> wrote:
Absolutely not. We dont want to slow down kernel 'just in case a fool might
want to do crazy things'
Actually, I think it would make the kernel (negligibly) faster to bump
f_pos before the vfs_write() call. Unless fget_light sets fput_needed
Thomas Gleixner wrote:
> Once you are there, you are near the point where you created a virtual
> architecture, which could run on any real architecture which gets
> supported by a hypervisor backend.
>
> I'd love that :)
>
Sure. But not even hypervisors. Once we sort out pv_ops's SMP
To let you hear the verdict.
Regards
Oliver
-- Weitergeleitete Nachricht --
Subject: Re: 2.6.21-rc suspend regression: sysfs deadlock
Date: Mittwoch, 7. März 2007 19:02
From: Linus Torvalds <[EMAIL PROTECTED]>
To: Oliver Neukum <[EMAIL PROTECTED]>
Cc:
On Thu, 8 Mar 2007, Jeremy Fitzhardinge wrote:
> Martin Drab wrote:
> > Hi,
> >
> > I'm writing a driver for a sampling device that is constantly delivering a
> > relatively high amount of data (about 16 MB/s) and I need to deliver the
> > data to the user-space ASAP. To prevent data loss I
On Thu, Mar 08, 2007 at 01:10:24AM -0800, Paul Menage wrote:
> On 3/7/07, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> >
> > Please next time this kind of patch is posted add a description of
> > what is happening and why. I have yet to see people explain why
> > this is a good idea. Why the
[ I don't really want to be involved too much in this particular
discussion, but I'll pipe up quickly anyway.. ]
On Thu, 8 Mar 2007, Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
> > For APICs, we have two operations - APICRead and APICWrite. It is
> > nice and clean, and plugs in very
Martin Drab wrote:
Hi,
I'm writing a driver for a sampling device that is constantly delivering a
relatively high amount of data (about 16 MB/s) and I need to deliver the
data to the user-space ASAP. To prevent data loss I create a queue of
buffers (consisting of few pages each) which are
Your change seems fine to me. I certainly concur that it seems insane
for init to be responsible for tasks created magically inside the
kernel. The history I've found says that the setting to SIGCHLD was
introduced as part of "v2.5.1.9 -> v2.5.1.10", without detailed
commentary in the log. This
Martin Drab wrote:
> Hi,
>
> I'm writing a driver for a sampling device that is constantly delivering a
> relatively high amount of data (about 16 MB/s) and I need to deliver the
> data to the user-space ASAP. To prevent data loss I create a queue of
> buffers (consisting of few pages each)
On Thu, 2007-03-08 at 15:55 -0800, Zachary Amsden wrote:
> Jeremy Fitzhardinge wrote:
> > No, but I'm not prejudiced against virtual hardware. If we have a piece
> > of code that thinks its talking to an apic, then I think its OK to use
> > that code whether its a real apic or a virtual one, _so
On Thu, 2007-03-08 at 15:55 -0800, Zachary Amsden wrote:
>
> We just don't drive the local timer interrupts through the APIC, we make
> hypercalls to schedule local timer alarms. Which is something we must
> do for UP kernels as well, which use the PIT / PIC. So there is a need
> for having
On Thu, 2007-03-08 at 16:14 -0800, David Miller wrote:
> The rest, like ioperm, iopl, modify_ldt, et al. are i386
> specific.
Thanks for the update. Quite why the PowerPC kernel defines system call
numbers for all of these I have no idea :)
--
dwmw2
-
To unsubscribe from this list: send the
Michael K. Edwards a écrit :
On 3/8/07, Eric Dumazet <[EMAIL PROTECTED]> wrote:
Nothing in the manuals says that write() on same fd should be non racy
: In
particular file pos might be undefined. There is a reason pwrite()
exists.
Kernel doesnt have to enforce thread safety as standard is
From: David Woodhouse <[EMAIL PROTECTED]>
Date: Thu, 08 Mar 2007 23:01:13 +
> Most system calls seem to get added to i386 first. This patch
> automatically generates a warning for any new system call which is
> implemented on i386 but not the architecture currently being compiled.
> On
On 03/08, Davide Libenzi wrote:
>
> On Fri, 9 Mar 2007, Oleg Nesterov wrote:
>
> > > Logic is, if it's not an RT signal, queue only one, otherwise multiple.
> > > The bit on the ->pending mask is clealer only when the queue slot becomes
> > > empty.
> >
> > Yes, I see what the code does, but I
On Thu, 8 Mar 2007, Jeremy Fitzhardinge wrote:
>
> The difficulty is that there are 4 different formats of signal structure
> you could get: (traditional|siginfo) x (32bit|64bit).
See my suggestion of a fixed-format (and much cleaned up) pseudo-siginfo
thing earlier in this thread, and also
Hi,
I get the following traces from 2.6.21-rc3-mm2 during the "resume" phase
of testing with 'echo test > /sys/power/disk && echo disk > /sys/power/state':
acpi thermal:00: resuming
pci :00:00.0: resuming
pcieport-driver :00:01.0: resuming
BUG: at drivers/pci/pci.c:679
Zachary Amsden wrote:
> For APICs, we have two operations - APICRead and APICWrite. It is
> nice and clean, and plugs in very easily to the APIC accessors
> available in Linux.
>
> Is this not clean?
Sure, that's clean, From that perspective the apic is a bunch of
registers backed by a state
On Thu, 8 Mar 2007, Martin Drab wrote:
> On Thu, 8 Mar 2007, Carsten Otte wrote:
>
> > On 3/8/07, Martin Drab <[EMAIL PROTECTED]> wrote:
> > >
> > > The thing is that I'd like to prevent kernel to swap these pages out,
> > > because then I may loose some data when they are not available in time
On Friday 09 March 2007 01:08, Jens Axboe wrote:
> Hi Con,
>
> One thing that has annoyed me greatly lately, is that scrolling in
> firefox very quickly becomes a huge pain if you have any load on your
> box. I typically do make -j4 kernel builds on my laptop (core duo), and
> try to stay out of
Commit 721449bf0d51213fe3abf0ac3e3561ef9ea7827a added support for using the
ADMA notifier bits to determine which commands to check for completion.
However there have been reports that this causes command timeouts in certain
cases. This is still being investigated. In addition, apparently the
On 3/8/07, Eric Dumazet <[EMAIL PROTECTED]> wrote:
Nothing in the manuals says that write() on same fd should be non racy : In
particular file pos might be undefined. There is a reason pwrite() exists.
Kernel doesnt have to enforce thread safety as standard is quite clear.
I know the standard
Linus Torvalds wrote:
> So I think you should get rid of signalfd_dequeue(), and just replace it
> with a "read()" function.
>
The difficulty is that there are 4 different formats of signal structure
you could get: (traditional|siginfo) x (32bit|64bit).
What happens if you're a 32 bit
On Thu, 2007-03-08 at 15:39 -0800, Jeremy Fitzhardinge wrote:
> Ingo Molnar wrote:
> > - /One/ _intelligent_ higher-level virtualization API/ABI. Xen's API is
> >quite advanced on this front.
>
> At last! Some love!
>
> The Xen approach has always been to prefer high-level interfaces over
Jeremy Fitzhardinge wrote:
No, but I'm not prejudiced against virtual hardware. If we have a piece
of code that thinks its talking to an apic, then I think its OK to use
that code whether its a real apic or a virtual one, _so long as its
being used in a way that's consistent with its intended
On Fri, 9 Mar 2007, Ingo Molnar wrote:
>
> disabling the following radeonfb options in the .config made resume work
> again:
In general, don't even *try* to use radeonfb for suspend/resume.
I don't think it has ever worked, except on some very rare laptops
(largely PPC Macs) where people
Linus, please pull from
master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git for-linus
This tree is also available from kernel.org mirrors at:
git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git
for-linus
This will get various post-rc3 fixes:
David Miller
Michael K. Edwards a écrit :
from sys_write():
file = fget_light(fd, _needed);
if (file) {
loff_t pos = file_pos_read(file);
ret = vfs_write(file, buf, count, );
file_pos_write(file, pos);
fput_light(file, fput_needed);
Ingo Molnar wrote:
> - /One/ _intelligent_ higher-level virtualization API/ABI. Xen's API is
>quite advanced on this front.
At last! Some love!
The Xen approach has always been to prefer high-level interfaces over
lower-level ones, so that guests can meaningfully participate in their
own
Ingo Molnar wrote:
* Zachary Amsden <[EMAIL PROTECTED]> wrote:
[...] So it is a little late to tell us - "redesign your hypervisor,
or else.."
is this how long the "paravirt_ops hides all the details and the VMI
hypervisor ABI will never hinder Linux" sham lasted? Now that your
> Surely that's racy when two threads write to the same fd and the first
> vfs_write call blocks or is preempted. Or does fget_light take some
> per-file lock that I'm not seeing?
I think you are making assumptions about file position behaviour that are
simply not guaranteed in the standards
Andrew Johnson wrote:
When the console is in VT_AUTO/KD_GRAPHICS mode, switching to the
SUSPEND_CONSOLE fails, resulting in vt_waitactive() waiting indefinately
or until the task is interrupted. The following patch tests if a
console switch can occur in set_console() and returns early if a
On Monday 05 March 2007 05:35, Antonino A. Daplas wrote:
> On Mon, 2007-03-05 at 02:50 +0100, Adrian Bunk wrote:
> > This email lists some known regressions in 2.6.21-rc2 compared to 2.6.20
> > that are not yet fixed in Linus' tree.
> >
> > If you find your name in the Cc header, you are either
Hi!
> > On 12.02.2007 01:10 I wrote:
> > > I don't doubt your basic assessment. However it doesn't translate that
> > > easily into a real implementation. In my case, I maintain a USB driver,
> > > so I have to deal with USB specifics of suspend/resume which happen not
> > > to be that well
On Thu 8 Mar 2007 15:40, Russell King pondered:
> On Thu, Mar 08, 2007 at 03:23:39PM -0500, Robin Getz wrote:
> > Right - We both agree - And setting console=/dev/null in the bootargs
> > still does not help.
>
> Ok, good.
>
> > When the kernel initializes the UART Port, it asserts RTS - which
> >
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > Here's another suspend/resume artifact: one of my boxes wouldnt
> > resume, it hangs at:
> >
> > [1.456633] pci :00:18.2: resuming
> > [1.456641] pci :00:18.3: resuming
> > [1.456648] 8139too :05:07.0: resuming
> > [
[PATCH] drivers: PMC MSP71xx TWI driver
Patch to add TWI driver for the PMC-Sierra MSP71xx devices.
This patch references some platform support files previously
submitted to the [EMAIL PROTECTED] list.
Thanks,
Marc
Signed-off-by: Marc St-Jean <[EMAIL PROTECTED]>
---
Re-posting patch with
On Thu, 8 Mar 2007, Martin Drab wrote:
> Hi,
>
> I'm writing a driver for a sampling device that is constantly delivering a
> relatively high amount of data (about 16 MB/s) and I need to deliver the
> data to the user-space ASAP. To prevent data loss I create a queue of
> buffers (consisting
On Thu, 08 Mar 2007 17:58:16 -0500 Mimi Zohar wrote:
> This is a request for comments for a new Integrity Based Access
> Control(IBAC) LSM module which bases access control decisions
> on the new integrity framework services.
>
> (Hopefully this will help clarify the interaction between an LSM
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> Here's another suspend/resume artifact: one of my boxes wouldnt
> resume, it hangs at:
>
> [1.456633] pci :00:18.2: resuming
> [1.456641] pci :00:18.3: resuming
> [1.456648] 8139too :05:07.0: resuming
> [1.456667] radeonfb
Hi Pavel,
When the console is in VT_AUTO/KD_GRAPHICS mode, switching to the
SUSPEND_CONSOLE fails, resulting in vt_waitactive() waiting indefinately
or until the task is interrupted. The following patch tests if a
console switch can occur in set_console() and returns early if a console
switch is
* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> Thomas found a new twist to this today: applying the patch below
> (which turns on ATA_DEBUG) made the SATA problem go away on his
> laptop. Michael, could you try this patch, does it change the behavior
> of your laptop in any way?
Here's another
from sys_write():
file = fget_light(fd, _needed);
if (file) {
loff_t pos = file_pos_read(file);
ret = vfs_write(file, buf, count, );
file_pos_write(file, pos);
fput_light(file, fput_needed);
}
Surely that's racy
On Fri, 9 Mar 2007, Oleg Nesterov wrote:
> > Logic is, if it's not an RT signal, queue only one, otherwise multiple.
> > The bit on the ->pending mask is clealer only when the queue slot becomes
> > empty.
>
> Yes, I see what the code does, but I don't undestand why. For example,
> SIGCHLD was
Jan Engelhardt wrote:
[]
> The other thing is, the bitmap is supposed to be written out at intervals,
> not at every write, so the extra head movement for bitmap updates should
> be really low, and not making the tar -xjf process slower by half a minute.
> Is there a way to tweak the
Most system calls seem to get added to i386 first. This patch
automatically generates a warning for any new system call which is
implemented on i386 but not the architecture currently being compiled.
On PowerPC at the moment, for example, it results in these warnings:
On Thu, 2007-03-08 at 18:29 +0100, Ingo Molnar wrote:
> * Nick Piggin <[EMAIL PROTECTED]> wrote:
>
> > Hi Ingo,
> >
> > I'm seeing an LTP test fail for ltp test sigaction_16_24. Basically,
> > it tests whether the SA_RESTART flag works for the sem_wait operation.
Not sure, whether the testcase
On Thu, 8 Mar 2007, Linus Torvalds wrote:
>
>
> On Fri, 9 Mar 2007, Oleg Nesterov wrote:
> >
> > Also. A malicious user can eat all memory,
> > signalfd_deliver()->kmem_cache_alloc()
> > doesn't check any limits.
>
> This, btw, is one reason I *really* think signalfd() should just use the
>
Andi Kleen wrote:
At least in Linux we don't really work with deadlines; if there
are issues they need to be fixed even if it takes longer. I don't
expect the version in .21 to be really usable anyways; it is clearly
still in development.
It was working, and I expect to have it working
modprobe irda ; rmmod irda in 2.6.21rc3 gets me the spew below..
Dave
NET: Registered protocol family 23
NET: Unregistered protocol family 23
=
[ INFO: possible recursive locking detected ]
2.6.20-1.2966.fc7 #1
David Howells <[EMAIL PROTECTED]> wrote:
> These patches together supply secure client-side RxRPC connectivity as a Linux
> kernel socket family. Only the transport/session side is supplied - the
> presentation side (marshalling the data) is left to the client.
The patches can also be
On Thu, 08 Mar 2007 22:48:29 GMT, David Howells said:
>
> diff --git a/include/linux/crypto.h b/include/linux/crypto.h
> index 779aa78..ce092fe 100644
> --- a/include/linux/crypto.h
> +++ b/include/linux/crypto.h
> @@ -40,7 +40,10 @@
> #define CRYPTO_ALG_LARVAL0x0010
> #define
On 3/8/07, Thomas Gleixner <[EMAIL PROTECTED]> wrote:
On Thu, 2007-03-08 at 08:01 -0500, linux-os (Dick Johnson) wrote:
> > Anything kernel configuration I need to be aware of to enable
> > preemption in kernel?
> >
> >
> > Thank you,
> > LNgo
> >
>
> First, in the ioctl, if you need spin-locks,
Export try_to_del_timer_sync() for use by the RxRPC module.
Add a try_to_cancel_delayed_work() so that it is possible to merely attempt to
cancel a delayed work timer.
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
---
include/linux/workqueue.h | 21 +
kernel/timer.c
Export the keyring key type definition.
Add extra alternative types into the key's type_data union to make it more
useful.
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
---
include/linux/key.h |2 ++
security/keys/keyring.c |2 ++
2 files changed, 4 insertions(+), 0 deletions(-)
Move generic skbuff stuff from XFRM code to generic code so that AF_RXRPC can
use it too.
Signed-Off-By: David Howells <[EMAIL PROTECTED]>
---
include/linux/skbuff.h |4 +
include/net/esp.h |2 -
net/core/skbuff.c | 173
These patches together supply secure client-side RxRPC connectivity as a Linux
kernel socket family. Only the transport/session side is supplied - the
presentation side (marshalling the data) is left to the client.
The userspace access methods make use of the control data passed to/by
sendmsg()
Add blkcipher accessors for using kernel data directly without the use of
scatter lists.
Also add a CRYPTO_ALG_DMA algorithm capability flag to permit or deny the use
of DMA and hardware accelerators. A hardware accelerator may not be used to
access any arbitrary piece of kernel memory lest it
This is a request for comments for a new Integrity Based Access
Control(IBAC) LSM module which bases access control decisions
on the new integrity framework services.
(Hopefully this will help clarify the interaction between an LSM
module and LIM module.)
Index:
* Zachary Amsden <[EMAIL PROTECTED]> wrote:
> [...] So it is a little late to tell us - "redesign your hypervisor,
> or else.."
is this how long the "paravirt_ops hides all the details and the VMI
hypervisor ABI will never hinder Linux" sham lasted? Now that your stuff
is upstream barely 2
From: Jarek Poplawski <[EMAIL PROTECTED]>
Date: Thu, 8 Mar 2007 08:47:51 +0100
> On 25-02-2007 10:08, Simon Arlott wrote:
> > This happens on every boot if more information is needed:
> >
> > [ 37.393715] =
> > [ 37.393830] [ INFO: inconsistent lock state ]
>
Ingo Molnar wrote:
* Zachary Amsden <[EMAIL PROTECTED]> wrote:
Ingo, either you or Thomas have vetoed every attempt we have made to
make our code operate with clockevents. [...]
this is news to me - do you have any proof of such a veto?
Yes, your refusal to discuss any technical
Ingo Molnar wrote:
[...] And apparently the VMI version is the same, just with some short
cuts. Are you just worried about the ->apic_write() hooks or about
something else too?
i'm worried about those "shot cuts" (which in essence create software
variants of silicon), the hooks, the
On Thursday 08 March 2007 19:49, Tom Rini wrote:
> On Thu, Mar 08, 2007 at 07:37:56PM +0100, Andi Kleen wrote:
> > On Thursday 08 March 2007 18:44, Dave Jiang wrote:
> >
> > > In spite of kgdb, shouldn't it have that \n anyways in case some other
> > > code
> > > gets added in the future after
* Zachary Amsden <[EMAIL PROTECTED]> wrote:
> Ingo, either you or Thomas have vetoed every attempt we have made to
> make our code operate with clockevents. [...]
this is news to me - do you have any proof of such a veto?
Ingo
-
To unsubscribe from this list: send the line
Jeremy Fitzhardinge wrote:
Zachary Amsden wrote:
We faithfully emulate lapic, io_apic, the pit, pic, and a normal
interrupt subsystem.
Can you not just use the apic clock driver directly then? Do you need
to do anything special?
The apic clock driver is going to program the
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> > what we do _NOT_ want is some mixture of 'simplified' and
> > 'hardwired' native hardware access mixed with hypercalls that
> > somehow ends up creating a Frankenstein mixture of 'virtual
> > silicon', is specified nowhere else but in VMWare's
On Thu, 2007-03-08 at 11:49 -0700, Tom Rini wrote:
> On Thu, Mar 08, 2007 at 07:37:56PM +0100, Andi Kleen wrote:
> > On Thursday 08 March 2007 18:44, Dave Jiang wrote:
> >
> > > In spite of kgdb, shouldn't it have that \n anyways in case some other
> > > code
> > > gets added in the future after
Bino, James,
Please review, sign-off and forward upstream.
--linas
If a PCI error is detected that cannot be recovered from, there
will be a double call of lpfc_pci_remove_one(), with the second call
resulting in a null-pointer dereference. The first call occurs in
lpfc_io_error_detected(),
Anton Blanchard wrote:
2. The badblocks stuff is PAGE_SIZEd too. Do we ever use it on modern
disks? Maybe we can just remove this support.
Badblocks is definitely still used in some configurations.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
101 - 200 of 1073 matches
Mail list logo
