> >
> > to a large degree, a device driver that doesn't suspend is better than
> > no device driver at all, right?
>
> I'm not sure it is. It only makes more work for everyone else: We have
> to help people figure out what causes their computer to fail to resume
> (which can take quite a
Emmeran Seehuber wrote:
# smartctl -a /dev/sda
smartctl version 5.36 [x86_64-unknown-linux-gnu] Copyright (C) 2002-6 Bruce
Allen
Home page is http://smartmontools.sourceforge.net/
Device: ATA WDC WD1500ADFD-0 Version: 20.0
Serial number: WD-WMAP41246348
Device type: disk
Local Time
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for input subsystem.
Changelog:
--
Akinobu Mita (1):
Input: pc110pad -
On Fri, Feb 09, 2007 at 07:25:34PM -0500, Jeff Garzik wrote:
> Nigel Cunningham wrote:
> >Hi.
> >
> >On Fri, 2007-02-09 at 23:17 +0100, Arjan van de Ven wrote:
> >>On Sat, 2007-02-10 at 08:57 +1100, Nigel Cunningham wrote:
> >>>Hi.
> >>>
> >>>I don't think this is already done (feel free to
This update breaks sata_via on my VIA K8T800Pro machine:
sata_via :00:0f.0 : failed to iomap PCI BAR 0
sata_via :00:0f.0 : out of memory
sata_via probe of :00:0f.0 failed with error -12
--
Markus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Applied.
thanks,
-Len
On Friday 09 February 2007 19:18, Michael Hanselmann wrote:
> Commit 40b20c257a13c5a526ac540bc5e43d0fdf29792a by Len Brown introduced
> a null pointer dereference in the appledisplay driver. This patch fixes
> it.
>
> Signed-off-by: Michael Hanselmann <[EMAIL PROTECTED]>
>
Print an explicit warning when a device's UDMA mode is limited due to
a 40-wire cable being detected, so that users have some idea why their
device isn't running as fast as it should.
This moves the application of the drive's mode masks before the cable
rule, so that can tell whether the rate is
Hi.
On Sat, 2007-02-10 at 03:42 +, Matthew Garrett wrote:
> On Sat, Feb 10, 2007 at 08:57:49AM +1100, Nigel Cunningham wrote:
>
> > Can we start to NAK new drivers that don't have proper power management
> > implemented? There really is no excuse for writing a new driver and not
> > putting
Ayaz Abdulla wrote:
For all those who are having issues, please try out the attached patch.
Ayaz
Seems to solve the problem for me (not heavily tested, but certainly
isn't totally dead as it was before).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL
On Fri, Feb 09, 2007 at 08:59:55PM -0500, Lee Revell wrote:
> On 2/9/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
> >I would disagree that it's a peripheral issue, it's pretty core these
> >days, at least for any hardware that you can stuff in a laptop (though a
> >fair number of desktops get
On Fri, 9 Feb 2007, Roland McGrath wrote:
> I don't think I really object to the ABI change of clearing %dr6 after an
> exception so that it does not accumulate multiple results. But first I'll
> have to convince myself that we never actually do want to accumulate
> multiple results. Hmm, I
On Friday 09 February 2007 18:09, Pavel Machek wrote:
> Hi!
>
> > Per your request, and the request of the distros, we've changed
> > how ACPICA Core releases are integrated into Linux so that each
> > upstream (CVS) check-in appears as a single git commit.
> > While this process is not yet
Hi Dmitry!
On Fri, 2007-02-09 at 22:27 -0500, Dmitry Torokhov wrote:
> Hi Nigel,
>
> On Friday 09 February 2007 21:05, Nigel Cunningham wrote:
> > [ 17.684475] Device driver serio0 lacks bus and class support for being
> > resumed.
> > [ 17.684724] Device driver serio1 lacks bus and class
On Sat, 10 Feb 2007, Rusty Russell wrote:
> Well it was the use of get_order() which triggered Andi's alarm bells,
> so I went back to deriving it. This code is correct, however.
+ hype_pages = alloc_pages(GFP_KERNEL|__GFP_ZERO, HYPERVISOR_MAP_ORDER);
+ if (!hype_pages)
+
On Sat, Feb 10, 2007 at 08:57:49AM +1100, Nigel Cunningham wrote:
> Can we start to NAK new drivers that don't have proper power management
> implemented? There really is no excuse for writing a new driver and not
> putting .suspend and .resume methods in anymore, is there?
The PCI layer is able
On Fri, Feb 09, 2007 at 05:24:10PM -0800, Kristen Carlson Accardi wrote:
> The user interface for the Bay driver is via sysfs - it is a platform
> driver
Though, ideally, in the long run it'll be tied into the PATA/SATA
interface that it's associated with. That involves a little more magic,
Hi Nigel,
On Friday 09 February 2007 21:05, Nigel Cunningham wrote:
> [ 17.684475] Device driver serio0 lacks bus and class support for being
> resumed.
> [ 17.684724] Device driver serio1 lacks bus and class support for being
> resumed.
> [ 17.684874] Device driver psaux lacks bus and
Over the past year we were able to make the necessary changes to the
microcode used with the 3945 such that we were able to remove the
regulatory daemon.
Great news !! Congratz ;-)
--
As you read this post global entropy rises. Have Fun ;-)
Nick
-
To unsubscribe from this list: send the line
On Fri, 2007-02-09 at 18:22 -0800, Lee Revell wrote:
> On 2/9/07, Nigel Cunningham <[EMAIL PROTECTED]> wrote:
> > On Fri, 2007-02-09 at 20:59 -0500, Lee Revell wrote:
> > > On 2/9/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
> > > > I would disagree that it's a peripheral issue, it's pretty core
Hi.
On Fri, 2007-02-09 at 19:50 -0600, Robert Hancock wrote:
> It also kind of bothers me that if a driver has no suspend/resume
> functions, and you suspend and resume the system, we don't complain
> about it even though there's a very good chance that device is not going
> to function
You're doing it wrong. Please read the bottom of your emails.
On 9 February 2007, at 00:29, Priyanka Sharma wrote:
unsubscribe linux-kernel
--
Priyanka
202.141.151.80/~priyanka
-
To unsubscribe from this list: send the line "unsubscribe linux-
kernel" in
the body of a message to [EMAIL
After running SetPageUptodate, preceeding stores to the page contents to
actually bring it uptodate may not be ordered with the store to set the page
uptodate.
Therefore, another CPU which checks PageUptodate is true, then reads the
page contents can get stale data.
Fix this by ensuring
This a reworked, replacement version of
x86-fix-vdso-mapping-for-aout-executables-* series of patches in -mm.
1) Define arch_setup_additional_pages() as weak in linux/interp.h
2) Include linux/interp.h in appropriate places
3) Conditionally call arch_setup_additional_pages() from binfmt_*.c
__block_write_full_page is calling SetPageUptodate without the page locked.
This is unusual, but not incorrect, as PG_writeback is still set.
However the next patch will require that SetPageUptodate always be called
with the page locked. Simply don't bother setting the page uptodate in this
case
Ensure pages are uptodate after returning from read_cache_page, which allows
us to cut out most of the filesystem-internal PageUptodate calls.
I didn't have a great look down the call chains, but this appears to fixes 7
possible use-before uptodate in hfs, 2 in hfsplus, 1 in jfs, a few in
OK, I have got rid of SetPageUptodate_nowarn, and removed the atomic op
from SetNewPageUptodate. Made PageUptodate_NoLock only issue the memory
barrier is the page was uptodate (hopefully the compiler can thread the
branch into the caller's branch).
SetNewPageUptodate does not do the S390
On 2/9/07, Nigel Cunningham <[EMAIL PROTECTED]> wrote:
On Fri, 2007-02-09 at 20:59 -0500, Lee Revell wrote:
> On 2/9/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
> > I would disagree that it's a peripheral issue, it's pretty core these
> > days, at least for any hardware that you can stuff in a
Hi.
On Fri, 2007-02-09 at 20:59 -0500, Lee Revell wrote:
> On 2/9/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
> > I would disagree that it's a peripheral issue, it's pretty core these
> > days, at least for any hardware that you can stuff in a laptop (though a
> > fair number of desktops get
Hi.
On Fri, 2007-02-09 at 19:50 -0600, Robert Hancock wrote:
> Jeff Garzik wrote:
> > Nigel Cunningham wrote:
> >> Hi.
> >>
> >> On Fri, 2007-02-09 at 23:17 +0100, Arjan van de Ven wrote:
> >>> On Sat, 2007-02-10 at 08:57 +1100, Nigel Cunningham wrote:
> Hi.
>
> I don't think this
On 2/9/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
I would disagree that it's a peripheral issue, it's pretty core these
days, at least for any hardware that you can stuff in a laptop (though a
fair number of desktops get suspended and resumed these days too).
Servers are still the most
On Fri, 09 Feb 2007, Pavel Machek wrote:
> Not including another /proc/acpi/ibm -like nightmare, is it?
Don't worry, I am already on my way to kill /proc/acpi/ibm... :-)
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the
> From: Russell King
> Newsgroups: gmane.linux.kernel
> Subject: Re: -mm merge plans for 2.6.21
> Date: Fri, 9 Feb 2007 22:03:27 +
[]
> However:
>
> sys_foo(int a, int c, unsigned long long b, unsigned long long d)
>
> is entirely reasonable and leaves us with spare room for one additional
>
2007/2/9, Andrew Morton <[EMAIL PROTECTED]>:
On Thu, 8 Feb 2007 20:16:55 +0800 "Cong WANG" <[EMAIL PROTECTED]> wrote:
> 2007/2/8, Andrew Morton <[EMAIL PROTECTED]>:
> > On Thu, 8 Feb 2007 17:07:28 +0800 "Cong WANG" <[EMAIL PROTECTED]> wrote:
> >
> > > Kfifo is a ring-buffer in kernel which can
Jeff Garzik wrote:
Nigel Cunningham wrote:
Hi.
On Fri, 2007-02-09 at 23:17 +0100, Arjan van de Ven wrote:
On Sat, 2007-02-10 at 08:57 +1100, Nigel Cunningham wrote:
Hi.
I don't think this is already done (feel free to correct me if I'm
wrong)..
Can we start to NAK new drivers that don't
On Sat, 10 Feb 2007 02:34:07 +0100
Nick Piggin <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 09, 2007 at 11:45:39AM -0800, Andrew Morton wrote:
> > On Fri, 9 Feb 2007 11:14:55 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > > If so, that might be preventable by leaving the buffer nonuptodate.
Enable readahead to handle partially done read requests, e.g.
sendfile(188, 1921, [1478592], 19553028) = 37440
sendfile(188, 1921, [1516032], 19515588) = 28800
sendfile(188, 1921, [1544832], 19486788) = 37440
sendfile(188, 1921, [1582272], 19449348) = 14400
On Fri, Feb 09, 2007 at 11:45:39AM -0800, Andrew Morton wrote:
> On Fri, 9 Feb 2007 11:14:55 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > If so, that might be preventable by leaving the buffer nonuptodate.
>
> oh, OK, it was buffer_new(), so zeroes are the right thing for a reader to
>
David R wrote:
I've just upgraded my home server to 2.6.20. It's got an Athlon64 on an ASUS
nForce-4 motherboard running a 32 bit kernel. I've had to fall back to using
sata_nv.adma=0 on the kernel command line. One of the NCQ capable drives
repeatedly produced the following errors. There wasn't
On Sat, 10 Feb 2007 02:15:11 +0100
Carl-Daniel Hailfinger <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> > On Fri, 9 Feb 2007 19:37:53 +
> > Alan <[EMAIL PROTECTED]> wrote:
> >
> >> Please just push the EDAC K8 stuff.
> >
> > OK.
> >
> >> Andi will say "no" from now until the
> >> end
Typos in KERN_ERR, KERN_INFO.
Signed-off-by: Nicolas Kaiser <[EMAIL PROTECTED]>
---
arch/arm/mach-imx/dma.c |2 +-
arch/arm/mach-s3c2410/pm-simtec.c |2 +-
arch/arm/plat-omap/dma.c |2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff -ur
On Fri, 9 Feb 2007 23:09:29 +
Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi!
>
> > Per your request, and the request of the distros, we've changed
> > how ACPICA Core releases are integrated into Linux so that each
> > upstream (CVS) check-in appears as a single git commit.
> > While this
Larry Finger wrote:
A bcm43xx user is having problems with suspend/resume with a PCIe system. This
may be the first time
we have tried to resume with PCIe. The problem occurs someplace within the
initialization of the
bcm43xx chip and we are still tracing it; however, there are some strange
Andrew Morton wrote:
> On Fri, 9 Feb 2007 19:37:53 +
> Alan <[EMAIL PROTECTED]> wrote:
>
>> Please just push the EDAC K8 stuff.
>
> OK.
>
>> Andi will say "no" from now until the
>> end of time, but end users want it, distributions want it, and Andi is
>> not the EDAC maintainer so should
(just sent this upstream to Andrew and Linus)
This is libata push 1 of 3. This is largely the "accumulated driver
updates" push: lots of minor changes. A few new drivers.
The most notable thing is "devres", an optional subsystem for drivers
that greatly simplifies the task of driver
Hi all!
On Fre, 09 Feb 2007, James Ketrenos wrote:
> We are pleased to announce the availability of a new driver for the
> Intel PRO/Wireless 3945ABG Network Connection adapter. This new driver
I am impressed: I had 2.6.20 running with ipw3945 + wpa_supplicant. I
installed the d80211 system
Do not clear references when the task_struct's mm is NULL by using
/proc/pid/clear_refs.
Also, use mmap_sem since the mm_struct's VMA's are being iterated in
fs/proc/task_mmu.c.
Reported by Oleg Nesterov <[EMAIL PROTECTED]>.
Signed-off-by: David Rientjes <[EMAIL PROTECTED]>
---
On Sat, 10 Feb 2007 03:39:58 +0300
Oleg Nesterov <[EMAIL PROTECTED]> wrote:
> David Rientjes wrote:
> >
> > +static ssize_t clear_refs_write(struct file *file, const char __user *buf,
> > + size_t count, loff_t *ppos)
> > +{
> > ...
> > + task =
[1.] module: xt_state compiles without errors but cannot be loaded
[2.] Here's what shows up in /var/log/messages:
kernel: xt_state: Unknown symbol nf_conntrack_untracked
kernel: xt_state: Unknown symbol nf_ct_l3proto_module_put
kernel: xt_state: disagrees about version of symbol
Temporarily at:
http://userweb.kernel.org/~chrisl/sparse-0.2-cl2
Will appear later at:
http://ftp.kernel.org//pub/linux/kernel/people/chrisl/patches/sparse/sparse-0.2-cl2/
I have been play with sparse to add more Stanford checker style
of checking. The paper is "Checking System Rules
On Fri, 9 Feb 2007 19:23:31 -0500
"Russ Cox" <[EMAIL PROTECTED]> wrote:
> > "The file system mounted on /tmp/z in the example contains 2^50
> > directories". heh.
> >
> > I do wonder how realistic this problem is in real life.
>
> That's a fair concern, although I was trying this as part
> of
David Rientjes wrote:
>
> +static ssize_t clear_refs_write(struct file *file, const char __user *buf,
> + size_t count, loff_t *ppos)
> +{
> ...
> + task = get_proc_task(file->f_path.dentry->d_inode);
> + if (!task)
> + return -ESRCH;
> +
Ondrej Zajicek napsal(a):
This patch adds driver for S3 Trio / S3 Virge. Driver is tested
with most versions of S3 Trio and S3 Virge, on i386.
It is tested both as compiled-in and module. It is against
linux-2.6.20 .
This is version 3. There are some minor modifications from version 2
(mostly
On 9 Feb 2007, at 23:22, Andrew Morton wrote:
On Fri, 09 Feb 2007 14:53:44 -0800
Dave Hansen <[EMAIL PROTECTED]> wrote:
This is the core of the read-only bind mount patch set.
Who wants read-only bind mounts, and for what reason?
On our local mirror server (mirrors just under 3TiB worth of
Nigel Cunningham wrote:
Hi.
On Fri, 2007-02-09 at 23:17 +0100, Arjan van de Ven wrote:
On Sat, 2007-02-10 at 08:57 +1100, Nigel Cunningham wrote:
Hi.
I don't think this is already done (feel free to correct me if I'm
wrong)..
Can we start to NAK new drivers that don't have proper power
Commit 40b20c257a13c5a526ac540bc5e43d0fdf29792a by Len Brown introduced
a null pointer dereference in the appledisplay driver. This patch fixes
it.
Signed-off-by: Michael Hanselmann <[EMAIL PROTECTED]>
---
I suggest adding this to 2.6.20.1 because this bug causes the kernel to
panic on boot when
"The file system mounted on /tmp/z in the example contains 2^50
directories". heh.
I do wonder how realistic this problem is in real life.
That's a fair concern, although I was trying this as part
of evaluating how much someone could hose a system
if we let them mount arbitrary FUSE servers.
On Sat, 10 Feb 2007, Eric Dumazet wrote:
>
> Well, I guess if the original program was mono-threaded, and syscall used
> fget_light(), we might have a problem here if the child try a close(). So you
> may have to disable fget_light() magic if async call is the originator of the
> syscall.
Yes.
On Saturday, 10 February 2007 00:28, Nigel Cunningham wrote:
> Hi.
>
> On Sat, 2007-02-10 at 00:12 +0100, Rafael J. Wysocki wrote:
> > > > I think if CONFIG_PM_DEBUG is set, the core should warn about drivers
> > > > not
> > > > having .suspend or .resume routines.
> > >
> > > The only problem
On Sat, 2007-02-10 at 00:41 +0100, Eric Dumazet wrote:
> Dave, please read again this comment in struct vfsmount definition.
>
> If I understand your infrastructure, mnt=5Fwriters is going to be frequently
> modified, so it should be placed at the end of struct vfsmount, in the same
> cache line
Linus Torvalds a écrit :
Ok, here's another entry in this discussion.
- IF the system call blocks, we call the architecture-specific
"schedule_async()" function before we even get any scheduler locks, and
it can just do a fork() at that time, and let the *child* return to the
Dave Hansen a écrit :
@@ -56,6 +57,7 @@ struct vfsmount {
struct vfsmount *mnt_master;/* slave is on master->mnt_slave_list */
struct mnt_namespace *mnt_ns; /* containing namespace */
struct user_namespace *mnt_user_ns; /* namespace for uid interpretation
*/
+
On Fri, 09 Feb 2007 23:01:06 +0100
Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> From: Miklos Szeredi <[EMAIL PROTECTED]>
>
> The time shrink_dcache_parent() takes, grows quadratically with the
> depth of the tree under 'parent'. This starts to get noticable at
> about 10,000.
>
> These kinds of
On Fri, 2007-02-09 at 15:22 -0800, Andrew Morton wrote:
> On Fri, 09 Feb 2007 14:53:44 -0800
> Dave Hansen <[EMAIL PROTECTED]> wrote:
>
> > This is the core of the read-only bind mount patch set.
>
> Who wants read-only bind mounts, and for what reason?
The original desire came out of the
On Fri, 09 Feb 2007 18:35:51 -0500 Chuck Ebbert wrote:
> Andrew Morton wrote:
> > I have an email sitting in my drafts folder stating that I'll no longer
> > accept any features unless they've been publically reviewed in detail and
> > run-time tested by a third party. The idea being to force
Hi!
> > > Nigel Cunningham <[EMAIL PROTECTED]> writes:
> > >
> > > > - for (tracedata = &__tracedata_start ; tracedata <
> > > > &__tracedata_end ; tracedata += 6) {
> > > > + for (tracedata = &__tracedata_start ; tracedata <
> > > > &__tracedata_end ; tracedata += 2 +
Hi!
> Per your request, and the request of the distros, we've changed
> how ACPICA Core releases are integrated into Linux so that each
> upstream (CVS) check-in appears as a single git commit.
> While this process is not yet perfect, it should be vastly better
> than previous "code drops" in
On Wed 2007-02-07 09:25:39, Henrique de Moraes Holschuh wrote:
> On Wed, 07 Feb 2007, Nigel Cunningham wrote:
> > Ok, as far as usage scenario goes, that's fair enough. But as to the
> > solution, I wonder though whether it's making life more complicated than
> > it needs to be. After all, we
Hi!
> From: Maxim Levitsky <[EMAIL PROTECTED]>
> Subject: [PATCH] [NETDEV] [004] dmfe : Add suspend/resume support
>
> Adds support for suspend/resume
Patch looks ok, but your mailer damaged it heavily.
> --- linux-2.6.20-mod/drivers/net/tulip/dmfe.c 2007-02-07 18:46:13.0
> +0200
>
Yes- this would be interesting to know wrt to doing things like
PCI<>PCI xfers (e.g., for things like the Micromemory NVRAM card).
On 2/9/07, Kumar Gala <[EMAIL PROTECTED]> wrote:
We've been having a discussion on the linuxppc-dev list about how to
handle IO memory that exists on some PPC SoC
On Fri, 2007-02-09 at 17:33 -0600, Kumar Gala wrote:
> ideally all this would be handled via the dma mapping API, the
> question is how to convey to the API to use the IO memory vs the
> system memory? Should we look at adding a new GFP_IOMEM flag or do
> something based on struct device?
>
Andrew Morton wrote:
> I have an email sitting in my drafts folder stating that I'll no longer
> accept any features unless they've been publically reviewed in detail and
> run-time tested by a third party. The idea being to force people to spend
> more time reviewing and testing each other's
On Fri, 2007-02-09 at 12:49 -0500, Len Brown wrote:
> On Friday 09 February 2007 12:14, James Morris wrote:
> > This is being disabled in the guest kernel only. The host and guest
> > kernels are expected to be the same build.
>
> Okay, but better to use disable_acpi()
> indeed, since this
From: Al Viro <[EMAIL PROTECTED]>
Date: Fri, 09 Feb 2007 18:13:42 +
>
> Signed-off-by: Al Viro <[EMAIL PROTECTED]>
> ---
> include/linux/dn.h |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Also applied, thanks Al.
-
To unsubscribe from this list: send the line "unsubscribe
From: Al Viro <[EMAIL PROTECTED]>
Date: Fri, 09 Feb 2007 18:13:37 +
>
> Signed-off-by: Al Viro <[EMAIL PROTECTED]>
> ---
> net/decnet/dn_rules.c | 12 ++--
> 1 files changed, 6 insertions(+), 6 deletions(-)
Applied.
-
To unsubscribe from this list: send the line "unsubscribe
Date: Tue, 6 Feb 2007 02:34:45 +0100 (CET)
From: Stefan Richter <[EMAIL PROTECTED]>
Since my commit 8252bbb1363b7fe963a3eb6f8a36da619a6f5a65 in 2.6.20-rc1,
host devices have a dummy driver attached. Alas the driver was not
registered before use if ieee1394 was loaded with disable_nodemgr=1.
Date: Sat, 03 Feb 2007 03:09:09 -0500
From: David Moore <[EMAIL PROTECTED]>
This together with the phys_to_virt fix in lib/swiotlb.c::swiotlb_sync_sg
fixes video1394 DMA on machines with DMA bounce buffers, especially Intel
x86-64 machines with > 3GB RAM.
Signed-off-by: Stefan Richter <[EMAIL
On Fri, 2007-02-09 at 13:15 -0500, James Morris wrote:
> On Sat, 10 Feb 2007, Rusty Russell wrote:
>
> > +/* 64k ought to be enough for anybody! */
> > +#define HYPERVISOR_MAP_ORDER 16
> > +#define HYPERVISOR_PAGES ((1 << HYPERVISOR_MAP_ORDER)/PAGE_SIZE)
>
> I think it'd be better to go back to
Date: Sun, 04 Feb 2007 13:39:40 -0500
From: David Moore <[EMAIL PROTECTED]>
Adds missing call to phys_to_virt() in the
lib/swiotlb.c:swiotlb_sync_sg() function. Without this change, a kernel
panic will always occur whenever a SWIOTLB bounce buffer from a
scatter-gather list gets synced.
On Fri, 9 Feb 2007, Davide Libenzi wrote:
>
> That's another way to do it. But you end up creating/destroying a new
> thread for every request. May be performing just fine.
Well, I actually wanted to add a special CLONE_ASYNC flag, because I
think we could do it better if we know it's a
We've been having a discussion on the linuxppc-dev list about how to
handle IO memory that exists on some PPC SoC devices. These IO
memories behave like system memory but are faster to the processor or
device needed accessing for things like buffer descriptors.
Here's an example in which
> Yes. In fact, the current existing code does not handle dr6 correctly.
> It never clears the register, which means you're likely to get into
> trouble when multiple breakpoints (or watchpoints) are enabled.
This is a subtle change from the existing ABI, in which userland has to
clear %dr6
Hi.
On Sat, 2007-02-10 at 00:12 +0100, Rafael J. Wysocki wrote:
> > > I think if CONFIG_PM_DEBUG is set, the core should warn about drivers not
> > > having .suspend or .resume routines.
> >
> > The only problem with that is, not everyone turns on CONFIG_PM_DEBUG.
> > CONFIG_PM instead?
>
>
On Fri, 09 Feb 2007 14:53:44 -0800
Dave Hansen <[EMAIL PROTECTED]> wrote:
> This is the core of the read-only bind mount patch set.
Who wants read-only bind mounts, and for what reason?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Fri, 09 Feb 2007 14:53:29 -0800
Dave Hansen <[EMAIL PROTECTED]> wrote:
> +/*
> + * Note: This is a crappy interface. It is here to make
> + * merging with the existing users of get_empty_filp()
> + * who have complex failure logic easier. All users
> + * of this should be moving to
Hi,
On Friday, 9 February 2007 23:51, Nigel Cunningham wrote:
> Hi.
>
> On Fri, 2007-02-09 at 23:44 +0100, Rafael J. Wysocki wrote:
> > On Friday, 9 February 2007 23:26, Nigel Cunningham wrote:
> > > Hi.
> > >
> > > On Fri, 2007-02-09 at 23:17 +0100, Arjan van de Ven wrote:
> > > > On Sat,
On Fri, 9 Feb 2007, Linus Torvalds wrote:
>
> Ok, here's another entry in this discussion.
That's another way to do it. But you end up creating/destroying a new
thread for every request. May be performing just fine.
Another, even simpler way IMO, is to just have a plain per-task kthread
pool,
Hello.
On Sat, 2007-02-10 at 09:26, Neil Brown wrote:
> On Friday February 9, [EMAIL PROTECTED] wrote:
> >
> > Ok. Now... any questions?
> >
>
> Yes. Does this require a closed user-space helper like the other
> 3945ABG driver, or is it completely open (maybe excepting firmware)?
Quote from
A cleanup patch against 2.6.20 for saa7134 video4linux driver:
- use generic sort instead of bubblesort
- removed useless saa7134_video_fini function
- small coding style changes
Signed-off-by: Heikki Orsila <[EMAIL PROTECTED]>
--
Heikki Orsila Barbie's law:
[EMAIL
Some ioctls need write access, but others don't. Make a helper
function to decide when write access is needed, and take it.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/ncpfs/ioctl.c | 55 +-
1 file changed, 54 insertions(+), 1
chown/chmod,etc... don't call permission in the same way
that the normal "open for write" calls do. They still
write to the filesystem, so bump the write count during
these operations.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/open.c | 37
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c | 10 ++
1 file changed, 10 insertions(+)
diff -puN fs/namei.c~09-24-elevate-write-count-for-link-and-symlink-calls
fs/namei.c
--- lxc/fs/namei.c~09-24-elevate-write-count-for-link-and-symlink-calls
2007-02-09
This basically audits the callers of xattr_permission(), which
calls permission() and can perform writes to the filesystem.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/nfsd/nfs4proc.c |7 ++-
lxc-dave/fs/xattr.c | 14 ++
2 files changed, 20
This patch actually adds the mount and superblock writer
counts, and the mnt_want/drop_write() functions that use
them.
Before these can become useful, we must first cover each
place in the VFS where writes are performed with a
want/drop pair. When that is complete, we can actually
introduce
Now that we have the sb writer count, and all of the
writers marked with mnt_want_write(), we don't need to
go looking at all of the individual open files.
Kill the open files walk, and use the sb writer count.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/file_table.c|
Hello!
> void* comparisons are unsigned. Period.
As far as the C standard is concerned, there is no relationship between
comparison on pointers and comparison of their values casted to uintptr_t.
The address space needn't be linear and on some machines it isn't. So
speaking about signedness of
Some filesystems forego the use of normal vfs calls to create
struct files. Make sure that these users elevate the mnt writer
count. These probably don't have any real meaning because there
is no real backing store for these mounts, but it is here for
consistency.
Signed-off-by: Dave Hansen
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/inode.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff -puN fs/inode.c~17-24-elevate-write-count-for-do-sys-utime-and-touch-atime
fs/inode.c
---
This is the first really tricky patch in the series. It
elevates the writer count on a mount each time a
non-special file is opened for write.
This is not completely apparent in the patch because the
two if() conditions in may_open() above the
mnt_want_write() call are, combined, equivalent to
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/open.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff -puN fs/open.c~15-24-elevate-writer-count-for-do-sys-truncate fs/open.c
--- lxc/fs/open.c~15-24-elevate-writer-count-for-do-sys-truncate
This takes care of all of the direct callers of vfs_mknod().
Since a few of these cases also handle normal file creation
as well, this also covers some calls to vfs_create().
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c | 12
1 - 100 of 878 matches
Mail list logo
