Hello,
since I switched to kernel 2.6.22 my dell 1750 server
with the two onboard BCM5704 network interfaces doesn't
work properly anymore.
TCP requests sometimes need more than 30 seconds to be answered
(or to get away) and the application stops with timeouts.
We are talking about two servers con
>From Ken Sugawara <[EMAIL PROTECTED]>
Description: Add an option to softdog to panic upon timer expiration
instead of reboot.
Signed-off-by: Ken Sugawara <[EMAIL PROTECTED]>
---
This patch is intended to help increase the chance of postmortem
analysis in the event of silent system hang where i
From: John Zaitseff <[EMAIL PROTECTED]>
The following patch to Linux kernel 2.6.23 enables most of the
extra keys found on the Microsoft Natural Ergonomic 4000 USB
keyboard. I had to add one keycode to include/linux/input.h; feel
free to reallocate the ID assigned to it (KEY_SPELL).
Main changes
On Wednesday 10 October 2007 04:24:24 Jeremy Fitzhardinge wrote:
> [ I think this is a straight repost this patch, which addresses all the
> previous comments. I'd like to submit this for .24 as the basis for a
> unified paravirt_ops. Any objections? ]
Thanks Jeremy, I've actually taken time to
Am Dienstag 09 Oktober 2007 schrieb Lennart Sorensen:
> Now if you were trying to transfer a lot of data to the laptop, would it
> be more power efficient to do it at gigabit speeds so you can finish
> sooner and shut down the machine entirely, or to slow to 100mbit and
> take longer to do it, and
>
> The kernel really cannot sustain 125MB/s? I assume the disk
> array is capable?
Yes, the array should be capable, LSI controller U320, SATA disks inside
the array.
> Where is the bottleneck? Does it keep all disks busy, or are
> the CPUs overloaded?
I'm not sure where the bottleneck is. C
Hi All,
I pulled the latest 2.6.23 changes to my local git repository and
compiled a fresh kernel.
The kernel boots fine but seem to be waiting for root filesystem.
The system is very much responsive at this stage, capslock, numlock
etc keys work. Alt+ctrl+del reboots the system fine.
My system i
On Tue, 2007-10-09 at 13:54 -0700, Linus Torvalds wrote:
> Finally.
>
> Yeah, it got delayed, not because of any huge issues, but because of
> various bugfixes trickling in and causing me to reset my "release clock"
> all the time. But it's out there now, and hopefully better for the wait.
>
>
Jim Gifford wrote:
Here's the situation. I have a MSI KN8Neo-f motherboard with a Seagate
Barracuda 250 GB SATA drive. I have replaced this drive three times in
the last two weeks due to it failing. Now the only thing in common is
the use of a 2.6.22.9 kernel I built from scratch, before that I
Gustavo Chain wrote:
El Wed, 10 Oct 2007 11:19:27 +0930
David Newall <[EMAIL PROTECTED]> escribió:
Gustavo Chain wrote:
I think it's necessary to reserve some pids to the super user.
5 must be sufficient.
Why? (Sorry if I missed something.)
¿ To prevent a posible DoS ?
On Wed, Oct 10, 2007 at 02:10:13AM +0530, chandru wrote:
> kdump kernel fails to boot with calgary iommu and aacraid driver on a
> x366 box. The ongoing dma's of aacraid from the first kernel continue
> to exist until the driver is loaded in the kdump kernel. Calgary is
> initialized prior to aacr
On Wed, 10 Oct 2007, Thomas Gleixner wrote:
>
> Fair enough. OTOH for the affected PPC users it's a regression and that's
> what I'm concerned of.
Hmm.. I just got the appended (Kevin, better not just send me email, other
people can be interested too):
From: Kevin <[EMAIL PROTECTED]>:
Subjec
On Tue, Oct 09, 2007 at 11:06:23PM +0200, Muli Ben-Yehuda wrote:
> Hi Chandru,
>
> Thanks for the patch. Comments on the patch below, but first a general
> question for my education: the main problem here that aacraid
> continues DMA'ing when it shouldn't. Why can't we shut it down
> cleanly? Even
On Wed, 10 Oct 2007, Hugh Dickins wrote:
> On Tue, 9 Oct 2007, Nick Piggin wrote:
> > by it ;) To prove my point: the *first* approach I posted to fix this
> > problem was exactly a patch to special-case the zero_page refcounting
> > which was removed with my PageReserved patch. Neither Hugh nor
El Wed, 10 Oct 2007 11:19:27 +0930
David Newall <[EMAIL PROTECTED]> escribió:
> Gustavo Chain wrote:
> > I think it's necessary to reserve some pids to the super user.
> > 5 must be sufficient.
>
> Why? (Sorry if I missed something.)
To prevent a posible DoS ?
>
> Shouldn't you test for error
On Tuesday 09 October 2007 20:01, Robert Hancock wrote:
> Some people with certain Supermicro boards (at least the H8DCE, it
> seems) have reported that the sata_nv driver fails to attach to some of
> the controllers due to resource conflicts:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2806
On Wed, Oct 10, 2007 at 09:39:44AM +0800, wit wrote:
> Hi,
> I found these routines in the kernel, does this means only one driver
> can be matched to a device?
Yes, you are correct, that is how the driver model currently works.
> What if two drivers both can drive the device, like sd & sg in scs
From: David Miller <[EMAIL PROTECTED]>
Date: Tue, 09 Oct 2007 15:00:40 -0700 (PDT)
> From: David Brownell <[EMAIL PROTECTED]>
> Date: Tue, 9 Oct 2007 14:43:54 -0700
>
> > Does it resolve the problem you observed?
>
> I will definitely give the patch a try and report back.
My tests look really g
On Tue, 9 Oct 2007, Nick Piggin wrote:
> by it ;) To prove my point: the *first* approach I posted to fix this
> problem was exactly a patch to special-case the zero_page refcounting
> which was removed with my PageReserved patch. Neither Hugh nor yourself
> liked it one bit!
True (speaking for me
Hi Linus,
Please pull from the repository at
git pull git://git.linux-nfs.org/pub/linux/nfs-2.6.git
This will update the following files through the appended changesets.
Cheers,
Trond
Documentation/kernel-parameters.txt |7 +
fs/Kconfig |8 +
fs/
Here's the situation. I have a MSI KN8Neo-f motherboard with a Seagate
Barracuda 250 GB SATA drive. I have replaced this drive three times in
the last two weeks due to it failing. Now the only thing in common is
the use of a 2.6.22.9 kernel I built from scratch, before that I was
using 2.6.19 k
Hi:
Here is the crypto update for 2.6.24:
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
or
master.kernel.org:/pub/scm/linux/kernel/git/herbert/crypto-2.6.git
Summary:
* Added SEED algorithm.
* Added XTS block cipher mode.
* Added new aead type (essenti
On Tue, 9 Oct 2007, Nick Piggin wrote:
>
> I gave 2 other numbers. After that, it really doesn't matter if I give
> you 2 numbers or 200, because it wouldn't change the fact that there
> are 3 programs using the ZERO_PAGE that we'll never know about.
You gave me no timings what-so-ever. Yes, yo
On Tuesday 09 October 2007 23:50, Michael Stiller wrote:
> Hi list,
>
> i'm developing an application (in C) which needs to write about
> 1Gbit/s (125Mb/s) to a disk array attached via U320 SCSI.
> It runs on Dual Core 2 Xeons @2Ghz utilizing kernel 2.6.22.7.
>
> I buffer the data in (currently 4)
On Wednesday 10 October 2007 12:22, Linus Torvalds wrote:
> On Tue, 9 Oct 2007, Nick Piggin wrote:
> > Where do you suggest I go from here? Is there any way I can
> > convince you to try it? Make it a config option? (just kidding)
>
> No, I'll take the damn patch, but quite frankly, I think your ar
On Wednesday 10 October 2007 11:26, Christoph Lameter wrote:
> On Tue, 9 Oct 2007, Nick Piggin wrote:
> > > We already use 32k stacks on IA64. So the memory argument fail there.
> >
> > I'm talking about generic code.
>
> The stack size is set in arch code not in generic code.
Generic code must as
Chris Rankin wrote:
> Hi,
>
> Do you remember that oops in sysfs a few versions ago? (Kernel bug 8198)
> Well, it's bck in
> 2.6.22.9...
This isn't really related to sysfs. It seems module count was too low
and went away while there still were holders. What were you doing when
it happened?
On Tue, 9 Oct 2007, Nick Piggin wrote:
>
> Where do you suggest I go from here? Is there any way I can
> convince you to try it? Make it a config option? (just kidding)
No, I'll take the damn patch, but quite frankly, I think your arguments
suck.
I've told you so before, and asked for numbers
On 10/9/07, Steven Rostedt <[EMAIL PROTECTED]> wrote:
> This has been complied tested (and no more ;-)
>
>
> The idea here is when we find a situation that we just scheduled in an
> RT task and we either pushed a lesser RT task away or more than one RT
> task was scheduled on this CPU before schedu
On Wednesday 10 October 2007 00:52, Linus Torvalds wrote:
> On Tue, 9 Oct 2007, Nick Piggin wrote:
> > I have done some tests which indicate a couple of very basic common tools
> > don't do much zero-page activity (ie. kbuild). And also combined with
> > some logical arguments to say that a "sane"
Appended patch fixes an oops while changing the vsyscall sysctl.
I am sure no one tested this code before integrating into mainline :(
BTW, using ioremap() in vsyscall_sysctl_change() to get the virtual
address of a kernel symbol sounds like an over kill.. I wonder if we
can define a simple __va_v
Gustavo Chain wrote:
I think it's necessary to reserve some pids to the super user.
5 must be sufficient.
Why? (Sorry if I missed something.)
Shouldn't you test for error return before the pid is allocated?
Otherwise, I think, you have to free it. Thus:
long do_fork(unsigned long clone_f
On Tue, Oct 09, 2007 at 04:46:46PM -0400, [EMAIL PROTECTED] wrote:
> On Tue, 09 Oct 2007 18:32:30 +0200, Oleg Verych said:
> > On Tue, Oct 09, 2007 at 06:06:05PM +0200, Joerg Roedel wrote:
> > > > cpu_has() returns int,
> > > > but would it be better to have something like
> > > >
> > > >
Hi,
I found these routines in the kernel, does this means only one driver
can be matched to a device? What if two drivers both can drive the
device, like sd & sg in scsi subsystem?
static int device_attach(struct device * dev)
{
struct bus_type * bus = dev->bus;
struct list_head *
On Tue, 9 Oct 2007, Nick Piggin wrote:
> > We already use 32k stacks on IA64. So the memory argument fail there.
>
> I'm talking about generic code.
The stack size is set in arch code not in generic code.
> > > The solution has until now always been to fix the problems so they don't
> > > use s
Hi Jiri,
Em Seg, 2007-10-08 às 13:41 +0100, Jiri Slaby escreveu:
> cinergyT2, remove bad usage of ERESTARTSYS
>
> test of cinergyt2->disconnect_pending doesn't ensure pending signal and so
> ERESTARTSYS would reach userspace, which is not permitted. Change it to
> EAGAIN
>
checkpatch.pl is comp
On Wednesday 10 October 2007 04:39, Christoph Lameter wrote:
> On Mon, 8 Oct 2007, Nick Piggin wrote:
> > The tight memory restrictions on stack usage do not come about because
> > of the difficulty in increasing the stack size :) It is because we want
> > to keep stack sizes small!
> >
> > Increas
Keep tx and rx elements separate on different cachelines to prevent
bouncing.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Cc: Stephen Hemminger <[EMAIL PROTECTED]>
Cc: Christoph Hellwig <[EMAIL PROTECTED]>
---
drivers/net/xen-netfront.c | 37 ++---
1
This patch removes some residual dead code left over from removing the
"flip" receive mode. This patch doesn't change the generated output
at all, since gcc already realized it was dead.
This resolves the "regression" reported by Adrian.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Cc:
struct net_device has its own stats structure, so use that instead.
Also, we can use the default get_stats function.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Cc: Stephen Hemminger <[EMAIL PROTECTED]>
Cc: Rusty Russell <[EMAIL PROTECTED]>
---
drivers/net/xen-netfront.c | 25 +++
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Tue, 9 Oct 2007 21:03:26 -0400
>
> Please pull from the 'upstream-davem' branch of
> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
> upstream-davem
>
> to receive these changes:
Pulled and pushed back out, thanks Jeff!
-
To unsub
Jeff Garzik wrote:
> ACK but does not apply to jgarzik/netdev-2.6.git#upstream nor
> davem/net-2.6.24.git
OK, looks like you don't have the other two patches. Will post in a sec.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL P
Huang, Ying wrote:
On Tue, 2007-10-09 at 12:23 -0700, H. Peter Anvin wrote:
Huang, Ying wrote:
- Which fields of boot parameters should be exported directly in
sysfs? Export all fields of boot parameters in sysfs is too complex
and unnecessary. Which fields should be?
The main this is that
Jeff Garzik wrote:
> Jeremy Fitzhardinge wrote:
>> Keep tx and rx elements separate on different cachelines to prevent
>> bouncing.
>>
>> Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
>> Cc: Stephen Hemminger <[EMAIL PROTECTED]>
>> Cc: Christoph Hellwig <[EMAIL PROTECTED]>
>>
>> ---
>> dr
Please pull from the 'upstream-davem' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-davem
to receive these changes:
Auke Kok (2):
e1000e: Simple optimizations in e1000_xmit_frame
e1000e: restore flow control settings properly
Jan-Bernd Theman
On Tue, 2007-10-09 at 12:23 -0700, H. Peter Anvin wrote:
> Huang, Ying wrote:
> >
> > - Which fields of boot parameters should be exported directly in
> > sysfs? Export all fields of boot parameters in sysfs is too complex
> > and unnecessary. Which fields should be?
> >
>
> The main this is
On Tue, Oct 09, 2007 at 09:17:31PM +0200, Ingo Molnar wrote:
>
> * Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > No need to be more spagetti than absolutely necessary.
> >
> > Replace loops implemented with gotos with real loops. Replace err =
> > ...; goto x; x: return err; with return ...;
> >
Mark Brown wrote:
The natsemi driver has a define NATSEMI_TIMER_FREQ which looks like it
controls the normal frequency of the chip poll timer but in fact only
takes effect for the first run of the timer. Adjust the value of the
define to match that used by the timer and use the define consistent
Mark Brown wrote:
Unless we have failed to fill the RX ring the timer used by the natsemi
driver is not particularly urgent and can use round_jiffies() to allow
grouping with other timers.
Signed-off-by: Mark Brown <[EMAIL PROTECTED]>
---
drivers/net/natsemi.c | 10 +++---
1 files changed
Jeremy Fitzhardinge wrote:
Keep tx and rx elements separate on different cachelines to prevent
bouncing.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Cc: Stephen Hemminger <[EMAIL PROTECTED]>
Cc: Christoph Hellwig <[EMAIL PROTECTED]>
---
drivers/net/xen-netfront.c | 37
Jan-Bernd Themann wrote:
eHEA recovery and DLPAR functions are called seldomly. The eHEA workqueues
are replaced by the kernel event queue.
Signed-off-by: Jan-Bernd Themann <[EMAIL PROTECTED]>
---
The patch has been built against upstream git
drivers/net/ehea/ehea.h |3 +--
drivers/n
Don't allow cpu hotplug on systems lacking XICS interrupt controller,
since current code is hardcoded for it.
Signed-off-by: Olof Johansson <[EMAIL PROTECTED]>
---
On Wed, Oct 10, 2007 at 10:18:26AM +1000, Stephen Rothwell wrote:
> > + struct device_node *np;
> > + const char *typep;
> > +
acked-by: Luca Risolia <[EMAIL PROTECTED]>
On Monday 08 October 2007 14:40:53 Jiri Slaby wrote:
> zc0301, remove bad usage of ERESTARTSYS
>
> down_read_trylock can't be interrupted and so ERESTARTSYS would reach
> userspace, which is not permitted. Change it to EAGAIN
>
> Signed-off-by: Jiri Slab
acked-by: Luca Risolia <[EMAIL PROTECTED]>
On Monday 08 October 2007 14:40:13 Jiri Slaby wrote:
> w9968cf, remove bad usage of ERESTARTSYS
>
> down_read_trylock can't be interrupted and so ERESTARTSYS would reach
> userspace, which is not permitted. Change it to EAGAIN
>
> Signed-off-by: Jiri Slab
Hi Olof,
On Tue, 9 Oct 2007 19:08:15 -0500 Olof Johansson <[EMAIL PROTECTED]> wrote:
>
> Don't allow cpu hotplug on systems lacking XICS interrupt controller,
> since current platform code is hardcoded for it.
>
>
> Signed-off-by: Olof Johansson <[EMAIL PROTECTED]>
>
>
> diff --git a/arch/powe
On Wed, 10 Oct 2007 09:50:49 +1000 (EST) James Morris wrote:
> On Tue, 9 Oct 2007, Randy Dunlap wrote:
>
> > I doth protest. Enabling the entire NET subsystem thru a hidden
> > select is awful. Select should be used (sparingly) to enable
> > library code only. If someone wants NET enabled, the
On Tue, Oct 09, 2007 at 10:49:20AM -0600, Jonathan Corbet wrote:
> Neil Brown <[EMAIL PROTECTED]> wrote:
> > > + (b) Any problems, concerns, or questions relating to the patch have been
> > > + communicated back to the submitter. I am satisfied with how the
> > > + submitter has responded
Some people with certain Supermicro boards (at least the H8DCE, it
seems) have reported that the sata_nv driver fails to attach to some of
the controllers due to resource conflicts:
https://bugzilla.redhat.com/show_bug.cgi?id=280641
https://bugzilla.redhat.com/show_bug.cgi?id=313491
Essentiall
Don't allow cpu hotplug on systems lacking XICS interrupt controller,
since current platform code is hardcoded for it.
Signed-off-by: Olof Johansson <[EMAIL PROTECTED]>
diff --git a/arch/powerpc/platforms/pseries/hotplug-cpu.c
b/arch/powerpc/platforms/pseries/hotplug-cpu.c
index 9711eb0..e29b8
On Tue, Oct 09, 2007 at 04:27:06PM -0700, Linus Torvalds wrote:
>
>
> On Wed, 10 Oct 2007, Thomas Gleixner wrote:
> >
> > Wrapping it into a #ifdef CONFIG_X86 would be sufficient.
>
> Well, the ppc oops seems to be a ppc bug regardless.
>
> If CPU_HOTPLUG isn't defined, the thing does nothing.
On Tue, 9 Oct 2007, Randy Dunlap wrote:
> I doth protest. Enabling the entire NET subsystem thru a hidden
> select is awful. Select should be used (sparingly) to enable
> library code only. If someone wants NET enabled, they should
> enable it overtly, not covertly.
Ok, fair enough.
I've drop
I think it's necessary to reserve some pids to the super user.
5 must be sufficient.
Signed-off-by: Gustavo Chain <[EMAIL PROTECTED]>
---
kernel/fork.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index 33f12f4..db23cb3 100644
--- a/k
On Tue, Oct 09, 2007 at 03:43:20PM -0500, Mark Langsdorf wrote:
> This patch should apply cleanly to the 2.6.23-rc8-mm2 kernel. It changes
> the powernow-k8 driver code that deals with 3rd generation Opteron, Phenom,
> and later processors to match the architectual pstate driver described
> i
On Tue, 9 Oct 2007, Linus Torvalds wrote:
>
>
> On Wed, 10 Oct 2007, Thomas Gleixner wrote:
> >
> > Wrapping it into a #ifdef CONFIG_X86 would be sufficient.
>
> Well, the ppc oops seems to be a ppc bug regardless.
>
> If CPU_HOTPLUG isn't defined, the thing does nothing. And if it is
> defin
On Wed, 10 Oct 2007 09:19:55 +1000 (EST) James Morris wrote:
> From: Eric Paris <[EMAIL PROTECTED]>
>
> Changes the security/selinux/Kconfig to use select instead of depends
> for most of the SELinux requirements. This allows the SELinux option to
> show up when people do a make config without a
On Wed, Oct 10, 2007 at 01:21:18AM +0200, Thomas Gleixner wrote:
>
>
> On Tue, 9 Oct 2007, Greg KH wrote:
>
> > On Tue, Oct 09, 2007 at 10:17:02AM -0500, Olof Johansson wrote:
> > > On Mon, Oct 08, 2007 at 11:06:33AM -0700, Greg KH wrote:
> > > > From: Mark Lord <[EMAIL PROTECTED]>
> > > >
> >
On Wed, 10 Oct 2007, Thomas Gleixner wrote:
>
> Wrapping it into a #ifdef CONFIG_X86 would be sufficient.
Well, the ppc oops seems to be a ppc bug regardless.
If CPU_HOTPLUG isn't defined, the thing does nothing. And if it is
defined, I don't see why/how ppc can validly oops. So I think the f
On Sat, Oct 06, 2007 at 03:07:25AM -0400, Bernardo Innocenti wrote:
> From: Francesco Sacchi <[EMAIL PROTECTED]>
>
> Reading serial port status lines was broken on the FT232RL since when it
> has been detected as a separate chip (2.6.22+). Previously, it would work
> because it was just handled a
On Tue, Oct 09, 2007 at 04:20:39PM -0700, Roland Dreier wrote:
> > > - relaying implementation details to userspace so that they cannot be
> > > easily changed. We would need to allow kobjects not showing up in sysfs
> > > and making symlinks a sysfs facility not relying on kobjects to help
> >
From: KaiGai Kohei <[EMAIL PROTECTED]>
* We add ebitmap_for_each_positive_bit() which enables to walk on
any positive bit on the given ebitmap, to improve its performance
using common bit-operations defined in linux/bitops.h.
In the previous version, this logic was implemented using a combin
From: KaiGai Kohei <[EMAIL PROTECTED]>
This patch kills ugly warnings when the "Improve SELinux performance when
AVC misses" patch.
Signed-off-by: KaiGai Kohei <[EMAIL PROTECTED]>
Signed-off-by: James Morris <[EMAIL PROTECTED]>
---
security/selinux/ss/ebitmap.c | 11 +--
security/seli
On Tue, 9 Oct 2007, Greg KH wrote:
> On Tue, Oct 09, 2007 at 10:17:02AM -0500, Olof Johansson wrote:
> > On Mon, Oct 08, 2007 at 11:06:33AM -0700, Greg KH wrote:
> > > From: Mark Lord <[EMAIL PROTECTED]>
> > >
> > > commit 4047727e5ae33f9b8d2b7766d1994ea6e5ec2991 from upstream
> > >
> > > We n
From: Eric Paris <[EMAIL PROTECTED]>
Allow policy to select, in much the same way as it selects MLS support, how
the kernel should handle access decisions which contain either unknown
classes or unknown permissions in known classes. The three choices for the
policy flags are
0 - Deny unknown sec
From: Yuichi Nakamura <[EMAIL PROTECTED]>
It reduces the selinux overhead on read/write by only revalidating
permissions in selinux_file_permission if the task or inode labels have
changed or the policy has changed since the open-time check. A new LSM
hook, security_dentry_open, is added to captu
From: Eric Paris <[EMAIL PROTECTED]>
Changes the security/selinux/Kconfig to use select instead of depends
for most of the SELinux requirements. This allows the SELinux option to
show up when people do a make config without already knowing they had to
enable audit and other non-obvious choices.
From: Yuichi Nakamura <[EMAIL PROTECTED]>
This patch reduces memory usage of SELinux by tuning avtab. Number of hash
slots in avtab was 32768. Unused slots used memory when number of rules is
fewer. This patch decides number of hash slots dynamically based on number
of rules. (chain length)^2 is a
> > - relaying implementation details to userspace so that they cannot be
> > easily changed. We would need to allow kobjects not showing up in sysfs
> > and making symlinks a sysfs facility not relying on kobjects to help
> > there.
>
> Huh? Why would you want a kobject to not show up in s
Please pull.
The following changes since commit bbf25010f1a6b761914430f5fca081ec8c7accd1:
Linus Torvalds (1):
Linux 2.6.23
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-2.6.git
for-linus
Eric Paris (2):
SELinux: change
On Tue, 9 Oct 2007 18:13:55 -0400 Matt LaPlante wrote:
> Most of these fixes were already submitted for old kernel versions, and were
> approved, but for some reason they never made it into the releases. I've
> updated the changes for the 2.6.23 kernel and attached the resulting patch.
> Beca
On Fri, Oct 05, 2007 at 06:44:04AM -0600, Eric W. Biederman wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
>
> > I would be interested in seeing what your patches look like.
>
> Sure.
>
> > I don't
> > think that we should take any more sysfs changes for 2.6.24 as we do
> > have a lot of them rig
On Tue, Oct 09, 2007 at 10:17:02AM -0500, Olof Johansson wrote:
> On Mon, Oct 08, 2007 at 11:06:33AM -0700, Greg KH wrote:
> > From: Mark Lord <[EMAIL PROTECTED]>
> >
> > commit 4047727e5ae33f9b8d2b7766d1994ea6e5ec2991 from upstream
> >
> > We need to disable all CPUs other than the boot CPU (usu
On Fri, Oct 05, 2007 at 05:00:48PM +0900, Tejun Heo wrote:
> Hello, Greg.
>
> I think this definitely needs more discussion, so here we go...
heh :)
> Greg KH wrote:
> >> 1. What is a kobject?
> [--snip--]
> >> The functionality served by kobject can be broken down into the
> >> following two.
>
On Fri, Oct 05, 2007 at 06:12:41AM -0600, Eric W. Biederman wrote:
> Greg KH <[EMAIL PROTECTED]> writes:
> >
> >> Also fun is that the dev file implementation needs to be able to
> >> report different major:minor numbers based on which mount of
> >> sysfs we are dealing with.
> >
> > Um, no,
On Tue, Oct 09, 2007 at 11:29:01AM +0200, Cornelia Huck wrote:
> On Fri, 05 Oct 2007 17:00:48 +0900,
> Tejun Heo <[EMAIL PROTECTED]> wrote:
>
> > I think this definitely needs more discussion, so here we go...
>
> I agree, so I'll give my 0.02 ? here...
> >
> > Greg KH wrote:
> > >> 1. What is a
Current TPM driver supports only locality 0. I am planning to add
support so that it can access any locality. Locality parameter will be
passed as parameter. Will this change be acceptable? If yes then I will
modify the driver and send the patch.
Thanks,
Lomesh
-
To unsubscribe from this list: sen
Unless we have failed to fill the RX ring the timer used by the natsemi
driver is not particularly urgent and can use round_jiffies() to allow
grouping with other timers.
Signed-off-by: Mark Brown <[EMAIL PROTECTED]>
---
drivers/net/natsemi.c | 10 +++---
1 files changed, 7 insertions(+), 3
The natsemi driver has a define NATSEMI_TIMER_FREQ which looks like it
controls the normal frequency of the chip poll timer but in fact only
takes effect for the first run of the timer. Adjust the value of the
define to match that used by the timer and use the define consistently.
Signed-off-by:
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> but the gist is that IBM has
> traditionally bit 0 for MSB and x for LSB. It's a pain to work with:
> for one, bits in the same place in a word (say, control register) are
> renumbered in 32 vs 64.
I wasn't aware of that, but it doesn't really ch
On Tuesday 09 October 2007 8:03:15 am Ahmed S. Darwish wrote:
> $ man getcwd
>
> char *getcwd(char *buf, size_t size);
>
> As an extension to the POSIX.1 standard, Linux (libc4, libc5, glibc)
> getcwd() allocates the buffer dynamically using malloc() if buf is NULL on
> call.
>
> Shouldn't "srctr
Timur Tabi <[EMAIL PROTECTED]> writes:
> I think when the PowerPC is running in little-endian mode, that might
> be the case. It needs to be able to write a byte in big-endian mode,
> and then read that byte back in little-endian mode and have it be the
> same byte.
But this is exactly what excl
On Tue 09 Oct at 13:14:49 +0200 [EMAIL PROTECTED] said:
> FWIW I had to do Tim's bits too. Just moving all output from the start
> into the show method didn't fix it.
Yes. The way the original lockdep_proc.c code was doing its pointers
around its seq data was definitely wrong, regardless of the o
Roel Kluin <[EMAIL PROTECTED]> found a minor defect in the init code if
hwmon device registration fails.
Signed-off-by: Darrick J. Wong <[EMAIL PROTECTED]>
---
drivers/hwmon/ibmpex.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/hwmon/ibmpex.c b/drivers/hwmon
On Tue, Oct 09, 2007 at 08:33:59PM +0200, Philipp Matthias Hahn wrote:
> Hello!
>
> On Tue, Oct 09, 2007 at 02:40:35PM +0200, Ahmed S. Darwish wrote:
> > On Tue, Oct 09, 2007 at 01:55:42AM +0400, Dmitri Vorobiev wrote:
> > > The patch below contains a small code clean-up for the NTFS driver: all
>
From: David Brownell <[EMAIL PROTECTED]>
Date: Tue, 9 Oct 2007 14:43:54 -0700
> Does it resolve the problem you observed?
I will definitely give the patch a try and report back.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Tuesday 09 October 2007, David Miller wrote:
> Are we sure that this is the only event that causes the conflicts between
> the EHCI and it's companion virtual OHCI/UHCI host(s)?
It's the event which can cause trouble when EHCI starts up
after OHCI/UHCI (rather than before it).
The other event
Krzysztof Halasa wrote:
> Some pointer maybe?
>
Erm, a bit of googling will turn one up, but the gist is that IBM has
traditionally bit 0 for MSB and x for LSB. It's a pain to work with:
for one, bits in the same place in a word (say, control register) are
renumbered in 32 vs 64. And I've wor
On Tue, 9 Oct 2007, Nick Piggin wrote:
>
> The commit b5810039a54e5babf428e9a1e89fc1940fabff11 contains the note
>
> A last caveat: the ZERO_PAGE is now refcounted and managed with rmap
> (and thus mapcounted and count towards shared rss). These writes to
> the struct page could cause exce
On Tue, Oct 09, 2007 at 04:50:47PM -0400, Steven Rostedt wrote:
> > I did something like this a while ago for another scheduling project.
> > A couple 'possible' optimizations to think about are:
> > 1) Only scan the remote runqueues once and keep a local copy of the
> >remote priorities for su
I tried something useful with this, see below.
Jan Engelhardt wrote:
On Oct 9 2007 07:12, Antonino A. Daplas wrote:
References: http://lkml.org/lkml/2007/4/1/162
http://lkml.org/lkml/2007/10/5/199
This is quite a long thread :-)
It was a patch series after all. But as Greg puts it, b
From: Alan Stern <[EMAIL PROTECTED]>
Date: Tue, 9 Oct 2007 14:42:34 -0400 (EDT)
> On Tue, 9 Oct 2007, Greg KH wrote:
>
> > > Anyway, it certainly would be easy enough to make port resets mutually
> > > exclusive with EHCI initialization. That would work on any platform,
> > > PCI or not.
> >
>
1 - 100 of 301 matches
Mail list logo
