On Saturday June 9, [EMAIL PROTECTED] wrote:
> Hi,
>
> As we know the forthcoming GPL V3 will be not compatible with the GPL V2
> and Linux Kernel is GPL V2 only.
> So, another point is, which is previously mentioned by Linus and others,
> that if it is decided to upgrade the Linux Kernel's
From: Zhang Rui <[EMAIL PROTECTED]>
Well, first of all, I don't want to change so many files either.
What I do:
Adding a new parameter "struct bin_attribute *" in the
.read/.write methods for the sysfs binary attributes.
In fact, only the four lines change in fs/sysfs/bin.c and
Hi,
As we know the forthcoming GPL V3 will be not compatible with the GPL V2
and Linux Kernel is GPL V2 only.
So, another point is, which is previously mentioned by Linus and others,
that if it is decided to upgrade the Linux Kernel's License to GPL V3,
it is needed the permission of all the
On Fri, 8 Jun 2007 22:18:40 -0700 (PDT)
[EMAIL PROTECTED] wrote:
> the way I would describe the difference betwen AA and SELinux is:
>
> SELinux is like a default allow IPS system, you have to describe
> EVERYTHING to the system so that it knows what to allow and what to stop.
>
> AA is like a
On Fri, 8 Jun 2007 22:38:57 -0700 (PDT)
[EMAIL PROTECTED] wrote:
> so are you suggesting that SELinux would call out to userspace for every
> file open to get the label for that file?
>
No, i'm not. You must already have a kernel function in the current
implementation of AA that decides the
Davide Libenzi writes:
> The only reason we use a floating base, is because Uli preferred to have
> non-exactly predictable fd allocations. There no reason of re-doing the
> same POSIX mistake all over again:
Why must everything that makes things a bit simpler and more
predictable for
On Sat, 9 Jun 2007, Sean wrote:
the AA policy is also much easier to understand becouse you can look at it
in pieces, understand that piece, and then forget it and move on to the
next piece.
Nobody is asking you to change the AA policy file. It lives in user space.
But i fail to see the
On Fri, 8 Jun 2007, Greg KH wrote:
I still want to see a definition of the AA "model" that we can then use
to try to implement using whatever solution works best. As that seems
to be missing the current argument of if AA can or can not be
implemented using SELinux or something totally
On 6/8/07, Alan Cox <[EMAIL PROTECTED]> wrote:
> There is an SE Linux execmem restriction that enforces W^X.
This depends on whatever SELinux rulesets you are running. Its just a
good rule to have present that most programs shouldn't be self patching,
and then label those that do differently.
On Fri, 8 Jun 2007 21:56:06 -0700 (PDT)
[EMAIL PROTECTED] wrote:
>
> with AA hardlinks are effectivly different labels on the same file
So what? SELinux can be be altered to accept whatever label you generate.
Pass it whatever label you want.
> one of the big problems with SELinux is what
On Fri, 8 Jun 2007, Sean wrote:
On Sat, 9 Jun 2007 11:01:41 +0900
Tetsuo Handa <[EMAIL PROTECTED]> wrote:
From the discussion so far, it seems that the different "model" that AA
is trying to implement, is to do in one step what SELinux does in two
steps; that is trying to combine labelling
Andrew Morton wrote:
On Fri, 08 Jun 2007 17:43:34 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
Some user space tools need to identify SYSV shared memory when
examining /proc//maps. To do so they look for a block device
with major zero, a dentry named SYSV, and having the minor of
the
On 6/8/07, Eric Dumazet <[EMAIL PROTECTED]> wrote:
Albert Cahalan a écrit :
> Additions to better support JIT emulators:
>
> a. sysctl to set IPC_RMID by default
Not very good, this will break some apps.
As a sysctl, the admin gets to choose between
compatibility and sanity.
I can see
Hello,
This patch makes the i386 behave the same way that x86_64 does when a
segfault happens. A line gets printed to the kernel log so that tools
that need to check for failures can behave more uniformly between
different kernels. Like x86_64, it can be disabled by setting
On Sat, 9 Jun 2007 11:01:41 +0900
Tetsuo Handa <[EMAIL PROTECTED]> wrote:
>From the discussion so far, it seems that the different "model" that AA
is trying to implement, is to do in one step what SELinux does in two
steps; that is trying to combine labelling and enforcement into a
single step.
I have noticed that recent kernels, 2.6.16 through at least 2.6.19,
hyperthreading
can no longer be effectively disabled by using maxcpus. This means that anyone
that
was using maxcpus to disable hyperthreading when running Linux will no longer be
using all of their physical cpus.
The following
Andrew Morton wrote:
On Thu, 07 Jun 2007 12:11:58 -0400
Chuck Ebbert <[EMAIL PROTECTED]> wrote:
On 06/07/2007 11:41 AM, Andrew Morton wrote:
mount /var/lib/mythtv -oremount,ro
sync
umount /var/lib/mythtv
Did this succeed? If the application is still truncating that file, the
umount
Andrew Morton wrote:
> On Fri, 08 Jun 2007 23:43:46 +0530
> Balbir Singh <[EMAIL PROTECTED]> wrote:
>
>> This patch implements per container statistics infrastructure and re-uses
>> code from the taskstats interface.
>
> boggle.
>
> Symbol: CONTAINERS [=y]
> Selected by: CONTAINER_DEBUG ||
On 2007.06.09 04:27:10 +0200, Björn Steinbrink wrote:
> On 2007.06.08 22:43:25 +0200, Ingo Molnar wrote:
> >
> > * Björn Steinbrink <[EMAIL PROTECTED]> wrote:
> >
> > > Anyway, both are bugs and should be fixed. Maybe we're even lucky and
> > > it fixes your hang. *fingers crossed*
> >
> >
On 2007.06.08 22:43:25 +0200, Ingo Molnar wrote:
>
> * Björn Steinbrink <[EMAIL PROTECTED]> wrote:
>
> > Anyway, both are bugs and should be fixed. Maybe we're even lucky and
> > it fixes your hang. *fingers crossed*
>
> just to make it clear: the NMI watchdog was working perfectly fine on
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Al Viro wrote:
> Any real-world examples of exploitable holes based on that?
Return to libc exploit, calling dup2, where some privileged data is
redirected from the normal file descriptor to one of the attackers
choosing. The latter could be an
From: Trond Myklebust <[EMAIL PROTECTED]>
Date: Fri, 08 Jun 2007 17:43:27 -0400
> It is not dhcp. I'm seeing the same bug with bog-standard ifup with a
> static address on an FC-6 machine.
>
> It appears to be something in the latest dump from davem to Linus, but I
> haven't yet had time to
Hello.
David Lang wrote:
> as I understand it SELinux puts one label on each file, so if you have
> three files accessed by two programs such that
> program A accesses files X Y
> program B accesses files Y Z
>
> then files X Y and Z all need separate labels with the policy stateing
> that
Sam Ravnborg wrote:
On Fri, Jun 08, 2007 at 11:32:29AM -0700, Tom wrote:
From: Tom Enderes <[EMAIL PROTECTED]>
The kernel build failed on cygwin hosts, because cygwin has slightly
different typedefs compared to linux:
scripts/mod/file2alias.c:518: error: dereferencing pointer to incomplete
On Fri, Jun 08, 2007 at 06:19:28PM -0700, Ulrich Drepper wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Al Viro wrote:
> > Exactly. Put it another way, randomizer is a stress-tester.
>
> ... and a security mechanism. And as such it is only useful if it is
> used. Probably it
From: Paul Jackson <[EMAIL PROTECTED]>
Third of three -- This applies after the container patches,
fixing a problem that earlier patches also fixed in the older
cpuset code.
The container code to present a list of tasks using a container
to user space could write to an array that it had
From: Paul Jackson <[EMAIL PROTECTED]>
First of three -- this one goes before the container patches,
and should be sent to Linus for 2.6.22.
The cpuset code to present a list of tasks using a cpuset to
user space could write to an array that it had kmalloc'd,
after a kmalloc request of zero
From: Paul Jackson <[EMAIL PROTECTED]>
Second of three -- This one undoes the first one. Apply before
the container patch that changes cpusets to use containers,
in order to avoid a patch conflict.
The cpuset code to present a list of tasks using a cpuset to
user space could write to an array
Please cc networking patches to [EMAIL PROTECTED]
Jeff Layton <[EMAIL PROTECTED]> wrote:
>
> The following patch is a first stab at removing this need. It makes it
> so that in tcp_recvmsg() we also check kthread_should_stop() at any
> point where we currently check to see if the task was
On Sat, Jun 09, 2007 at 11:20:43AM +1000, Herbert Xu wrote:
> Chris Wright <[EMAIL PROTECTED]> wrote:
> >
> > --- linux-2.6.20.13.orig/net/ipv4/Kconfig
> > +++ linux-2.6.20.13/net/ipv4/Kconfig
> > @@ -43,11 +43,11 @@ config IP_ADVANCED_ROUTER
> > asymmetric routing (packets from you to a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Al Viro wrote:
> Exactly. Put it another way, randomizer is a stress-tester.
... and a security mechanism. And as such it is only useful if it is
used. Probably it should be policy-controlled whether you can turn it off.
> Note that
> #define
Chris Wright <[EMAIL PROTECTED]> wrote:
>
> --- linux-2.6.20.13.orig/net/ipv4/Kconfig
> +++ linux-2.6.20.13/net/ipv4/Kconfig
> @@ -43,11 +43,11 @@ config IP_ADVANCED_ROUTER
> asymmetric routing (packets from you to a host take a different path
> than packets from that host to
Trond Myklebust <[EMAIL PROTECTED]> wrote:
>
> It appears to be something in the latest dump from davem to Linus, but I
> haven't yet had time to identify what.
You want this patch which should hit the tree soon.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu
On Fri, 8 Jun 2007, Greg KH wrote:
On Sat, Jun 09, 2007 at 12:03:57AM +0200, Andreas Gruenbacher wrote:
AppArmor is meant to be relatively easy to understand, manage, and customize,
and introducing a labels layer wouldn't help these goals.
Woah, that describes the userspace side of AA just
Robert P. J. Day wrote:
>
> and once again, an initially innocuous question quickly leaves me
> behind. no, no, i'm getting used to it. :-P
>
This is what happens when you stir the muck on the bottom. This is
probably a good thing.
-hpa
-
To unsubscribe from this list: send the line
Andrew Lyon wrote:
>
> I have run memtest86+ for days at a time on both systems with no errors
> at all.
>
> broken hardware i guess, i am not surprised about the abit board, ive
> had nothing but trouble with abit motherboards and do not use them any
> more, but the supermicro is a xeon server
On Fri, Jun 08, 2007 at 05:03:57PM -0700, Linus Torvalds wrote:
>
>
> On Fri, 8 Jun 2007, Davide Libenzi wrote:
> >
> > On Fri, 8 Jun 2007, Linus Torvalds wrote:
> > >
> > > You need things to be *repeatable* for debugging. No ifs, buts, or maybes
> > > about it.
> >
> > It all depends on how
Andy Whitcroft wrote:
> This version brings a some new tests, and a host of changes to fix
> false positives, of particular note:
>
> - check for and report #if 0
> - extend checking of line lengths and spacing for .pl, .sh etc
> - extends the pointer type checks to multiple levels
> -
From: Kay Sievers <[EMAIL PROTECTED]>
Signed-off-by: Kay Sievers <[EMAIL PROTECTED]>
Cc: bert hubert <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
drivers/usb/core/Kconfig | 22 +-
1 files changed, 13 insertions(+), 9 deletions(-)
diff --git
On Sat, Jun 09, 2007 at 12:03:57AM +0200, Andreas Gruenbacher wrote:
> AppArmor is meant to be relatively easy to understand, manage, and customize,
> and introducing a labels layer wouldn't help these goals.
Woah, that describes the userspace side of AA just fine, it means
nothing when it comes
On Fri, 8 Jun 2007, Linus Torvalds wrote:
> On Fri, 8 Jun 2007, Davide Libenzi wrote:
> >
> > On Fri, 8 Jun 2007, Linus Torvalds wrote:
> > >
> > > You need things to be *repeatable* for debugging. No ifs, buts, or maybes
> > > about it.
> >
> > It all depends on how you use the file
* fix PIO setup for devices with different PIO speeds in passthru mode
IT821x allows one PIO setting per port se we have to limit maximum
PIO mode to the one of the slowest device on the port.
* (partially) fix DMA in RAID mode
Code intended to check DMA status was checking DMA command
On Fri, Jun 08, 2007 at 10:45:10AM -0600, [EMAIL PROTECTED] wrote:
> From: Douglas Thompson <[EMAIL PROTECTED]>
>
> pci_ids.h needs two of the AMD NB device-ids namely,
> Addressmap and the Memory Controller devices
Does any kernel driver need this? We're trying to only include things
in the
On Fri, 8 Jun 2007, Davide Libenzi wrote:
>
> On Fri, 8 Jun 2007, Linus Torvalds wrote:
> >
> > You need things to be *repeatable* for debugging. No ifs, buts, or maybes
> > about it.
>
> It all depends on how you use the file descriptor.
Read what I wrote. "for debugging".
If your code is
From: Alan Stern <[EMAIL PROTECTED]>
This patch (as904) adds code to check for endpoint descriptor bInterval
values outside the legal limits. Illegal values are set to 32 ms, which
seems like a reasonable default.
This fixes Bugzilla #8432.
Signed-off-by: Alan Stern <[EMAIL PROTECTED]>
From: Alan Stern <[EMAIL PROTECTED]>
This patch (as901) fixes an oversight in ohci-hcd. The
hub_status_data routine must not try to access the controller's
memory-mapped registers if the controller is in a low-power state;
such attempts will cause a crash on some architectures (such as PPC).
From: Simon Arlott <[EMAIL PROTECTED]>
The sysfs adsl_status attribute ignores (aside from returning -EIO to the
user) any error sending a START/STOP command to the device and there is at
least one firmware which never sends a response but appears to work
regardless. Therefore atm_start should
From: Simon Arlott <[EMAIL PROTECTED]>
Since usbatm doesn't set the usb_interface driver data until after calling
bind and heavy_init, it would be NULL when the sysfs attributes are read.
Reading the MAC address from atm_dev before atm_dev exists would have been
be possible too.
Calling
From: Ben Collins <[EMAIL PROTECTED]>
UNUSUAL_DEV: Sync up some reported devices from Ubuntu
Various unusual dev entries accumulated from Ubuntu bug reports.
Signed-off-by: Ben Collins <[EMAIL PROTECTED]>
Cc: Alan Stern <[EMAIL PROTECTED]>
Signed-off-by: Phil Dibowitz <[EMAIL PROTECTED]>
---
From: Simon Arlott <[EMAIL PROTECTED]>
The sysfs attributes for exposing cxacru statistics/status information with
possible values is now explained in Documentation/networking/cxacru.txt
including information on the writable adsl_state attribute's commands and a
sample of the kernel log format.
From: Pete Zaitcev <[EMAIL PROTECTED]>
Suspend destroys refcounting for open/release.
Signed-off-by: Pete Zaitcev <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
drivers/usb/class/usblp.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git
From: David Brownell <[EMAIL PROTECTED]>
It turns out that le16_to_cpup() and le32_to_cpup() aren't always safe
to call with pointers into packed structures, since those are inlined
functions and GCC may lose the "packed" attribute. So those references
can become unaligned kernel accesses, which
Here are some USB fixes against your 2.6.22-rc4 tree.
They fix a number of minor things and update some documentation and add
some usb-storage quirks, and make the config option a default that has
been tripping up some usbfs users with older udev configurations.
All of these have been in the -mm
On Fri, 08 Jun 2007 17:43:34 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Some user space tools need to identify SYSV shared memory when
> examining /proc//maps. To do so they look for a block device
> with major zero, a dentry named SYSV, and having the minor of
> the internal sysv
On Sat, Jun 09, 2007 at 12:02:28AM +0100, Richard Purdie wrote:
> On Fri, 2007-06-08 at 11:57 -0700, Greg KH wrote:
> > On Fri, Jun 01, 2007 at 05:23:24PM +0100, Richard Purdie wrote:
> > > I still question whether either colour or function properties are
> > > actually particularly useful to
Some user space tools need to identify SYSV shared memory when
examining /proc//maps. To do so they look for a block device
with major zero, a dentry named SYSV, and having the minor of
the internal sysv shared memory kernel mount.
To help these tools and to make it easier for people just
Jesse Barnes <[EMAIL PROTECTED]> writes:
>> - Overlapping MTRRs.
>
> Overlapping should be ok, since that's usually intentional (e.g. one big
> wb range with a portion of uc space due to another mtrr).
I'm not say overlapping was a bug. I was saying that you don't handle
overlapping mtrrs in
The downside: We need mem_map[] struct page entries behind all memory
segments. Nowerdays we can easily create those via vmem_map/sparsemem.
Opinions?
Frankly this is going to be mostly relevant on ARM architectures at
least at first. Maybe I'm missing something but I don't see that
sparemem
On Fri, 2007-06-08 at 11:57 -0700, Greg KH wrote:
> On Fri, Jun 01, 2007 at 05:23:24PM +0100, Richard Purdie wrote:
> > I still question whether either colour or function properties are
> > actually particularly useful to userspace other than for naming purposes
> > which is why they were part of
On Sat, 9 Jun 2007, Andi Kleen wrote:
> > Why was it not allowed? Because interrupts are disabled?
>
> Allocating memory during page out under low memory could
> lead to deadlocks. That is because Linux used to make no attempt
> to limit dirty pages for anonymous mappings and then you could
>
On Saturday 09 June 2007 00:36, Christoph Lameter wrote:
> On Fri, 8 Jun 2007, Andreas Kleen wrote:
> > > That's what kmem_cache_alloc() is for?!?!
> >
> > Tradtionally that was not allowed in block layer path. Not sure
> > it is fully obsolete with the recent dirty tracking work, probably not.
>
On Fri, 8 Jun 2007, Keshavamurthy, Anil S wrote:
> > What functionality are you missing in the page allocator? It seems that is
> > does what you want?
> Humm..I basically want to allocate memory during interrupt context and
> expect not to fail. I know this is a hard requirement :)
The page
On Fri, Jun 08, 2007 at 03:33:39PM -0700, Christoph Lameter wrote:
> On Fri, 8 Jun 2007, Keshavamurthy, Anil S wrote:
>
> > > You _seem_ to be saying that the resource pools are there purely for
> > > alloc/free performance reasons. If so, I'd be skeptical: slab is pretty
> > > darned fast.
> >
On Fri, Jun 08, 2007 at 03:32:08PM -0700, Christoph Lameter wrote:
> On Fri, 8 Jun 2007, Keshavamurthy, Anil S wrote:
>
> > In the IOMMU case, we need exactly opposite of what mempool provides,
> > i.e we always want to look for the element in the pool and if the pool
> > has no element then go
Will Schmidt <[EMAIL PROTECTED]> writes:
> On Fri, 2007-06-08 at 12:32 -0700, Andrew Morton wrote:
>> On Fri, 08 Jun 2007 14:19:18 -0500
>> Will Schmidt <[EMAIL PROTECTED]> wrote:
>>
>> > > > > zap_other_threads() requires tasklist_lock.
>> >
>
>> In fact, it's probably the case that
Currently there are 97 occurrences where drivers need the pci
revision ID. We can do this once for all devices. Even the pci
subsystem needs the revision several times for quirks. The extra
u8 member pads out nicely in the pci_dev struct.
Signed-off-by: Auke Kok <[EMAIL PROTECTED]>
---
Jack Stone wrote:
> Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
Acked-By: H. Peter Anvin <[EMAIL PROTECTED]>
As far as I can tell, autofs 3 has fallen into disuse, and autofs 4/5
has matured to the point where I don't think there is any major reason
to use autofs 3 anymore. It probably should
On Fri, 8 Jun 2007, Alan Cox wrote:
> > > > It does not work. What if the main application, library A and library B
> > > > wants to implement their own allocation strategy?
> > >
> > > Its called "discipline". I would suggest that libc contains a default
> > > allocator. You might also want to
On Fri, 8 Jun 2007, Andreas Kleen wrote:
> > That's what kmem_cache_alloc() is for?!?!
>
> Tradtionally that was not allowed in block layer path. Not sure
> it is fully obsolete with the recent dirty tracking work, probably not.
Why was it not allowed? Because interrupts are disabled?
>
On Fri, 8 Jun 2007, Siddha, Suresh B wrote:
> > If for some reason you really can't do that (and a requirement for
> > allocation-in-interrupt is the only valid reason, really) and if you indeed
> > can demonstrate memory allocation failures with certain workloads then
> > let's take a look at
Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
---
-#ifdef DEBUG
-#define DPRINTK(D) (printk D)
-#else
-#define DPRINTK(D) ((void)0)
-#endif
-
/*
* If the daemon returns a negative response (AUTOFS_IOC_FAIL) then the
* kernel will keep the negative response cached for up to the time given
On Fri, 8 Jun 2007, Keshavamurthy, Anil S wrote:
> > You _seem_ to be saying that the resource pools are there purely for
> > alloc/free performance reasons. If so, I'd be skeptical: slab is pretty
> > darned fast.
> We need several objects of size say( 4 * sizeof(u64)) and reuse
> them in dma
Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
---
-#define DPRINTK(fmt, args...) if (debug_alternative) \
- printk(KERN_DEBUG fmt, args)
-
#ifdef GENERIC_NOP1
/* Use inline assembly to define this because the nops are defined
as inline assembly strings in the include files and we
On Fri, 8 Jun 2007, Keshavamurthy, Anil S wrote:
> In the IOMMU case, we need exactly opposite of what mempool provides,
> i.e we always want to look for the element in the pool and if the pool
> has no element then go to OS as a worst case. This resource pool
> library routines do the same.
Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
---
#ifdef DEBUG
-#define DPRINTK(fmt,args...) do { printk(KERN_DEBUG "pid %d: %s: " fmt
"\n" , current->pid , __FUNCTION__ , ##args); } while(0)
+#define DPRINTK(fmt,args...) do { pr_debug("pid %d: %s: " fmt "\n" ,
current->pid , __FUNCTION__ ,
On Sat, 9 Jun 2007 00:42:50 +0200
Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
> On Friday 08 June 2007, Alan Cox wrote:
> > On Fri, 8 Jun 2007 14:18:55 +0200
> > Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
> >
> > > On Monday 04 June 2007, Jiri Slaby wrote:
> > > > ide-generic,
On Friday 08 June 2007 22:55, Andrew Morton wrote:
> On Fri, 8 Jun 2007 22:43:10 +0200 (CEST)
>
> Andreas Kleen <[EMAIL PROTECTED]> wrote:
> > > That's what kmem_cache_alloc() is for?!?!
> >
> > Tradtionally that was not allowed in block layer path. Not sure
> > it is fully obsolete with the
On Thu, 7 Jun 2007, Andrew Morton wrote:
> > +void *iommu_rpool_alloc(unsigned int size, gfp_t flag)
> > +{
> > + if (size == PAGE_SIZE_4K)
> > + return(void *)get_zeroed_page(flag);
> > + else
> > + return kzalloc(size, flag);
> > +}
>
> kmalloc(4k) is pretty efficient
Andrew,
Can you include this in -mm ?
Thanks,
Badari
shmid used to be stored as inode# for shared memory segments. Some of
the proc-ps tools use this from /proc/pid/maps. Recent cleanups
to newseg() changed it. This patch sets inode number back to shared
memory id to fix breakage.
> None of the patches posted by Björn fix the kernel BUG at
> arch/i386/kernel/cpu/perfctr-watchdog.c:126! that occurs when doing
> echo 0 > /proc/sys/kernel/nmi_watchdog
>
> Call Trace:
> [] single_msr_unreserve+0xd/0x1a
> [] disable_lapic_nmi_watchdog+0x27/0x35
> []
On Friday 08 June 2007, Alan Cox wrote:
> On Fri, 8 Jun 2007 14:18:55 +0200
> Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
>
> > On Monday 04 June 2007, Jiri Slaby wrote:
> > > ide-generic, add another device exception
> >
> > ide-generic is a generic ISA IDE driver, this one is
Add x86-optimized implementation of the SHA-1 hash function, taken from
Nettle under the LGPL. This code will be enabled on kernels compiled for
486es or better; kernels which support 386es will use the generic
implementation (since we need BSWAP).
We disable building lib/sha1.o when an
Add optimized implementation of the SHA-1 hash function for x86_64, ported
from the x86 implementation in Nettle (which is LGPLed).
The code has been tested with tcrypt and the NIST test vectors.
Signed-off-by: Benjamin Gilbert <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/x8664_ksyms.c |3
Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
---
Index: linux/include/linux/kernel.h
===
--- linux.orig/include/linux/kernel.h
+++ linux/include/linux/kernel.h
@@ -228,11 +228,18 @@ extern void print_hex_dump(const char *l
/* If
This patch series replaces DPRINTK with pr_debug in alternative.c,
autofs, autofs4
and ncpfs. A new function called pr_err is also added to keep
functionality in
ncpfs. The last 2 patches add support for pr_debug_pid and apply it to
autofs4 to
keep the output the same as the current DPRINTK
The following 3-part series adds assembly implementations of the SHA-1
transform for x86 and x86_64. For x86_64 the optimized code is always
selected; on x86 it is selected if the kernel is compiled for i486 or above
(since the code needs BSWAP). These changes primarily improve the
performance
Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
---
-/* #define DEBUG */
-
-#ifdef DEBUG
-#define DPRINTK(fmt,args...) do { pr_debug("pid %d: %s: " fmt "\n" ,
current->pid , __FUNCTION__ , ##args); } while(0)
-#else
-#define DPRINTK(fmt,args...) do {} while(0)
-#endif
-
/* Unified info structure.
Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
---
+static inline int __attribute__ ((format (printf, 1, 2)))
pr_debug_pid(const char * fmt, ...)
+{
+ return 0;
+}
+
static inline int __attribute__ ((format (printf, 1, 2))) pr_err(const
char * fmt, ...)
{
return 0;
--
-
To
Signed-off-by: Jack Stone <[EMAIL PROTECTED]>
---
- DDPRINTK("ncp_lookup_validate: %s/%s not valid, age=%ld, server
lookup\n",
+ pr_debug("ncp_lookup_validate: %s/%s not valid, age=%ld, server
lookup\n",
dentry->d_parent->d_name.name, dentry->d_name.name,
> > Unproven and dubious at best as a claim.
>
> I really don't mean to be rude and pointing you to read the archives, but
> the proof and the reason why claims are valid is inside there.
I've read the archive. I'm totally unconvinced by any of the fd
allocation policy stuff. There are some
On Fri, Jun 08, 2007 at 02:42:07PM -0700, Andrew Morton wrote:
> I'd say just remove the whole thing and use kmem_cache_alloc().
We will try that.
> Put much effort into removing the GFP_ATOMIC and using GFP_NOIO instead:
> there's your problem right there.
As these are called from interrupt
Alan Stern wrote:
Robert, it would help somewhat if you could build a kernel with
CONFIG_USB_DEBUG turned on and post the dmesg log showing what happens
when you plug in one of those non-working devices.
Sorry, yes I should have done that before...
Yes, in principle Linux can be made to
Andrew Morton wrote:
Put much effort into removing the GFP_ATOMIC and using GFP_NOIO instead:
there's your problem right there.
If for some reason you really can't do that (and a requirement for
allocation-in-interrupt is the only valid reason, really)
and that's the case here; IO gets
Hello, I'm using -ck since... along time ago (I start using it with the
kernel 2.6.16) . I started using it with Ubuntu and the response of the
system was better. Since that I always compile my kernels with -ck.
Actually I use 2.6.20-ck1 and I have no problems, even with things that
needs
Robert de Rooy wrote:
Mark Lord wrote:
I still don't see much evidence that interrupts are actually
functioning here.
It would be good to see /proc/interrupts before/after libata tries to
talk to it.
Let's assume for the moment that interrupts are b0rken.
The legacy IDE driver can talk to
Make sha_init() a static inline in cryptohash.h rather than an (unexported)
function in lib/sha1.c, in preparation for making sha1.c optional. This
also allows some cleanups:
- Modular code can now use sha_init() rather than reimplementing it
- The optimized implementation of SHA-1 for ARM no
Hi Matthieu.
Can you please try to tell what your patch actually does.
As for the part added in the MAkefile you pass -lintl for Cygwin -
but I fail to see _why_ -lintl is needed.
The patch to check-lxdialog.sh is outdated.
Could I ask you to redo it againt latest version and again explains
the
Mark Lord wrote:
I still don't see much evidence that interrupts are actually
functioning here.
It would be good to see /proc/interrupts before/after libata tries to
talk to it.
Let's assume for the moment that interrupts are b0rken.
The legacy IDE driver can talk to such devices completely
On Wednesday 06 June 2007 15:26, Stephen Smalley wrote:
> On Mon, 2007-06-04 at 23:03 +0200, Andreas Gruenbacher wrote:
> > [...] SELinux turns pathnames into labels when it
> > initially labels all files (when a policy is rolled out), whereas
> > AppArmor computes the "label" of each file when a
On Fri, 8 Jun 2007, Alan Cox wrote:
> > > #1: Throw the whole thing away and accept its not a good idea anyway
> >
> > Unfortunately (exactly because of the same guarantees you're asking for
> > those handles), in order for userspace libraries to reliably internally
> > use fds to interact
1 - 100 of 1183 matches
Mail list logo
