* Pavel Machek [EMAIL PROTECTED] [061206 14:12]:
From: Vladimir Ananiev [EMAIL PROTECTED]
Convert 1501-15xx in drivers omap code, so that sx1 can work.
Pushing this too to linux-omap.
Tony
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
* Pavel Machek [EMAIL PROTECTED] [061206 14:13]:
Fix too long lines in sound headers.
Pushing this too.
Tony
-
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
I'm also hitting this running at commit:
commit 7bf65382caeecea4ae7206138e92e732b676d6e5
Author: Andrew Morton [EMAIL PROTECTED]
Date: Fri Dec 8 02:41:14 2006 -0800
I was at 2.6.19, then merged up to Linus's tree Friday 12/8 and now I
hit this. I have 2 identical systems with one difference,
Fields of struct pipe_buf_operations have not a precise layout (ie not
optimized to fit cache lines nor reduce cache line ping pongs)
The bufs[] array is *large* and is placed near the beginning of the structure,
so all following fields have a large offset. This is unfortunate because many
Hi
I've got a card that presents a PCIe to PCI transparent
bridge to the slot connector - behind which is a non
transparent bridge with 3 bars - 1 non prefetchable,
2 prefetchable. The non prefetchable is not assigned
after boot on some machines. It seems that if resource
allocation fails on
On Mon, 11 Dec 2006 21:44:34 +0100
Eric Dumazet [EMAIL PROTECTED] wrote:
Andrew Morton a __crit :
hm, the patch seems to transform a mess into a mess. I guess it's a messy
problem.
I agree that aggregating all the time-related things into a struct like
this makes some sense. As
Hi David,
See also Andrew Victor's patch (dated 04/Dec/2006) in the
linux-2.6-watchdog tree. It's indeed the at91rm9200_wdt, the mpcore_wdt
and the omap_wdt that are affected by the miscdev changes
I was just following the fix brown paper bags ASAP policy.
One that seems followed less
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Piel wrote:
12/09/2006 09:03 PM, Kyle McMartin wrote/a écrit:
On Sat, Dec 09, 2006 at 02:34:47PM -0500, John Richard Moser wrote:
I have filed this as a distro bug with Ubuntu; it may be their issue, I
haven't dug deep enough to find out.
Linus Torvalds writes:
On Mon, 11 Dec 2006, Olaf Hering wrote:
arch/powerpc/boot/wrapper:156:version=`${CROSS}strings $kernel | grep
'^Linux version [-0-9.]' | \
This is also obviously broken (and really sad), but actually ends up being
better than what get_kernel_version
On Tue, Dec 12, 2006 at 07:28:23AM +1100, Benjamin Herrenschmidt wrote:
Same here, btw - except that I couldn't catch the exact message as
nicely.
Yeah, fixed in the patch I sent yesterday [PATCH] powerpc: Fix irq
routing on some PowerMac 32 bit.
Confirmed, everything is fine with that
On Sunday 10 December 2006 10:27 pm, Voipio Riku wrote:
Update the rtc-rs5c372 driver:
I suspect the
issue wasn't that mode 1 didn't work on that board; the original
code to fetch the trim was broken. If mode 1 really won't work,
that's almost certainly a bug in that board's I2C
Hi,
since at least 2.6.18, my ISDN card has given me this error in dmesg:
ISDN subsystem Rev: 1.1.2.3/1.1.2.3/1.1.2.2/1.1.2.3/none/1.1.2.2
PPP BSD Compression module registered
HiSax: Linux Driver for passive ISDN cards
HiSax: Version 3.5 (kernel)
HiSax: Layer1 Revision 2.46.2.5
HiSax: Layer2
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
It caused all of the md RAID1s on my test box to
Stephane,
This patch has the same race as in 64 bit patch, that was fixed here
http://www.ussg.iu.edu/hypermail/linux/kernel/0611.3/1264.html
With that race, idle callbacks does not work correctly. Even on a
totally idle system, I can see exit_idle called before enter_idle once
every few
Linus Torvalds wrote:
On Mon, 11 Dec 2006, Andy Whitcroft wrote:
I am afraid to report that this second version also fails for me, as you point
out CIFS can break us if defined.
Olaf, will you admit that the SLES9 code is crap now?
Andy, does just replacing the __initdata with const fix it
On Monday December 11, [EMAIL PROTECTED] wrote:
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
Some subsystems dont need more than 32bits timestamps.
See for example net/ipv4/inetpeer.c and include/net/tcp.h :
#define tcp_time_stamp((__u32)(jiffies))
Because most timeouts should work with 'normal jiffies' that are 32bits on
32bits platforms, it makes sense to be able to use
Hello, list,
I am the big red button men with the one big 14TB xfs, if somebody can
remember me. :-)
Now i found something in the 2.6.16.18, and try the 2.6.18.4, and the
2.6.19, but the bug still exists:
Dec 11 22:47:21 dy-base BUG: spinlock bad magic on CPU#3, xfslogd/3/317
Dec 11 22:47:21
On Mon, 11 Dec 2006, Andrea Arcangeli wrote:
On Mon, Dec 11, 2006 at 01:17:25PM -0800, dean gaudet wrote:
rdtscp doesn't solve anything extra [..]
[..] lsl-based vgetcpu is relatively slow
Well, if you accept to run slow there's nothing to solve in the first
place indeed.
If nothing
Christoph Lameter wrote:
Ahh. Fallback_alloc() does not do the check for GFP_WAIT as done in
cache_grow(). Thus interrupts are disabled when we call kmem_getpages()
which results in the failure.
Duplicate the handling of GFP_WAIT in cache_grow().
Jay could you try this patch?
The patch
On Wed, 6 Dec 2006 16:59:04 +
Andy Whitcroft [EMAIL PROTECTED] wrote:
This is a repost of the lumpy reclaim patch set. This is
basically unchanged from the last post, other than being rebased
to 2.6.19-rc2-mm2.
The patch sequencing appeared to be designed to make the code hard to
review,
On 12/11/06, Voipio Riku [EMAIL PROTECTED] wrote:
snip
Have you asked around for anyone who may have insights about i2c-iop3xx
driver bugs? Maybe the driver maintainers, or arm-linux folk, or on
the i2c list.
I was told to contact Dan Williams, I didn't get any response.
Hi Riku, this is
On Mon, Dec 11, 2006 at 03:15:44PM -0800, dean gaudet wrote:
rdtscp gets you 2 of the 5 values you need to compute the time. anything
can happen between when you do the rdtscp and do the other 3 reads: the
computation is (((tsc-A)*B)N)+C where N is a constant, and A, B, C are
per-cpu
On Monday, 11 December 2006 23:52, Neil Brown wrote:
On Monday December 11, [EMAIL PROTECTED] wrote:
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
--- Trond Myklebust [EMAIL PROTECTED] wrote:
On Mon, 2006-12-11 at 08:09 -0800, Martin Knoblauch wrote:
Hi, [please CC me, as I am not subscribed]
after updating a RHEL4 box (EM64T based) to a plain 2.6.19 kernel,
we
are seeing repeated occurences of the following messages (about
On Sat, 2006-12-09 at 18:34 -0800, Pete Zaitcev wrote:
On Sat, 9 Dec 2006 15:09:13 -0600, Erik Jacobson [EMAIL PROTECTED] wrote:
Please try to declare u64 timestamp_ns, then copy it into the *ev
instead of copying whole *ev. This ought to fix the problem if
buffer[] ends aligned to 32
On Thu, 2006-12-07 at 17:22 -0600, Erik Jacobson wrote:
On ia64, the various functions that make up cn_proc.c cause kernel
unaligned access errors.
If you are using these, for example, to get notification about
all tasks forking and exiting, you get multiple unaligned access errors
per
On 12/11/06, Franck Bui-Huu [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
+ atomic_t ref_count;
+ atomic_t vma_count;
what purpose do these counters deserve ?
You are right. I can remove them.
+
+void hcb_wait_for_ack(struct hecubafb_par *par)
+{
+
+ int timeout;
+
On Tuesday December 12, [EMAIL PROTECTED] wrote:
On Monday, 11 December 2006 23:52, Neil Brown wrote:
On Monday December 11, [EMAIL PROTECTED] wrote:
Hi,
On Monday, 11 December 2006 09:58, Andrew Morton wrote:
Temporarily at
Signed-off-by: Kyle McMartin [EMAIL PROTECTED]
diff --git a/arch/i386/mm/init.c b/arch/i386/mm/init.c
index 84697df..fb61709 100644
--- a/arch/i386/mm/init.c
+++ b/arch/i386/mm/init.c
@@ -512,6 +512,9 @@ void __init paging_init(void)
set_nx();
if (nx_enabled)
From: Paul Mackerras [EMAIL PROTECTED]
Date: Tue, 12 Dec 2006 09:04:41 +1100
If there is a reliable way to get the version string, great, I'll use
that.
FWIW, on sparc and sparc64 we have this information block for
the boot loader.
The first two instructions at the entry point simply branch
Appended patch attempts to fix the process idle load balancing in the
presence of dynticks. cpus for which ticks are stopped will sleep
till the next event wakes it up. Potentially these sleeps can be for large
durations and during which today, there is no idle load balancing being done.
There was
On Mon, 2006-12-11 at 15:44 -0800, Martin Knoblauch wrote:
So far, we are only seeing it on amd-mounted filesystems, not on
static NFS mounts. Unfortunatelly, it is difficult to avoid amd in
our environment.
Any chance you could try substituting a recent version of autofs? This
sort of
So it makes perfect sense to say
you won't be getting any notification by anything built-in, until
'device_initcall' (which is the default module_init, of course).
which in the case of certain drivers obviously _does_ mean that they had
better not try to use any early initcalls
Hi,
Please cc your reply to my email. many thanks
I would appreciate any help on the following
questions.
I have looked on disk scheduling algorithms
http://www.cs.princeton.edu/courses/archive/fall06/cos318/lectures/disks.pdf
and the main thing that striked me is that most of the
algorithms
Albert Cahalan wrote:
David Singleton writes:
Add variation of /proc/PID/smaps called /proc/PID/pagemaps.
Shows reference counts for individual pages instead of aggregate totals.
Allows more detailed memory usage information for memory analysis tools.
An example of the output shows the shared
From: Eric Dumazet [EMAIL PROTECTED]
Date: Mon, 11 Dec 2006 23:58:06 +0100
Some subsystems dont need more than 32bits timestamps.
See for example net/ipv4/inetpeer.c and include/net/tcp.h :
#define tcp_time_stamp((__u32)(jiffies))
Because most timeouts should work with
On Mon, 11 Dec 2006 15:52:47 -0800, Matt Helsley [EMAIL PROTECTED] wrote:
I'm shocked memcpy() introduces 8-byte stores that violate architecture
alignment rules. Is there any chance this a bug in ia64's memcpy()
implementation? I've tried to read it but since I'm not familiar with
ia64
I'm worried by this... At no point do you check the host bridge
capabilities, and thus will happily set the max read req size to some
value larger than the max the host bridge can cope...
Well, it's disabled by default... the option is there as a quick way
to fix why is my bandwidth so low
From: Pete Zaitcev [EMAIL PROTECTED]
Date: Mon, 11 Dec 2006 17:29:07 -0800
On Mon, 11 Dec 2006 15:52:47 -0800, Matt Helsley [EMAIL PROTECTED] wrote:
I'm shocked memcpy() introduces 8-byte stores that violate architecture
alignment rules. Is there any chance this a bug in ia64's
Actually even PCIe might not be that easy. For example with current
kernels on PowerPC 440SPe (SoC with PCIe), I just get:
# lspci
00:01.0 InfiniBand: Mellanox Technology: Unknown device 6274 (rev a0)
ie no host bridge / root complex.
Did somebody used the spec as toilet paper
Pete Zaitcev wrote on Monday, December 11, 2006 5:29 PM
On Mon, 11 Dec 2006 15:52:47 -0800, Matt Helsley [EMAIL PROTECTED] wrote:
I'm shocked memcpy() introduces 8-byte stores that violate architecture
alignment rules. Is there any chance this a bug in ia64's memcpy()
implementation?
On Mon, 11 Dec 2006 08:01:40 -0800 (PST)
Linus Torvalds [EMAIL PROTECTED] wrote:
On Mon, 11 Dec 2006, Al Viro wrote:
On Mon, Dec 11, 2006 at 02:27:46AM -0800, Andrew Morton wrote:
@@ -115,6 +115,11 @@ extern void setup_arch(char **);
#define device_initcall_sync(fn)
On Mon, Dec 11, 2006 at 06:08:22PM -0800, Andrew Morton wrote:
diff --git a/include/linux/init.h b/include/linux/init.h
index 5eb5d24..5a593a1 100644
--- a/include/linux/init.h
+++ b/include/linux/init.h
@@ -111,6 +111,7 @@ extern void setup_arch(char **);
#define
Martin A. Fink wrote:
Compared to ICH6R with AHCI OFF the only difference I can see is that with
AHCI the system seems to reac much faster on keyboard events and screen
redraw seems to be as fast as normal. It looks like that CPU usage has not
decreased that dramatically as I would have
On Mon, 11 Dec 2006, Andrew Morton wrote:
Looks like this might break pcmcia which for some reason does firmware
requesting at fs_initcall level (drivers/pcmcia/ds.c).
Ok, that's just strange.
I think it's fine to do init_pcmcia_bus early to make sure that the PCMCIA
bus interface is
On second thought, this is probably better since most people will
presumably be booting non-PAE kernels, generating this message when
they've not tried to force the issue seems silly.
This way, the user will only see a warning if they actually go
out and specify noexec=on on the command line.
On Mon, 2006-12-11 at 17:50 -0800, David Miller wrote:
From: Pete Zaitcev [EMAIL PROTECTED]
Date: Mon, 11 Dec 2006 17:29:07 -0800
On Mon, 11 Dec 2006 15:52:47 -0800, Matt Helsley [EMAIL PROTECTED] wrote:
I'm shocked memcpy() introduces 8-byte stores that violate architecture
--- Trond Myklebust [EMAIL PROTECTED] wrote:
On Mon, 2006-12-11 at 15:44 -0800, Martin Knoblauch wrote:
So far, we are only seeing it on amd-mounted filesystems, not on
static NFS mounts. Unfortunatelly, it is difficult to avoid amd
in
our environment.
Any chance you could try
On Mon, 11 Dec 2006, Alan wrote:
On Sun, 10 Dec 2006 19:23:54 -0600
Corey Minyard [EMAIL PROTECTED] wrote:
Nothing has come of this yet. But we have these two requests and a
request from Russell Doty at Redhat.
It would be nice to know if this type of thing was acceptable or not,
On Mon, 11 Dec 2006, Neil Brown wrote:
this nash thing is exactly the command which triggers a bit different
oops in my case. On my side, the oops is fully reproducible. If you
manage to make your case also reproducible, could you please try to
revert
On Mon, 11 Dec 2006, Alan wrote:
there as protocols for user-tty interfaces, i.e., you need a user, that
opens a tty, sets a line discipline to it, and does io (read/write) over
it, and NOT to be completely initialised and driven from the kernel.
Take a look at the SLIP driver. User
Seth Arnold wrote:
On Fri, Dec 08, 2006 at 01:36:57PM -0600, Serge E. Hallyn wrote:
The other is that root can lose capabilities by executing files with
only some capabilities set. The next two patches change these
behaviors.
I saw this in my code review and thought that this
### Comments for Changeset
Thanks Jens for alerting me to this.
Cc: Jens Axboe [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Signed-off-by: Neil Brown [EMAIL PROTECTED]
### Diffstat output
./drivers/md/faulty.c |2 +-
./drivers/md/raid1.c |2 +-
./drivers/md/raid10.c |6 +++---
On Monday December 11, [EMAIL PROTECTED] wrote:
On Mon, 11 Dec 2006, Neil Brown wrote:
this nash thing is exactly the command which triggers a bit different
oops in my case. On my side, the oops is fully reproducible. If you
manage to make your case also reproducible, could you
On Mon, 11 Dec 2006, Mauro Carvalho Chehab wrote:
Please pull 'master' from:
git://git.kernel.org:/pub/scm/linux/kernel/git/mchehab/v4l-dvb.git
master
It fixes a breakage when compiling on ia64.
I get Already up-to-date.
Did you forget to push out again?
Linus
The previous checkstack fix for UML, which needs to use the host's tools,
was wrong in the crossbuilding case. It would use the build host's,
rather than the target's, toolchain.
This patch removes the old fix and adds an explicit special case for UML,
leaving everyone else alone.
to keep the amount of code between ll and sc to an absolute minimum
to avoid interference which causes livelock. Processor timeouts
are generally much longer than any reasonable code sequence.
Generally does not mean you can just ignore it and hope the C compiler
does the right thing. Nor
From: Matt Helsley [EMAIL PROTECTED]
Date: Mon, 11 Dec 2006 19:09:16 -0800
Hmm, that GCC assumption conflicts with the prototypes of memcpy() I've
seen.
When GCC expands __builtin_memcpy() internally it looks at the types
of the arguments, and what it knows about their guarenteed alignment.
David Miller a écrit :
From: Eric Dumazet [EMAIL PROTECTED]
Date: Mon, 11 Dec 2006 23:58:06 +0100
Some subsystems dont need more than 32bits timestamps.
See for example net/ipv4/inetpeer.c and include/net/tcp.h :
#define tcp_time_stamp((__u32)(jiffies))
Because most timeouts
From: Eric Dumazet [EMAIL PROTECTED]
Date: Tue, 12 Dec 2006 04:47:14 +0100
I doubt being able to extend the expiration of a dst above 2^32
ticks (49 days if HZ=1000, 198 days if HZ=250) is worth the ram
wastage.
And this doesn't apply for all jiffies uses because? :-)
That's the point I'm
David Miller a écrit :
From: Eric Dumazet [EMAIL PROTECTED]
Date: Tue, 12 Dec 2006 04:47:14 +0100
I doubt being able to extend the expiration of a dst above 2^32
ticks (49 days if HZ=1000, 198 days if HZ=250) is worth the ram
wastage.
And this doesn't apply for all jiffies uses because? :-)
From: Eric Dumazet [EMAIL PROTECTED]
Date: Tue, 12 Dec 2006 05:09:23 +0100
We definitly *like* being able to use bigger timeouts on 64bits platforms.
Not that they are mandatory since the same application should run fine on
32bits kernel. But as the standard type for 'tick timestamps' is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I tried building the new kernel and ran into this bug:
WARNING: kernel_sendmsg [fs/dlm/dlm.ko] undefined!
WARNING: sock_release [fs/dlm/dlm.ko] undefined!
WARNING: config_item_put [fs/dlm/dlm.ko] undefined!
WARNING: sock_create_kern [fs/dlm/dlm.ko]
On Mon, 11 Dec 2006 00:58:07 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
When I use ftp on 2.6.19-mm1,
On Tue, 12 Dec 2006 14:53:41 +0900
KAMEZAWA Hiroyuki [EMAIL PROTECTED] wrote:
On Mon, 11 Dec 2006 00:58:07 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
On Mon, Dec 11, 2006 at 10:24:02AM +0100, Karsten Weiss wrote:
We could not reproduce the data corruption anymore if we boot the
machines with the kernel parameter iommu=soft i.e. if we use
software bounce buffering instead of the hw-iommu. (As mentioned
before, booting with mem=2g works
From: Keiichi KII [EMAIL PROTECTED]
The netconsole is a very useful module for collecting kernel message under
certain circumstances(e.g. disk logging fails, serial port is unavailable).
But current netconsole is not flexible. For example, if you want to change ip
address for logging agent, in
Andrew Morton [EMAIL PROTECTED] writes:
On Mon, 11 Dec 2006 16:34:27 +0300
Dmitriy Monakhov [EMAIL PROTECTED] wrote:
OpenVZ team has discovered error inside generic_file_direct_write()
If generic_file_direct_IO() has fail (ENOSPC condition) it may have
instantiated
a few blocks outside
From: Keiichi KII [EMAIL PROTECTED]
This patch contains the following cleanups.
- add __init for initialization functions(option_setup() and
init_netconsole()).
- define name of magic number.
Signed-off-by: Keiichi KII [EMAIL PROTECTED]
---
--- linux-2.6.19/drivers/net/netconsole.c
From: Keiichi KII [EMAIL PROTECTED]
This patch contains the following changes.
create a sysfs entry for netconsole in /sys/class/misc.
This entry has elements related to netconsole as follows.
You can change configuration of netconsole(writable attributes such as IP
address, port number and so
From: Keiichi KII [EMAIL PROTECTED]
This patch contains switch function of netpoll.
if enable attribute of certain port is '1', this port is used.
if enable attribute of certain port is '0', this port isn't used.
active_netconsole_dev list manages a list of active ports.
inactive_netconsole_dev
G'day. One of the machines I maintain is having real trouble with the
AIC79XX HBA or the tape drive attached to it. I believe this is a
hardware fault, but I am not certain where the problem lies.
Normally I would blame the cable or, maybe, the tape drive, but the
early stage of the fault and
From: Keiichi KII [EMAIL PROTECTED]
This patch contains the following changes.
To add port dynamically, create add element in /sys/class/misc/netconsole.
ex)
1. echo eth0 /sys/clas/misc/netconsole/add
then the port is added with the default settings.
2. echo @/eth0,@192.168.0.1/
From: Keiichi KII [EMAIL PROTECTED]
Update modification history.
Signed-off-by: Keiichi KII [EMAIL PROTECTED]
---
--- linux-2.6.19/drivers/net/netconsole.c 2006-12-12 14:57:45.588967500
+0900
+++ enhanced-netconsole/drivers/net/netconsole.c.sign 2006-12-12
14:54:49.541965250 +0900
@@
On Tue, 12 Dec 2006 12:22:14 +0300
Dmitriy Monakhov [EMAIL PROTECTED] wrote:
@@ -2041,6 +2041,14 @@ generic_file_direct_write(struct kiocb *
mark_inode_dirty(inode);
}
*ppos = end;
+ } else if (written 0) {
+ loff_t isize =
On Mon, 11 Dec 2006 22:06:17 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
When I use ftp on 2.6.19-mm1, transfered file is always broken.
like this:
==
[EMAIL PROTECTED] ~]$ file ./linux-2.6.19.tar.bz2 (got on 2.6.19-mm1)
./linux-2.6.19.tar.bz2: data
(I confirmed original file was not
This bug started to show up after the release of 2.6.19 (iirc plain 2.6.19
was still working fine).
The full dmesg is at
http://www.bencastricum.nl/lk/bootmessages-2.6.19-g9202f325.log,
and the .config http://www.bencastricum.nl/lk/config-g9202f325.log
I haven't tried disabling
David Miller a écrit :
From: Eric Dumazet [EMAIL PROTECTED]
Date: Tue, 12 Dec 2006 05:09:23 +0100
We definitly *like* being able to use bigger timeouts on 64bits platforms.
Not that they are mandatory since the same application should run fine on
32bits kernel. But as the standard type for
On Mon, Dec 11, 2006 at 12:58:07AM -0800, Andrew Morton wrote:
...
Changes since 2.6.19-rc6-mm2:
...
git-ocfs2.patch
...
git trees.
...
This patch makes needlessly global code static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
fs/ocfs2/cluster/tcp.c |2 +-
Hi Adrian,
On Mon, Dec 11, 2006 at 08:10:01PM +0100, Adrian Bunk wrote:
On Mon, Dec 11, 2006 at 12:58:07AM -0800, Andrew Morton wrote:
...
Changes since 2.6.19-rc6-mm2:
...
git-ocfs2.patch
...
git trees.
...
This patch makes needlessly global code static.
Signed-off-by: Adrian
Before:
[EMAIL PROTECTED] kpahole-2.6]$ pahole --cacheline 32 /tmp/scsi.o.before
scsi_target
/* include/scsi/scsi_device.h:86 */
struct scsi_target {
struct scsi_device * starget_sdev_user;/* 0 4 */
struct list_head siblings; /* 4 8
On Tue, Dec 12, 2006 at 01:17:18AM -0200, Arnaldo Carvalho de Melo wrote:
}; /* size: 368, cachelines: 12 */
}; /* size: 364, cachelines: 12 */
Saving space is always good ;-)
- unsigned intcreate:1; /* signal that it needs to be added */
+ char
On Mon, Dec 11, 2006 at 12:58:07AM -0800, Andrew Morton wrote:
...
Changes since 2.6.19-rc6-mm2:
...
git-acpi.patch
...
git trees.
...
This patch makes needlessly global code static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
drivers/acpi/bus.c |2 +-
On Sat, 9 Dec 2006 12:59:58 +0100
Holger Macht [EMAIL PROTECTED] wrote:
Well, I like to have them ;-)
Ok - how is this?
Send a uevent to indicate a device change whenever we dock or
undock, so that userspace may now check the dock status via
sysfs.
Signed-off-by: Kristen Carlson Accardi
On Mon, Dec 04, 2006 at 11:06:41AM -0500, Alan Stern wrote:
On Mon, 4 Dec 2006, Maneesh Soni wrote:
hmm, I guess Greg has to say the final word. The question is either to fail
the IO (-ENODEV) or fail the file removal (-EBUSY). If we are not going to
fail the removal then your patch is
On Mon, Dec 11, 2006 at 04:13:06PM +0530, Maneesh Soni wrote:
On Mon, Dec 04, 2006 at 11:06:41AM -0500, Alan Stern wrote:
On Mon, 4 Dec 2006, Maneesh Soni wrote:
hmm, I guess Greg has to say the final word. The question is either to
fail
the IO (-ENODEV) or fail the file removal
On Thu, 7 Dec 2006, Peter Stuge wrote:
On Wed, Dec 06, 2006 at 01:08:14PM -0800, Lu, Yinghai wrote:
-Original Message-
From: Andi Kleen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 06, 2006 12:59 PM
I haven't looked how the other usb_debug works -- if it's polled
too
Hi Andi,
What problem do they cause together? There's certainly no problem with
Xen+vdso (in fact, its actually very useful so that it picks up the
right libc with Xen-friendly TLS).
J
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Jeremy Fitzhardinge wrote:
Hi Andi,
What problem do they cause together? There's certainly no problem with
Xen+vdso (in fact, its actually very useful so that it picks up the
right libc with Xen-friendly TLS).
Methinks the compat VDSO support got broken in the config? Paravirt +
Zachary Amsden wrote:
Jeremy Fitzhardinge wrote:
Hi Andi,
What problem do they cause together? There's certainly no problem with
Xen+vdso (in fact, its actually very useful so that it picks up the
right libc with Xen-friendly TLS).
Methinks the compat VDSO support got broken in the
Jeremy Fitzhardinge wrote:
Zachary Amsden wrote:
Jeremy Fitzhardinge wrote:
Hi Andi,
What problem do they cause together? There's certainly no problem with
Xen+vdso (in fact, its actually very useful so that it picks up the
right libc with Xen-friendly TLS).
Methinks the
Zachary Amsden wrote:
It's not for us or Xen. Perhaps it came from lhype?
(I suspect it came from Andi's fevered brain.) If lhype can't deal with
vdso, it can turn it off for itself - but I don't think its a problem
for lhype.
J
-
To unsubscribe from this list: send the line unsubscribe
piix_init_one() allocates host private data which should be freed by
piix_host_stop(). ich_pata_ops wasn't converted to piix_host_stop()
while merging, leaking 4 bytes on driver detach. Fix it.
This was spotted using Kmemleak by Catalin Marinas.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
Cc:
Benjamin Herrenschmidt wrote:
Could that be related to the fix
[PATCH] libata: fix oops with sparsemem
That Arnd Bergmann just posted ? I'm copying it below in case you
haven't seen it.
Seems to be the same problem to me. I'll reply in the original thread.
Thanks.
--
tejun
-
To
Calling sg_init_one() with NULL buf causes oops on certain
configurations. Don't initialize sg in ata_exec_internal() if
DMA_NONE and make the function complain if @buf is NULL when dma_dir
isn't DMA_NONE. While at it, fix comment.
The problem is discovered and initial patch was submitted by
On Mon, 11 Dec 2006 22:26:25 +0900
Tejun Heo [EMAIL PROTECTED] wrote:
piix_init_one() allocates host private data which should be freed by
piix_host_stop(). ich_pata_ops wasn't converted to piix_host_stop()
while merging, leaking 4 bytes on driver detach. Fix it.
This was spotted using
Tejun Heo wrote:
I'll follow up with conversion to ata_do_simple_cmd().
The current situation is...
ata_exec_internal_sg() : no user except for ata_exec_internal() yet
ata_exec_internal() : one data transferring user. other are non-data
ata_do_simple_cmd() : three users
So, adding
Arnd Bergmann wrote:
On Monday 11 December 2006 15:02, Tejun Heo wrote:
{
struct scatterlist sg;
+ unsigned int n_elem = 0;
- sg_init_one(sg, buf, buflen);
+ if (dma_dir != DMA_NONE) {
+ WARN_ON(!buf);
+ sg_init_one(sg, buf, buflen);
+
Tejun Heo wrote:
Calling sg_init_one() with NULL buf causes oops on certain
configurations. Don't initialize sg in ata_exec_internal() if
DMA_NONE and make the function complain if @buf is NULL when dma_dir
isn't DMA_NONE. While at it, fix comment.
The problem is discovered and initial patch
601 - 700 of 739 matches
Mail list logo
