[EMAIL PROTECTED] wrote:
The patch titled
git-netdev-all: e1000 fix
has been added to the -mm tree. Its filename is
git-netdev-all-e1000-fix.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
Andrew Morton wrote:
On Tue, 09 Jan 2007 09:36:29 -0800
Auke Kok <[EMAIL PROTECTED]> wrote:
git-pull git://lost.foo-projects.org/~ahkok/git/linux-2.6 e1000
That tree appears to be based on the -mm git tree?
That's a somewhat unusual thing to do - a tree which is based on current
Linus
Provide an option to provide a view of the encrypted files such that
the metadata is always in the header of the files, regardless of
whether the metadata is actually in the header or in the extended
attribute. This mode of operation is useful for applications like
incremental backup utilities
Generalize the metadata reading and writing mechanisms, with two
targets for now: metadata in file header and metadata in the
user.ecryptfs xattr of the lower file.
Signed-off-by: Michael Halcrow <[EMAIL PROTECTED]>
---
fs/ecryptfs/crypto.c | 224
On Jan 9 2007 11:41, Shaya Potter wrote:
>
>Again, what about fibre channel support? Imagine I have multiple blades
>connected to a SAN. For whatever reason I format the san w/ ext3 (I've
>actually done this when we didn't need sharing, just needed a huge disk,
>for instance for doing
Add extended attribute support to version bit vector, flags to
indicate when xattr or encrypted view modes are enabled, and support
for the new mount options.
Signed-off-by: Michael Halcrow <[EMAIL PROTECTED]>
---
fs/ecryptfs/crypto.c | 20
This patch set introduces the ability to store cryptographic metadata
into an lower file extended attribute rather than the lower file
header region.
This patch set implements two new mount options:
ecryptfs_xattr_metadata
- When set, newly created files will have their cryptographic
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 includes the small patches from my previous
When I try to use oprofile on 2.6.19, it does not seem to work:
[EMAIL PROTECTED] tmp]$ sudo opcontrol --no-vmlinux
[EMAIL PROTECTED] tmp]$ sudo opcontrol --start
/usr/bin/opcontrol: line 911: /dev/oprofile/0/enabled: No such file or directory/usr/bin/opcontrol: line 911:
-Original Message-
From: Tobias Diedrich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 2:01 PM
To: Eric W. Biederman
Cc: Linus Torvalds; Lu, Yinghai; Andrew Morton; Adrian Bunk; Andi Kleen;
Linux Kernel Mailing List
Subject: Re: [PATCH 4/4] x86_64 ioapic: Improve the
On Tue, 9 Jan 2007 17:06:16 -0500
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> * Andrew Morton ([EMAIL PROTECTED]) wrote:
> > On Mon, 8 Jan 2007 22:14:46 -0500
> > Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> >
> > > +* How to use local atomic operations
> > > +
> > > +#include
> > >
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Mon, 8 Jan 2007 22:14:46 -0500
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>
> > +* How to use local atomic operations
> > +
> > +#include
> > +#include
> > +
> > +static DEFINE_PER_CPU(local_t, counters) = LOCAL_INIT(0);
> > +
> > +
> > +*
Thanks, applied.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Tue, 9 Jan 2007 12:01:21 +0100
Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Tuesday 09 January 2007 03:55, Adrian Bunk wrote:
> > RESTORE_CONTEXT lost a newline in
> > commit 658fdbef66e5e9be79b457edc2cbbb3add840aa9:
> >
> These machines are running a 2.6.9-42 RHEL4 kernel with the
> powernow-k8 module loaded - which I believe have backported
> cpufreq support from more recent mainline kernels.
To an extent. The problem is not the powernow-k8 driver,
but the cpufreq infrastructure. See below.
> In trying to
Eric W. Biederman wrote:
> Tobias. I don't have a box with the problem yours does, and this
> doesn't quite try any of the cases you have been asked to test
> so could you please test this one?
Works fine with BIOS 0402.
patches/series:
patch-2.6.20-rc4
patch-2.6.19-rc3-nokmem
myconfig
ccache
> > Here is a simple patch that does it.
>
> Looks more likely to work than Ken's - which I didn't try,
> but I couldn't see what magic prevented it from just going BUG.
>
> But I have to say, having seen the ensuing requests for this
> to impose the same constraints as other implementations
Jean Delvare <[EMAIL PROTECTED]> ha scritto:
> Hi all,
Hi Jean,
> Since 2.6.20-rc1 or so, running "make" always builds a new kernel with
> an incremented version number, whether there has actually been any
> change done to the code or configuration or not. This increases the
> build time quite a
Jeff V. Merkey wrote:
Jeff V. Merkey wrote:
root=/dev/hda2 is what was passed to the kernel from grub.
Jeff
I just finished pulling out a melted IDE flash drive out of a Shuttle
motherboard with the intel 945 chipset which claims to support
SATA and IDE drives concurrently under Linux
[EMAIL PROTECTED] wrote on 01/09/2007 02:27:19 PM:
>Which, unfortunately, creates incredibly brittle code when some attacker
>reads the SLIM source code and finds a way to force the non-simple case
>you ignore.
>
>This is an area where you really need to do it *right*, or not at all.
For the
On Tue, 9 Jan 2007 21:44:21 +0100
Jean Delvare <[EMAIL PROTECTED]> wrote:
> So, Linus, Andrew, can you please take a look and revert or fix what
> needs to be?
Am afraid to touch it. Sam should be back on deck soon and will hopefully
have time to fix this stuff up.
> This new behavior of the
Arjan van de Ven <[EMAIL PROTECTED]> wrote on 01/08/2007 10:07:25 PM:
> Hi,
>
>maybe this is a silly question, but do you revoke not only the current
>fd entries, but also the ones that are pending in UNIX domain sockets
>and that are already being sent to the process? If not.. then you might
Roland Dreier wrote:
I'm running a 64-bit Fedora 6 install as a guest on a host running
2.6.20-rc4 with the kvm-10 userspace release. The CPU is a Xeon 5160
and I have 6 GB of RAM. The guest is given 512 MB of memory. I left
the guest idle overnight, and the makewhatis cron job seems to have
Hi,
Sascha Sommer, le Sun 07 Jan 2007 00:32:26 +0100, a écrit :
> Attached is a very experimental driver for a Ricoh SD Card reader that can be
> found in some notebooks like the Samsung P35.
Yehaaaw! That reader can be found on DELL X300 too. It works almost fine
for me, see attached dmesg.
Jeff V. Merkey wrote:
root=/dev/hda2 is what was passed to the kernel from grub.
Jeff
I just finished pulling out a melted IDE flash drive out of a Shuttle
motherboard with the intel 945 chipset which claims to support
SATA and IDE drives concurrently under Linux 2.6.18.
The chip worked
If there is no problem with Linux gaming I should shut the hell up and
start buying all these Linux games I keep hearing about and seeing in
those TV commercials.
I feel that you are getting confused Linux = linux (kernel)? This
effort is pretty much lies with the distro guys. I have played
Sergey Vlasov wrote:
Yep.
Hello!
I have encountered a deadlock in the NTFS filesystem on a
2.6.18.6-based kernel (x86_64, CONFIG_SMP set, but the machine has
only one CPU (Athlon64 3200+), no PREEMPT).
The kswapd0 and mklocatedb processes were apparently involved in the
deadlock:
kswapd0
I just finished pulling out a melted IDE flash drive out of a Shuttle
motherboard with the intel 945 chipset which claims to support
SATA and IDE drives concurrently under Linux 2.6.18.
The chip worked for about 30 seconds before liquifying in the chassis.
I note that the 945 chipset in the
On Tue, Jan 09, 2007 at 09:50:20PM +0100, Maciej Rutecki wrote:
> Frederik Deweerdt napisał(a):
>
> > See:
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/hot-fixes/
> > This should fix it.
> > Regards,
> > Frederik
> >>
>
> I don't use reiser4 or
I got the oops after some hotplug events. And the similar oops can
reproduce by the following step.
plug usb-storage (e.g. scsi_host of usb is "host5", and device is sde)
# mount /dev/sde1 /mnt
# echo 1 > /sys/block/sde/device/delete
# echo - - - > /sys/class/scsi_host/host5/scan
#
On 1/9/07, Jesper Juhl <[EMAIL PROTECTED]> wrote:
Depends on what you want to do. If you want a stable kernel to use in
production you should probably pick the latest stable kernel
I am a Linux user/developer in all my IT career which began in 1997.
But always my goal to be a kernel developer
On Mon, 8 Jan 2007 22:14:46 -0500
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> +* How to use local atomic operations
> +
> +#include
> +#include
> +
> +static DEFINE_PER_CPU(local_t, counters) = LOCAL_INIT(0);
> +
> +
> +* Counting
> +
> +In preemptible context, use get_cpu_var() and
* Christoph Hellwig ([EMAIL PROTECTED]) wrote:
> On Mon, Jan 08, 2007 at 07:07:25PM -0800, Arjan van de Ven wrote:
> > maybe this is a silly question, but do you revoke not only the current
> > fd entries, but also the ones that are pending in UNIX domain sockets
> > and that are already being
Hello!
I have encountered a deadlock in the NTFS filesystem on a
2.6.18.6-based kernel (x86_64, CONFIG_SMP set, but the machine has
only one CPU (Athlon64 3200+), no PREEMPT).
The kswapd0 and mklocatedb processes were apparently involved in the
deadlock:
kswapd0 D 810005dea304 0
Frederik Deweerdt napisał(a):
> See:
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/hot-fixes/
> This should fix it.
> Regards,
> Frederik
>>
I don't use reiser4 or cpufreq, see my .config.
--
Maciej Rutecki <[EMAIL PROTECTED]>
http://www.unixy.pl
On Mon, 8 Jan 2007, Hua Zhong wrote:
> A while ago there was a discussion about supporting direct-io on tmpfs.
Ah, I think I can just about remember that... ;)
>
> Here is a simple patch that does it.
Looks more likely to work than Ken's - which I didn't try,
but I couldn't see what magic
Hi Andrey,
On Tue, 09 Jan 2007 20:05:49 +0300, Andrey Borzenkov wrote:
> Jean Delvare wrote:
> > Since 2.6.20-rc1 or so, running "make" always builds a new kernel with
> > an incremented version number, whether there has actually been any
> > change done to the code or configuration or not. This
Hi!
> Explain a couple of the most common errors in kernel-doc usage.
>
> Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
>
> ---
>
> seems useful to emphasize these issues since they occur occasionally
> in the source.
>
> diff --git a/Documentation/kernel-doc-nano-HOWTO.txt
>
On Tue, Jan 09, 2007 at 09:58:19AM -0800, Linus Torvalds wrote:
>
>
> On Tue, 9 Jan 2007, Adrian Bunk wrote:
> >
> > Subject : BUG: at mm/truncate.c:60 cancel_dirty_page() (reiserfs)
> > References : http://lkml.org/lkml/2007/1/7/117
> > Submitter : Malte Schröder <[EMAIL PROTECTED]>
> >
linux-os (Dick Johnson) wrote:
> On Tue, 9 Jan 2007, Stefan Richter wrote:
>> The limitations are certainly highly compiler-specific.
>
> I don't think so.
I referred to the ({ expr; }) in this remark, not to do-while. It's not
a valid construct in many flavors of the C language in the first
On Tue, 9 Jan 2007, Frank van Maarseveen wrote:
>
> Yes but "cp -rl" is typically done by _developers_ and they tend to
> have a better understanding of this (uh, at least within linux context
> I hope so).
>
> Also, just adding hard-links doesn't increase the number of inodes.
No, but it
On Tue, Jan 09, 2007 at 11:26:25AM -0500, Steven Rostedt wrote:
> On Mon, 2007-01-08 at 13:00 +0100, Miklos Szeredi wrote:
>
> > > 50% probability of false positive on 4G files seems like very ugly
> > > design problem to me.
> >
> > 4 billion files, each with more than one link is pretty far
Randy Dunlap wrote:
On Tue, 09 Jan 2007 20:16:27 +0100 Krzysztof Halasa wrote:
Auke Kok <[EMAIL PROTECTED]> writes:
drivers/net/e1000/Makefile| 19
drivers/net/e1000/e1000.h | 95
drivers/net/e1000/e1000_80003es2lan.c | 1330 +
>
> In the interest of expediting this I'll go implement it...
>
> Steve.
>
Here it is. I think this is the correct way to solve the issue (now
that I've implemented it :). This is a delta from the driver patch
series just for reviewing purposes.
commit
Hi,
I'm having a really ugly problem I'm trying to pinpoint, but failed so
far. I'm neither completely convinced it is not related to my local
setup(s), nor do I have any clue how this might be caused.
I have several boxes with native IPv6 connectivity at various places.
Some of them show
If assigned minor is 10 or greater, terminator will be put beyound the end.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
drivers/media/video/cpia.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
--- a/drivers/media/video/cpia.c
+++ b/drivers/media/video/cpia.c
@@
On Mon, 08 Jan 2007 17:38:25 EST, Mimi Zohar said:
> revoked. Based on previous comments on lkml, we understand
> that this is not really possible in general, so SLIM only
> attempts to revoke access in certain simple cases.
Which, unfortunately, creates incredibly brittle code when some
On Tue, 09 Jan 2007 20:16:27 +0100 Krzysztof Halasa wrote:
> Auke Kok <[EMAIL PROTECTED]> writes:
>
> > drivers/net/e1000/Makefile| 19
> > drivers/net/e1000/e1000.h | 95
> > drivers/net/e1000/e1000_80003es2lan.c | 1330 +
> >
Change i386 nmi handler to handle 32 bit perfmon counter MSR writes cleanly.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.20-rc-mm/arch/i386/kernel/nmi.c
===
---
Handle these 32 bit perfmon counter MSR writes cleanly in oprofile.
Signed-off-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Index: linux-2.6.20-rc-mm/arch/i386/oprofile/op_model_ppro.c
===
---
On Tue, 9 Jan 2007, Stefan Richter wrote:
> Robert P. J. Day wrote:
>> just to stir the pot a bit regarding the discussion of the two
>> different ways to define macros,
>
> You mean function-like macros, right?
>
>> i've just noticed that the "({ })"
>> notation is not universally acceptable.
On Tue, 9 Jan 2007 11:02:35 -0800 (PST) Amit Choudhary wrote:
>
> --- [EMAIL PROTECTED] wrote:
>
> > On Mon, 08 Jan 2007 01:06:12 PST, Amit Choudhary said:
> > > I do not see how a double free can result in _logical_wrong_behaviour_ of
> > > the program and the
> > > program keeps on running
P6 CPUs and Core/Core 2 CPUs which has 'architectural perf mon' feature,
only supports write of low 32 bits in Performance Monitoring Counters.
Bits 32..39 are sign extended based on bit 31 and bits 40..63 are reserved
and should be zero.
This patch:
Change x86_64 nmi handler to handle this
Auke Kok <[EMAIL PROTECTED]> writes:
> drivers/net/e1000/Makefile| 19
> drivers/net/e1000/e1000.h | 95
> drivers/net/e1000/e1000_80003es2lan.c | 1330 +
> drivers/net/e1000/e1000_80003es2lan.h | 89
> drivers/net/e1000/e1000_82540.c | 586 ++
>
Andrew Morton wrote:
On Tue, 09 Jan 2007 09:36:29 -0800
Auke Kok <[EMAIL PROTECTED]> wrote:
git-pull git://lost.foo-projects.org/~ahkok/git/linux-2.6 e1000
That tree appears to be based on the -mm git tree?
That's a somewhat unusual thing to do - a tree which is based on current
Linus
--- [EMAIL PROTECTED] wrote:
> On Mon, 08 Jan 2007 01:06:12 PST, Amit Choudhary said:
> > I do not see how a double free can result in _logical_wrong_behaviour_ of
> > the program and the
> > program keeps on running (like an incoming packet being dropped because of
> > double free).
> Double
Current mmconfig has some problems of remapped range. The base
address always corresponds to bus number 0, but currently we are
assuming it corresponds to start bus number.
This patch fixes the above problems.
Signed-off-by: OGAWA Hirofumi <[EMAIL PROTECTED]>
---
arch/x86_64/pci/mmconfig.c |
Currently, unreachable_devices() compares value of mmconfig and value
of conf1. But it doesn't check the device is reachable or not.
Signed-off-by: OGAWA Hirofumi <[EMAIL PROTECTED]>
---
arch/i386/pci/mmconfig-shared.c | 12 +++-
arch/i386/pci/mmconfig.c|6 ++
This rejects a broken MCFG tables on Asus etc.
Arjan and Andi suggest this.
Signed-off-by: OGAWA Hirofumi <[EMAIL PROTECTED]>
---
arch/i386/pci/mmconfig-shared.c | 24 +++-
arch/i386/pci/mmconfig.c|9 -
arch/x86_64/pci/mmconfig.c |9 -
This just cleans up.
Signed-off-by: OGAWA Hirofumi <[EMAIL PROTECTED]>
---
arch/i386/pci/mmconfig-shared.c | 50 +---
arch/i386/pci/mmconfig.c| 13 +++---
arch/i386/pci/pci.h |4 ++-
arch/x86_64/pci/mmconfig.c | 16
On Tue, 09 Jan 2007, Adrian Bunk wrote:
> > diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
> > index 1639998..34cc8d5 100644
> > --- a/drivers/acpi/Kconfig
> > +++ b/drivers/acpi/Kconfig
> > @@ -215,26 +215,29 @@ config ACPI_IBM
> > config ACPI_IBM_DOCK
> > bool "Legacy Docking
I have a number of dual CPU and dual CPU/dual core Opteron systems that
are used as compute servers. In an effort to reduce power consumption
and reduce heat output, I would like to make use of the PowerNow!
capabilities to clock back the CPUs when the machines are idle.
These machines are
Stephen Hemminger wrote:
On Tue, 09 Jan 2007 09:36:29 -0800
Auke Kok <[EMAIL PROTECTED]> wrote:
Andrew, All,
This patch contains a major rewrite to the e1000 driver that groups and separates e1000
hardware by chipset family. It abstracts the hardware specific code into an API that
will
On Tue, 09 Jan 2007 09:36:29 -0800
Auke Kok <[EMAIL PROTECTED]> wrote:
> git-pull git://lost.foo-projects.org/~ahkok/git/linux-2.6 e1000
That tree appears to be based on the -mm git tree?
That's a somewhat unusual thing to do - a tree which is based on current
Linus mainline would be
On Tue, 09 Jan 2007 09:36:29 -0800
Auke Kok <[EMAIL PROTECTED]> wrote:
>
> Andrew, All,
>
> This patch contains a major rewrite to the e1000 driver that groups and
> separates e1000
> hardware by chipset family. It abstracts the hardware specific code into an
> API that
> will allow us to
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Michael S. Tsirkin
> Sent: Tuesday, January 09, 2007 5:57 AM
> To: Steve Wise
> Cc: netdev@vger.kernel.org; Roland Dreier; Divy Le Ray;
> linux-kernel@vger.kernel.org; openib-general
> Subject:
On Tue, 09 Jan 2007 12:01:14 +0300
Dmitriy Monakhov <[EMAIL PROTECTED]> wrote:
> network pci drivers have to return correct error code during resume stage in
> case of errors.
> Signed-off-by: Dmitriy Monakhov <[EMAIL PROTECTED]>
> -
Please don't introduce one dev_err() call into a device
On Tue, 9 Jan 2007, Malte Schröder wrote:
>
> > So something interesting is definitely going on, but I don't know exactly
> > what it is. Why does reiserfs do the truncate as part of a close, if the
> > same inode is actually mapped somewhere else? And if it's a race with two
> > different
On Tue, 9 Jan 2007 14:54:01 +0100
"Bartlomiej Zolnierkiewicz" <[EMAIL PROTECTED]> wrote:
> The good news is that it doesn't matter now as Andrew fixed Conke's patches
> manually and applied them to -mm
I applied three pathces, but there's been such a storm of inadequately
changelogged mangled
In message <[EMAIL PROTECTED]>, "Raz Ben-Jehuda(caro)" writes:
> On 1/9/07, Erez Zadok <[EMAIL PROTECTED]> wrote:
> > In message <[EMAIL PROTECTED]>, Christoph Hellwig writes:
> > > On Mon, Jan 08, 2007 at 07:03:35PM -0500, Erez Zadok wrote:
> > > > However, I must caution that a file system like
Andrey Borzenkov schrieb:
John Clark wrote:
Then quite likely it remembered lower numbers for "old" interfaces and
starts renaming with next available.
The kernel is 2.6.19.1 the at-that-moment current linux kernel.
What should I look for in terms of interface renaming.
I
On Tue, 9 Jan 2007, Pekka J Enberg wrote:
> The current implementation of cache_grow() has to either (1) use pre-allocated
> memory for the slab or (2) allocate the memory itself which makes the error
> paths messy. Move __GFP_NO_GROW and __GFP_WAIT processing to kmem_getpages()
> and introduce a
Akula2 wrote:
> Should I start compile/test/debug one-after-one in this fashion:-
>
> 2.6.19 source + patch-2.6.20-rc1
> 2.6.19 source + patch-2.6.20-rc2
> 2.6.19 source + patch-2.6.20-rc3
> 2.6.19 source + patch-2.6.20-rc4
Or
linux-2.6.19 + testing/patch-2.6.20-rc1 = linux-2.6.20-rc1
On Tuesday 09 January 2007 18:58, Linus Torvalds wrote:
> On Tue, 9 Jan 2007, Adrian Bunk wrote:
> > Subject : BUG: at mm/truncate.c:60 cancel_dirty_page() (reiserfs)
> > References : http://lkml.org/lkml/2007/1/7/117
> > Submitter : Malte Schröder <[EMAIL PROTECTED]>
> > Status : unknown
>
>
On Tue, 2007-01-09 at 07:56 -0600, Dave Kleikamp wrote:
> On Tue, 2007-01-09 at 15:02 +0530, Srinivasa Ds wrote:
> > Tomasz Kvarsin wrote:
> > > This I got during boot with 2.6.20-rc4:
> > > =
> > > [ INFO: possible recursive locking detected ]
>
> ...
On Thu, Jan 04, 2007 at 07:53:07PM +0100, Adrian Bunk wrote:
> This option is already in arch/um/Kconfig.char
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
ACK, definitely.
Jeff
--
Work email - jdike at linux dot intel dot com
-
To unsubscribe from this list: send the
On 1/9/07, Erez Zadok <[EMAIL PROTECTED]> wrote:
In message <[EMAIL PROTECTED]>, Christoph Hellwig writes:
> On Mon, Jan 08, 2007 at 07:03:35PM -0500, Erez Zadok wrote:
> > However, I must caution that a file system like ecryptfs is very different
> > from Unionfs, the latter being a fan-out
On Mon, 08 Jan 2007 09:55:24 +0100, Jens Axboe said:
> On Sat, Jan 06 2007, [EMAIL PROTECTED] wrote:
> > On Thu, 04 Jan 2007 22:02:00 PST, Andrew Morton said:
> >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc
3/2.6.20-rc3-mm1/
> >
> > With git-block.patch
On Tue, 2007-01-09 at 17:16 +0100, Pierre Peiffer wrote:
> @@ -133,8 +133,8 @@ struct futex_q {
>* Split the global futex_lock into every hash list lock.
>*/
> struct futex_hash_bucket {
> - spinlock_t lock;
> - struct list_head chain;
> + spinlock_t
On Tue, 9 Jan 2007, Adrian Bunk wrote:
>
> Subject : BUG: at mm/truncate.c:60 cancel_dirty_page() (reiserfs)
> References : http://lkml.org/lkml/2007/1/7/117
> Submitter : Malte Schröder <[EMAIL PROTECTED]>
> Status : unknown
Adrian, this is also available as
On Tue, Jan 09, 2007 at 03:15:39PM +, Alasdair G Kergon wrote:
> On Mon, Jan 08, 2007 at 06:01:11PM -0500, Dave Jones wrote:
> > Did backwards compatability with old LVM metadata break intentionally
> > in 2.6.19 ? I have a volume that mounts just fine in 2.6.18,
> > but moving to 2.6.19
On Tue, Jan 09, 2007 at 03:28:45PM -0200, Henrique de Moraes Holschuh wrote:
> A new one for you, it exists since 2.6.20-rc2.
>
> Subject : ThinkPad removable bay support disabled unconditionally
> References :
> http://marc.theaimsgroup.com/?l=linux-acpi=116750681901208=2
> Caused-By
In message <[EMAIL PROTECTED]>, Christoph Hellwig writes:
> On Mon, Jan 08, 2007 at 07:03:35PM -0500, Erez Zadok wrote:
> > However, I must caution that a file system like ecryptfs is very different
> > from Unionfs, the latter being a fan-out file system---and both have very
> > different goals.
In message <[EMAIL PROTECTED]>, Jan Kara writes:
> > In message <[EMAIL PROTECTED]>, Andrew Morton writes:
> > > On Sun, 7 Jan 2007 23:12:53 -0500
> > > "Josef 'Jeff' Sipek" <[EMAIL PROTECTED]> wrote:
> > >
> > > > +Modifying a Unionfs branch directly, while the union is mounted, is
> > > >
Andrew, All,
This patch contains a major rewrite to the e1000 driver that groups and separates e1000
hardware by chipset family. It abstracts the hardware specific code into an API that
will allow us to continue to maintain the complex e1000 driver and add new hardware
support to it without
On Tue, 9 Jan 2007, Tomasz Kvarsin wrote:
>
> During boot into 2.6.20-rc4 iptables says
> iptables-restore: line 15 failed.
> And works fine with my default kernel: 2.6.18.x
I bet you enabled the new transport-agnostic netfilter, and didn't enable
some of the actual rules needed for your
On Tue, Jan 09, 2007 at 06:41:56PM +0900, takada wrote:
> In kernel 2.6, write back wrong register when configure Geode processor.
> Instead of storing to CCR4, it stores to CCR3.
>
> --- linux-2.6.19/arch/i386/kernel/cpu/cyrix.c.orig2007-01-09
> 16:45:21.0 +0900
> +++
Robert P. J. Day wrote:
> just to stir the pot a bit regarding the discussion of the two
> different ways to define macros,
You mean function-like macros, right?
> i've just noticed that the "({ })"
> notation is not universally acceptable. i've seen examples where
> using that notation
Martin Michlmayr wrote:
* Stuart Anderson <[EMAIL PROTECTED]> [2007-01-05 09:40]:
shark w/o any changes to the kernel. I dug a bit further, both in the
driver, and in the HW spec for the shark, and discovered that the video
chip on the shark is connected via the VL bus, not the PCI bus. The
A new one for you, it exists since 2.6.20-rc2.
Subject : ThinkPad removable bay support disabled unconditionally
References : http://marc.theaimsgroup.com/?l=linux-acpi=116750681901208=2
Caused-By: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
Handled-By : Henrique de Moraes
Peter Staubach wrote:
> Hua Zhong wrote:
>> Hi,
>>
>> A while ago there was a discussion about supporting direct-io on tmpfs.
>>
>> Here is a simple patch that does it.
>>
>> 1. A new fs flag FS_RAM_BASED is added and the O_DIRECT flag is ignored
>>if this flag is set (suggestions on a
In message <[EMAIL PROTECTED]>, Trond Myklebust writes:
> I'm saying that at the very least it should not Oops in these
> situations. As to whether or not they are something you want to handle
> more gracefully, that is up to you, but Oopses are definitely a
> showstopper.
>
> Trond
I totally
> On Tue, 2007-01-09 at 11:30 -0500, Trond Myklebust wrote:
> > On Tue, 2007-01-09 at 13:15 +0100, Jan Kara wrote:
> > > > On Mon, Jan 08, 2007 at 11:18:52AM -0800, Andrew Morton wrote:
> > > > > On Sun, 7 Jan 2007 23:12:53 -0500
> > > > > "Josef 'Jeff' Sipek" <[EMAIL PROTECTED]> wrote:
> > > > >
On Tue, 2007-01-09 at 12:03 -0500, Trond Myklebust wrote:
> I'm saying that at the very least it should not Oops in these
> situations. As to whether or not they are something you want to handle
> more gracefully, that is up to you, but Oopses are definitely a
> showstopper.
I don't think anyone
> The time for adding new stuff to 2.6.20 is /long/ past. We stop
> adding things like new drivers when Linus releases 2.6.X-rc1.
Well, in the past I think new drivers have been added after the merge
window, given that there's no chance of regressions (old kernel == no
support for device X, so
Robert P. J. Day wrote:
just to stir the pot a bit regarding the discussion of the two
different ways to define macros, i've just noticed that the "({ })"
notation is not universally acceptable. i've seen examples where
using that notation causes gcc to produce:
error: braced-group within
Hello Roland!
Here is a patch for ehca to use proper flag, ie. GFP_ATOMIC resp. GFP_KERNEL,
when
calling get_zeroed_page() to prevent "Bug: scheduling while atomic...". This
error
does not cause a kernel panic but makes ipoib un-usable afterwards. It is
reproducible on 2.6.20-rc4 if one does
On Tue, 2007-01-09 at 18:04 +0100, Jan Kara wrote:
> But once you have MS_RDONLY set, there should be no modifications of
> the underlying filesystem, should they? And I have understood that the
> only problem is modifying the filesystem underneath unionfs. But maybe
> I'm missing something.
> > To top it off, someone noticed some of the failures and fixed them but
> > nobody thought to fix the drivers in drivers/video/backlight itself and
> > a mac reference seems to have escaped too.
>
> If my memory serves me well, there is a patch for mac in mm.
> Not sure other drivers in
Jean Delvare wrote:
> Hi all,
>
> Since 2.6.20-rc1 or so, running "make" always builds a new kernel with
> an incremented version number, whether there has actually been any
> change done to the code or configuration or not. This increases the
> build time quite a bit.
>
> I've tracked it down
101 - 200 of 736 matches
Mail list logo
