On Wed, Dec 27, 2006 at 01:56:24PM +, Al Viro wrote:
> On Wed, Dec 27, 2006 at 04:42:23PM +0300, Alexey Dobriyan wrote:
> >
> > struct proc_entry_raw foo_pe_raw = {
> > .owner = THIS_MODULE,
> > .name = "foo",
> > .mode = 0644,
> > .read_proc
John Freighter wrote:
Has anybody succeded running OpenSolaris under KVM virtualization?
Before I download OS install DVD in vain...
There was indeed a report (and a patch) from Michael Riepe to that
effect. -rc2 should contain that patch. Please report to kvm-devel if
it doesn't work.
"Thomas Maier" <[EMAIL PROTECTED]> writes:
> this is a patch to cleanup some things in the pktcdvd driver for linux 2.6.20:
>
> - update documentation
> - removed DECLARE_BUF_AS_STRING macro
This part looks good.
> - use clear_bdi_congested/set_bdi_congested functions directly instead of old
>
Hi!
> Was just wondering if the _var_ in kfree(_var_) could be set to NULL after
> its freed. It may solve
> the problem of accessing some freed memory as the kernel will crash since
> _var_ was set to NULL.
>
> Does this make sense? If yes, then how about renaming kfree to something else
> an
Hi!
> +Identifying GPIOs
> +-
> +GPIOs are identified by unsigned integers in the range 0..MAX_INT. That
> +reserves "negative" numbers for other purposes like marking signals as
> +"not available on this board", or indicating faults.
> +
> +Platforms define how they use those in
Hi!
> Arch-neutral GPIO calls for PXA.
>
> From: Philipp Zabel <[EMAIL PROTECTED]>
Missing s-o-b?
> +static inline int gpio_direction_input(unsigned gpio)
> +{
> + if (gpio > PXA_LAST_GPIO)
> + return -EINVAL;
> + pxa_gpio_mode(gpio | GPIO_IN);
> +}
Missing return 0?
> +s
On Tue 26-12-06 16:18:32, yunfeng zhang wrote:
> In the patch, I introduce a new page system -- pps which
> can improve
> Linux swap subsystem performance, you can find a new
> document in
> Documentation/vm_pps.txt. In brief, swap subsystem
> should scan/reclaim
> pages on VMA instead of zone::
Hi!
> > > developer documentation, and one short paragraph about PM_TRACE that
> > > tells me nothing new. Could you point me to the documentation part that
> > > you are referring to, and that tells me what to do if PM_TRACE shows
> > > the usb device but the failure only occurs when I load the s
Hi!
> +static inline int gpio_direction_input(unsigned gpio)
> +{
> + if (gpio > GPIO_MAX)
> + return -EINVAL;
> + GPDR = (GPDR_In << gpio) 0
> +}
Missing return 0.
> +static inline int gpio_direction_output(unsigned gpio)
> +{
> + if (gpio > GPIO_MAX)
> + ret
Hi!
> > > > I got this nasty oops while playing with debugger. Not sure if that is
> > > > related; it also might be something with bluetooth; I already know it
> > > > corrupts memory during suspend, perhaps it corrupts memory in some
> > > > error path?
> > >
> > > Okay, I spoke too soon. bluet
On Dec 27 2006 17:10, Pavel Machek wrote:
>> Was just wondering if the _var_ in kfree(_var_) could be set to
>> NULL after its freed. It may solve the problem of accessing some
>> freed memory as the kernel will crash since _var_ was set to NULL.
>>
>> Does this make sense? If yes, then how abou
Do we have a right to reverse engineer hardware, or they are protected by
patents or something similar that would prevent you from publishing results
adn/or drivers (open source).
Are there any restrictions in how you obtain information - signal analyser,
disassembly of windows driver, etc.
Rok
>Since Linus can't necessarily hear us, lets all type in harmony.
Just add him in Cc ;-)
>> Be it remembered that on the 28th day of December in the year of our
>> Lord 1969, there was born in the town of Helsinki, Finland, Linus
>> Benedict Torvalds.
So that's which stardate...
-`
On 12/28/06, Rok Markovic <[EMAIL PROTECTED]> wrote:
Do we have a right to reverse engineer hardware, or they are protected by
patents or something similar that would prevent you from publishing results
adn/or drivers (open source).
This is a pretty good resource:
http://www.chillingeffects.
On Wed, 2006-12-27 at 19:04 -0800, Linus Torvalds wrote:
>
> On Wed, 27 Dec 2006, David Miller wrote:
> > >
> > > I still don't see _why_, though. But maybe smarter people than me can see
> > > it..
> >
> > FWIW this program definitely triggers the bug for me.
>
> Ok, now that I have something
On Dec 28 2006 00:06, Mike Huber wrote:
>
> I would like to point out one key argument against raid0 swap partitions,
> which is that, should a drive failure occur, the least used programs in
> memory are most drastically affected. Unfortunately, in the case of a
> drastic drive failure in a stan
* Pavel Machek <[EMAIL PROTECTED]> wrote:
> > But lots of people have now written downstream log-parsing tools
> > which might break due to this change, so I'm inclined to go with
> > Ingo's patch, and restore the old (il)logic.
>
> People should not be parsing syslog. If they do, they deserve
I get this message in my webservers (with NFS mounted homedirs) logs once
in a while :
kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a
nice day...
It doesn't seem to have any bad effect on anything, but it would be nice
to know if there is any cause for concern.
* Gordon Farquharson <[EMAIL PROTECTED]> [2006-12-27 22:38]:
> >That's just 400kB!
> >
> >There's no way you should see corruption with that kind of value. It
> >should all stay solidly in the cache.
> >
> >Is this perhaps with ARM nommu or something else strange? It may be that
> >the program just
Parag Warudkar wrote:
Running qemu with 512M ram out of available 480M total invoked the OOM killer
(that's obvious along with other OOM-killer stupidities like killing totally
irrelevant processes) followed by the below OOPS.
Killed process 19271 (trashapplet)Out of memory: kill process 12475
On Dec 28 2006 10:27, Jesper Juhl wrote:
>
>I get this message in my webservers (with NFS mounted homedirs) logs once
>in a while :
>
> kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a
> nice day...
This happens when the underlying "block device" disappears, the mos
* Catalin Marinas <[EMAIL PROTECTED]> wrote:
> >memleak info is at a negative offset from the allocated pointer. I.e.
> >that if kmalloc() returns 'ptr', the memleak info could be at
> >ptr-sizeof(memleak_info). That way you dont have to know the size of the
> >object beforehand and there's absol
I first saw the problem on the 64x2 box after upgrading to 2.6.19. The
network appeared OK with ifconfig and route -n, but I had no network
access. Pinging any other box, the box was responding, but no response
was received by the 64x2. I checked cables and the switch which were OK,
so I figured
Currently native linux AIO is properly supported (in the sense of
actually being asynchronous) only for files opened with O_DIRECT.
While this suffices for a major (and most visible) user of AIO, i.e. databases,
other types of users like Samba require AIO support for regular file IO.
Also, for gli
Add a wait queue parameter to the action routine called by
__wait_on_bit to allow it to determine whether to block or
not.
Signed-off-by: Suparna Bhattacharya <[EMAIL PROTECTED]>
Acked-by: Ingo Molnar <[EMAIL PROTECTED]>
---
linux-2.6.20-rc1-root/fs/buffer.c |2 +-
linux-2
In order to allow for interruptible and asynchronous versions of
lock_page in conjunction with the wait_on_bit changes, we need to
define low-level lock page routines which take an additional
argument, i.e a wait queue entry and may return non-zero status,
e.g -EINTR, -EIOCBRETRY, -EWOULDBLOCK etc
init_wait_bit_key() initializes the key field in an already
allocated wait bit structure, useful for async wait bit support.
Also separate out the wait bit test to a common routine which
can be used by different kinds of wakeup callbacks.
Signed-off-by: Suparna Bhattacharya <[EMAIL PROTECTED]>
A
Allocates space for the default io wait queue entry (actually a wait
bit entry) in the task struct. Doing so simplifies the patches
for AIO wait page allowing for cleaner and more efficient
implementation, at the cost of 28 additional bytes in task struct
vs allocation on demand on-stack.
Signe
Enable wait bit based filtered wakeups to work for AIO.
Replaces the wait queue entry in the kiocb with a wait bit
structure, to allow enough space for the wait bit key.
This adds an extra level of indirection in references to the
wait queue entry in the iocb. Also, an extra check had to be
added
Define low-level page wait and lock page routines which take a
wait queue entry pointer as an additional parameter and
return status (which may be non-zero when the wait queue
parameter signifies an asynchronous wait, typically during
AIO).
Synchronous IO waits become a special case where the wai
Converts the wait for page to become uptodate (lock page)
after readahead/readpage (in do_generic_mapping_read) to a retry
exit, to make buffered filesystem AIO reads actually synchronous.
The patch avoids exclusive wakeups with AIO, a problem originally
spotted by Chris Mason, though the reasoni
AIO support for O_SYNC buffered writes, built over O_SYNC-speedup.
It uses the tagged radix tree lookups to writeout just the pages
pertaining to this request, and retries instead of blocking
for writeback to complete on the same range. All the writeout is
issued at the time of io submission, and
Sorry this should have read [PATCH 1/8] instead of [PATCH 1/6]
Regards
Suparna
--
Suparna Bhattacharya ([EMAIL PROTECTED])
Linux Technology Center
IBM Software Lab, India
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Hi,
One of my NFS servers just blew up on me. I found the following in the log -
hope it is useful :
NMI Watchdog detected LOCKUP on CPU 1
CPU 1
Modules linked in: sg eeprom i2c_i801
Pid: 284, comm: scsi_eh_2 Not tainted 2.6.18.1 #1
RIP: 0010:[] [] __delay+0xa/0x20
RSP: :81022fbf5d80
On Wed, Dec 27, 2006 at 12:45:50PM -0800, Ulrich Drepper ([EMAIL PROTECTED])
wrote:
> Evgeniy Polyakov wrote:
> > Why do we want to inject _ready_ event, when it is possible to mark
> > event as ready and wakeup thread parked in syscall?
>
> Going back to this old one:
>
> How do you want to mar
* Suparna Bhattacharya <[EMAIL PROTECTED]> wrote:
> The following is a sampling of comparative aio-stress results with the
> patches (each run starts with uncached files):
>
> -
>
> aio-stress throughput comparisons (in
Mikulas Patocka wrote:
>>> If user (or script) doesn't specify that flag, it doesn't help. I think
>>> the best solution for these filesystems would be either to add new syscall
>>> int is_hardlink(char *filename1, char *filename2)
>>> (but I know adding syscall bloat may be objectionable)
>> i
> Hmm, then maybe it'd be worth updating that patch I just sent so that
> the only change is to switch #includes for the extern decl ... i.e. to
> "export" it only to other statically linked kernel code, rather than to
> modules. I'll do that.
>
> My own question about that EXPORT_SYMBOL was whe
On Wed, Dec 27, 2006 at 10:20:20PM -0700, Gordon Farquharson wrote:
> I have run the program a few times, and the output is pretty
> consistent. However, when I increase the target size, the difference
> between the expected and actual values is larger.
>
> Written as (749)935(738)
> Chunk 1113 co
* Gordon Farquharson <[EMAIL PROTECTED]> [2006-12-27 22:38]:
> >> #define TARGETSIZE (100 << 12)
> >
> >That's just 400kB!
> >
> >There's no way you should see corruption with that kind of value. It
> >should all stay solidly in the cache.
> >
> >Is this perhaps with ARM nommu or something else str
On Wed, 27 Dec 2006, Theodore Tso wrote:
> On Wed, Dec 27, 2006 at 08:18:24PM +0100, Karel Zak wrote:
> > Frankly, it wasn't always easy to use SeLinux in previous FC
> > releases, but there is huge progress and I think it's much better in
> > FC6.
>
> I've never tried SELinux, but at one poin
On Thu, 28 Dec 2006 15:19:04 +0800
Fengguang Wu <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 27, 2006 at 07:49:59PM -0800, Andrew Morton wrote:
> > On Thu, 28 Dec 2006 11:17:25 +0800
> > "Zhang, Yanmin" <[EMAIL PROTECTED]> wrote:
> >
> > > Currently, by /proc/sys/vm/drop_caches, applications could dr
On Thu, 28 Dec 2006, Jesper Juhl wrote:
>
> I get this message in my webservers (with NFS mounted homedirs) logs once
> in a while :
>
> kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a
> nice day...
>
> It doesn't seem to have any bad effect on anything, but it
From: Melissa Howland <[EMAIL PROTECTED]>
[S390] Change max. buffer size for monwriter device.
Reduce the max. buffer size for the monwriter device to prevent a
possible problem with the z/VM monitor service.
Signed-off-by: Melissa Howland <[EMAIL PROTECTED]>
Signed-off-by: Martin Schwidefsky <[
From: Michael Holzheu <[EMAIL PROTECTED]>
[S390] cio: fix stsch_reset.
Copy inline assembly of stsch and add "memory" to clobber list in order
to prevent gcc from optimizing away the checking of the global variable
"pgm_check_occured".
Signed-off-by: Michael Holzheu <[EMAIL PROTECTED]>
Signed-of
Please pull from 'for-linus' branch of
git://git390.osdl.marist.edu/pub/scm/linux-2.6.git for-linus
to receive the following updates:
drivers/s390/char/monwriter.c |2 +-
drivers/s390/cio/cio.c| 13 ++---
2 files changed, 11 insertions(+), 4 deletions(-)
Melissa H
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc2/2.6.20-rc2-mm1/
- Various updates. Things are pretty quiet at present.
There are quite a few things here which are needed for 2.6.20 but which go
through subsystem maintainers, when people wake up again.
Boilerplat
Hi Pavel,
> > > > > I got this nasty oops while playing with debugger. Not sure if that is
> > > > > related; it also might be something with bluetooth; I already know it
> > > > > corrupts memory during suspend, perhaps it corrupts memory in some
> > > > > error path?
> > > >
> > > > Okay, I spo
On Thu, Dec 28, 2006 at 02:29:26AM -0800, Andrew Morton wrote:
> On Thu, 28 Dec 2006 15:19:04 +0800
> Fengguang Wu <[EMAIL PROTECTED]> wrote:
> > Yanmin: I've been using the fadvise tool from
> > http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz
> >
> > It's a nice tool:
> >
> > %
On Thu, Dec 28, 2006 at 11:16:59AM +0100, Martin Michlmayr wrote:
> * Gordon Farquharson <[EMAIL PROTECTED]> [2006-12-27 22:38]:
> > >> #define TARGETSIZE (100 << 12)
> > >
> > >That's just 400kB!
> > >
> > >There's no way you should see corruption with that kind of value. It
> > >should all stay s
On Wed, 2006-12-27 at 17:37 -0600, Loye Young wrote:
> Be it remembered that on the 28th day of December in the year of our
> Lord 1969, there was born in the town of Helsinki, Finland, Linus
> Benedict Torvalds.
>
> Long live the king.
Hear, hear!!
--LX
-
To unsubscribe from this list: send t
On Thu, Dec 28, 2006 at 02:29:26AM -0800, Andrew Morton wrote:
> On Thu, 28 Dec 2006 15:19:04 +0800
> Fengguang Wu <[EMAIL PROTECTED]> wrote:
>
> > Yanmin: I've been using the fadvise tool from
> > http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz
> >
> > It's a nice tool:
> >
> >
On Thu, 28 Dec 2006 10:45:08 +
Russell King <[EMAIL PROTECTED]> wrote:
> The kernel community needs to get a grip with the implementation of
> new syscalls - we need a process where architecture maintainers get
> to review the arguments _prior_ to them being accepted into the kernel.
> That wa
> It seems like the posix idea of unique doesn't
> hold water for modern file systems
are you really sure?
and if so, why don't we fix *THAT* instead, rather than adding racy
syscalls and such that just can't really be used right...
--
if you want to mail me at work (you don't), use arjan (a
[ I'm only subscribed to linux-fsdevel@ from above Cc list, please keep this
list in Cc: for AIO related stuff. ]
On Wed, Dec 27, 2006 at 04:25:30PM +, Christoph Hellwig ([EMAIL PROTECTED])
wrote:
> (1) note that there is another problem with the current kevent interface,
> and that is
On 28/12/06, Ingo Molnar <[EMAIL PROTECTED]> wrote:
* Catalin Marinas <[EMAIL PROTECTED]> wrote:
> >memleak info is at a negative offset from the allocated pointer. I.e.
> >that if kmalloc() returns 'ptr', the memleak info could be at
> >ptr-sizeof(memleak_info). That way you dont have to know
On Wed, Dec 27, 2006 at 07:04:34PM -0800, Linus Torvalds wrote:
> [ Modified test-program that tells you where the corruption happens (and
> when the missing parts were supposed to be written out) appended, in
> case people care. ]
Hi
2.6.18 (and 2.6.18.6) is ok, 2.6.19-rc1 is broken. I tri
add gitignore file for relocs in arch i386 fix
The .gitigonre was intended to be in arch/ subtree.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
Cc: Thomas Meyer <[EMAIL PROTECTED]>
---
commit 45dc5568e87fb6ce405b57e18cc0eb4a98da073c
tree c8d38366bee888b5cf043853a8c2edbabdd3b2ee
parent 6db76f0b9
Jesper Juhl wrote:
I get this message in my webservers (with NFS mounted homedirs) logs once
in a while :
kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a
nice day...
It doesn't seem to have any bad effect on anything, but it would be nice
to know if there is an
On linux-26..20-rc2, "modprobe kvm-intel" loaded the module
successful, but running qemu returns a error ...
/usr/local/kvm/bin/qemu -hda vdisk.img -cdrom cd.iso -boot d -m 128
open /dev/kvm: No such file or directory
Could not initialize KVM, will disable KVM support
/dev/kvm does not exist
mxser_new, remove unused stuff
- nobody waits on close_wait
- ASYNC_SPLIT_TERMIOS is not set by anybody, so do not test this flag
- process session and pgrp are useless information
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit 8fc2346d2eab1a1780c319ddd77d818a270aba02
tree 2e3a0a372616
mxser, obsolete old, nonexperimental new
Mark v 1.x as obsolete and v 2.x as non-experimental in Kconfig.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit ce3d140accc090dee75676a4db2b1ddf7b39843e
tree a4322efa3ce3a55abd76340d769ec8e365a43b38
parent 8fc2346d2eab1a1780c319ddd77d818a270aba0
mxser_new, remove tty_wakeup bottomhalf
It's safe to call tty_wakeup from irq context. Do not schedule it for later
calling.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit ec5dee09bf3e78d886d61168625e63280c715739
tree ec09e7afa162b4901d4304d89e588a12df77e494
parent ce3d140accc090dee756
mxser_new, clean request_irq call
We always set ASYNC_SHARE_IRQ, so do not test against this flag and request
shared irq directly. Also remove nonsense comment.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit ab35af25a3d01f1e07fc8de5b96f484b93a8ad2a
tree 3a79b6dba3253393371decb0c2cdd97c
This is an experiment on how an SD/MMC card could be used in the MTD layer.
I don't currently have a system set up to test this, so this driver is
completely _untested_ and therefore you should consider it _broken_.
You can get similar functionality by using the mmc_block driver together
with bloc
> Seems to me anyone really desperate to put PCI devices into a low
> power mode, without driver support at the "ifdown" level, would be
> able just "rmmod driver; setpci".
Incorrect for very obvious reasons - there may be two devices driven by
the same driver one up and one down.
Alan
-
To uns
>On linux-26..20-rc2, "modprobe kvm-intel" loaded the module
>successful, but running qemu returns a error ...
>
>/usr/local/kvm/bin/qemu -hda vdisk.img -cdrom cd.iso -boot d -m 128
>open /dev/kvm: No such file or directory
>Could not initialize KVM, will disable KVM support
Are you sure the kvm
Loye Young wrote:
>>Take for example the AT keyboard which is
>>one of the most common keyboards in the world. I have seen and
>>used it attached to a PC via parport, serial port and the standard
>>PS/2 port. So to handle cases like this the input layer created a
>>serio interface.
>
>
> If plai
On Thu, Dec 28, 2006 at 02:11:49PM +0530, Suparna Bhattacharya wrote:
> -extern void FASTCALL(lock_page_slow(struct page *page));
> +extern int FASTCALL(__lock_page_slow(struct page *page, wait_queue_t *wait));
> extern void FASTCALL(__lock_page_nosync(struct page *page));
> extern void FASTCALL(
> + if (in_aio()) {
> + /* Avoid repeat readahead */
> + if (kiocbTryRestart(io_wait_to_kiocb(current->io_wait)))
> + next_index = last_index;
> + }
Every place we use kiocbTryRestart in this and the next patch it's in
this from, so we should add
Hi,
I am working on a testing framework for file systems focusing on
repair and recovery areas. Right now, I have been timing fsck and
trying to determine the effectiveness of fsck. The idea that I have is
below.
In abstract terms, I create a file system (ideal state), corrupt it,
run fsck on it
Benny Halevy wrote:
It seems like the posix idea of unique doesn't
hold water for modern file systems and that creates real problems for
backup apps which rely on that to detect hard links.
Why not? Granted, many of the filesystems in the Linux kernel don't enforce that
they have unique st_
Location:
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/
git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
RSS feed of the git tree:
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=rss
Changes since 2.6.16.36:
Adrian Bunk (5):
[ALSA]
On 12/28/06, Russell King <[EMAIL PROTECTED]> wrote:
Fixing Linus' test program to pass nr & 255 to memset results in clean
passes on 2.6.9 on TheCus N2100 (IOP8032x) and 2.6.16.9 StrongARM
machines (as would be expected.)
Thanks for the fix, Russell.
I can now trigger the (real) problem by u
On 12/28/06, Dor Laor <[EMAIL PROTECTED]> wrote:
Are you sure the kvm_intel & kvm modules are loaded?
Yes.
Maybe you're bios does not support virtualization.
Configured in the bios on Dell 745.
Please check your dmesg.
I'll double-check dmesg when I get to the office tomorrow. But I'm
p
Jeff Chua wrote:
It's a dynamic misc device, you don't need to create it.
But it'll be nice to be able to manually create the device as I
normally mount "/" as read-only?
udev is the best solution here. It works with read-only root as it
mounts tmpfs on /dev.
--
error compiling committ
* Russell King <[EMAIL PROTECTED]> [2006-12-28 10:49]:
> > By the way, I just tried it with TARGETSIZE (100 << 12) on a different
> > ARM machine (a Thecus N2100 based on an IOP32x chip with 128 MB of
> > memory) and I see similar results to that from Gordon:
>
> Work around the glibc memset() pro
Hi all,
I am writing a kernel module that creates a kernel thread on a SMP
platform.
How to get the ID of the processor the kernel thread run on? Have any
kernel API? THX
Raymond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMA
I set a qemu environment to test kernels: http://guichaz.free.fr/linux-bug/
I have corruption with every Fedora release kernel except the first, that is
2.4.22 works, but 2.6.5, 2.6.9, 2.6.11, 2.6.15 and 2.6.18-1.2798 exhibit
some
corruption.
Command line to test:
qemu root_fs -snapshot -kerne
I am writing a kernel module that creates a kernel thread on a SMP
platform.
How to get the ID of the processor the kernel thread run on? Have any
kernel API? THX
Raymond
try smp_processor_id() it returns an unsigned int.
Thanks,
jerry
-
To unsubscribe from this list: send the line "unsub
On Thu, Dec 28, 2006 at 02:42:37AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.20-rc1-mm1:
>...
> git-dvb.patch
>...
> git trees
>...
This patch fixes the following compile error:
<-- snip -->
...
LD drivers/media/video/built-in.o
drivers/media/video/saa7134/built-in.o:(.dat
On 12/28/06, Avi Kivity <[EMAIL PROTECTED]> wrote:
udev is the best solution here. It works with read-only root as it
mounts tmpfs on /dev.
Thanks for the suggestion and I'll look into it. As for now, my system
works well without udev, and I just wanted to test kvm without the
"dynamic" /dev/
Jeff Chua wrote:
On 12/28/06, Avi Kivity <[EMAIL PROTECTED]> wrote:
udev is the best solution here. It works with read-only root as it
mounts tmpfs on /dev.
Thanks for the suggestion and I'll look into it. As for now, my system
works well without udev, and I just wanted to test kvm without t
* Gordon Farquharson <[EMAIL PROTECTED]> [2006-12-28 07:15]:
> Thanks for the fix, Russell.
>
> I can now trigger the (real) problem by using a 25 MB file (100 << 18)
> and the Linksys NSLU2 (ARM, IXP420 processor, 32 MB RAM).
Me too (using 100 << 18). Interestingly, I don't seem to get any
corr
[sorry for delay with answer]
On Wed, Dec 20, 2006 at 09:35:55PM -0800, Andrew Morton wrote:
> I know nothing of UFS, but here goes..
>
> > Looks like this is the problem, which point Al Viro some time ago:
> > when we allocate block(in this situation 16K) we mark as new
> > only one fragment(in
On Thu, 2006-12-28 at 13:31 +, Alan wrote:
> > Seems to me anyone really desperate to put PCI devices into a low
> > power mode, without driver support at the "ifdown" level, would be
> > able just "rmmod driver; setpci".
>
> Incorrect for very obvious reasons - there may be two devices driv
On Thu Dec 28 15:09 , Guillaume Chazarain sent:
>I set a qemu environment to test kernels: http://guichaz.free.fr/linux-bug/
>I have corruption with every Fedora release kernel except the first, that is
>2.4.22 works, but 2.6.5, 2.6.9, 2.6.11, 2.6.15 and 2.6.18-1.2798 exhibit
>some corruption.
On Wed, 2006-12-27 at 13:54 -0600, Loye Young wrote:
> I, a humble pilgrim in the Land of Tux, have spent over a year seeking
> a simple answer to what seems to me a simple question: How do I expose
> my RS232 barcode scanner to the input layer so that the scanned
> information shows up in applicat
On 22-12-2006 15:28, Eric Sesterhenn wrote:
> hi,
>
> while running my usual stuff on 2.6.20-rc1-git5, sfuzz
> (http://www.digitaldwarf.be/products/sfuzz.c)
> did the following, to produce the lockdep warning below:
...
> Here is the stacktrace:
>
> [ 313.239556] ===
> Pluse possible naming updates discussed in the last mail. Also do we
> really need to pass current->io_wait here? Isn't the waitqueue in
> the kiocb always guaranteed to be the same? Now that all pagecache
> I/O goes through the ->aio_read/->aio_write routines I'd prefer to
> get rid of the ta
On Thu, Dec 28, 2006 at 11:55:10AM +, Christoph Hellwig wrote:
> On Thu, Dec 28, 2006 at 02:11:49PM +0530, Suparna Bhattacharya wrote:
> > -extern void FASTCALL(lock_page_slow(struct page *page));
> > +extern int FASTCALL(__lock_page_slow(struct page *page, wait_queue_t
> > *wait));
> > exter
Jeff Layton wrote:
> Benny Halevy wrote:
>> It seems like the posix idea of unique doesn't
>> hold water for modern file systems and that creates real problems for
>> backup apps which rely on that to detect hard links.
>>
>
> Why not? Granted, many of the filesystems in the Linux kernel don't e
On Thu, Dec 28, 2006 at 11:57:47AM +, Christoph Hellwig wrote:
> > + if (in_aio()) {
> > + /* Avoid repeat readahead */
> > + if (kiocbTryRestart(io_wait_to_kiocb(current->io_wait)))
> > + next_index = last_index;
> > + }
>
> Every place we use kiocbTr
Arjan van de Ven wrote:
>> It seems like the posix idea of unique doesn't
>> hold water for modern file systems
>
> are you really sure?
Well Jan's example was of Coda that uses 128-bit internal file ids.
> and if so, why don't we fix *THAT* instead
Hmm, sometimes you can't fix the world, esp
Benny Halevy wrote:
Jeff Layton wrote:
Benny Halevy wrote:
It seems like the posix idea of unique doesn't
hold water for modern file systems and that creates real problems for
backup apps which rely on that to detect hard links.
Why not? Granted, many of the filesystems in the Linux kernel do
* Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> Generic event handling mechanism.
it would be /very/ helpful to state against which kernel tree the
patch-queue is. It does not apply to 2.6.20-rc1 nor to -rc2 nor to
2.6.19. At which point i gave up ...
Ingo
-
To unsubscribe from this l
* Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> Generic event handling mechanism.
i see it covers alot of event sources, but i cannot see block IO
notifications. Am i missing something?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
On Dec 28 2006 11:57, Christoph Hellwig wrote:
>
>> +
>> +if ((error = __lock_page(page, current->io_wait))) {
>> +goto readpage_error;
>> +}
>
>This should be
>
> error = __lock_page(page, current->io_wait);
> if (error)
>
On Dec 28 2006 10:54, Jeff Layton wrote:
>
> Sorry, I should qualify that statement. A lot of filesystems don't have
> permanent i_ino values (mostly pseudo filesystems -- pipefs, sockfs, /proc
> stuff, etc). For those, the idea is to try to make sure we use 32 bit values
> for them and to ensure
Hi,
while writing a netfilter match module I found that, when run,
skb->h.th is not set to the TCP header (it is assured that the packet
_is_ TCP), as this printk shows me:
skb: h.th=cb5bc4dc nh.iph=cb5bc4dc mac.raw=cb5bc4ce head=cb5bc400
data=cb5bc4dc tail=cb5bc510 end=cb5bc580
Is it intende
1 - 100 of 270 matches
Mail list logo
