Hi Rafael.
Probably you haven't got any answers yet because you should NEVER EVER
(i repeat: NEVER EVER, not even in college projects) go for file I/O in
the kernel. You might want to think the whole thing over one or two
times, i think.
If it comes to you that it is absolutely necessary (i
william cheng writes:
Dear all,
We got some problem on modprobing the ipmi_si module on Dell
Power Edge 2600.
On modprobing the ipmi_si the terminal hang and the process
cannot be terminated by control-C.
We got these messages in dmesg
ipmi
Hi
+static void __sched
+account_global_scheduler_latency(struct task_struct *tsk, int usecs)
+{
+ int i;
+ int firstnonnull = MAXLR + 1;
+
+ if (!tsk-latency_reason.reason)
+ return;
+
+ /* skip kernel threads for now */
+ if (!tsk-mm)
+
From: [EMAIL PROTECTED]
Date: Fri, 18 Jan 2008 10:29:54 -0800
percpu_modcopy() is defined multiple times in arch files. However, the only
user is module.c. Put a static definition into module.c and remove
the definitions from the arch files.
Cc: Rusty Russell [EMAIL PROTECTED]
Cc: Andi
On Mon, Jan 21, 2008 at 04:44:36PM +0800, Dave Young wrote:
...
I applied it in my kernel, built and run without warnings, but it need
more testing.
I will be very glad to see the test result about this if you could, thanks.
I'll try this of course, but alas I don't have anything such more
On Jan 21, 2008 4:36 PM, Jarek Poplawski [EMAIL PROTECTED] wrote:
On Mon, Jan 21, 2008 at 09:43:35AM +0800, Dave Young wrote:
...
Convert the class semaphore to mutex.
class_interface_register/unregister use class_device_* functions, so
SINGLE_DEPTH_NESTING added for lockdep please in
On Mon, Jan 21, 2008 at 09:43:35AM +0800, Dave Young wrote:
...
Convert the class semaphore to mutex.
class_interface_register/unregister use class_device_* functions, so
SINGLE_DEPTH_NESTING added for lockdep please in these functions.
Looks fine to me now, but... I think you forgot again
On Fri, 2008-01-18 at 14:29 -0800, David Brownell wrote:
EXPERIMENTAL and incomplete patch to make LOCKDEP behave better in
the face of irq chaining, by annotating irqs with a lock_class which
can reflect that hierarchy.
This is too short for me (who has no clue about genirq) to understand
I thought the effects of exit(0) and _exit(0) should be different.
int main(void)
{
int var = 0;
pid_t pid;
printf(before vfork\n);
if ( (pid = vfork()) 0 )
printf(error\n);
else if ( pid == 0 )
{
var++;
the original code use KOBJ_NAME_LEN for built-in module name length,
that's defined to 20 in linux/kobject.h, but this is not enough,
some module names(such as nf_conntrack_proto_icmp) are longer than this;
#define KOBJ_NAME_LEN 20
another macro is MODULE_NAME_LEN defined in
the original code use KOBJ_NAME_LEN for built-in module name length,
that's defined to 20 in linux/kobject.h, but this is not enough appearntly,
many module names are longer than this;
#define KOBJ_NAME_LEN 20
another macro is MODULE_NAME_LEN defined in linux/module.h, I think
On Thu, Jan 17, 2008 at 03:51:17PM +0800, Zhang Rui wrote:
From: Thomas Sujith [EMAIL PROTECTED]
Intel menlow platform specific driver for thermal management.
Signed-off-by: Thomas Sujith [EMAIL PROTECTED]
Signed-off-by: Zhang Rui [EMAIL PROTECTED]
---
drivers/misc/Kconfig| 10
On Fri, Jan 18, 2008 at 05:14:18PM -0800, Roland McGrath wrote:
+#define RUSAGE_LWP RUSAGE_THREAD /* Solaris name for same */
Please don't add this to the kernel header. If glibc really wants that
it can provide it in it's own headers.
--
To unsubscribe from this list: send the
From: Ryan O'Hara [EMAIL PROTECTED]
Remove read/write permission() checks from xattr operations.
VFS layer is already handling permission for xattrs via the
xattr_permission() call, so there is no need for gfs2 to
check permissions. Futhermore, using permission() for SELinux
xattrs ops is
From: Fabio Massimo Di Nitto [EMAIL PROTECTED]
The patch is a fix to abort mount if the mount.gfs* and possible
umount.* are missing from /sbin.
While we do what we can to guarantee that they are installed properly in
userland (CVS HEAD), we want to make sure that mount still aborts properly.
From: Steven Whitehouse [EMAIL PROTECTED]
We only care about the content of the jindex in two cases,
one is when we mount the fs and the other is when we need
to recover another journal. In both cases we have to update
the jindex anyway, so there is no point in updating it
periodically between
From: Bob Peterson [EMAIL PROTECTED]
This patch changes the /sys/fs/gfs2/s_id/id file to give the device
id major:minor rather than the s_id. That enables gfs2_tool to
match devices properly (by id, not name) when locating the tuning files.
Signed-off-by: Bob Peterson [EMAIL PROTECTED]
From: Steven Whitehouse [EMAIL PROTECTED]
This set of address space operations was missing a sync_page
operation.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/meta_io.c b/fs/gfs2/meta_io.c
index 01ef902..4b1aced 100644
--- a/fs/gfs2/meta_io.c
+++ b/fs/gfs2/meta_io.c
From: Steven Whitehouse [EMAIL PROTECTED]
Something changed in the upstream kernel, and it needs this
one-liner to allow ops_address.c to build.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/ops_address.c b/fs/gfs2/ops_address.c
index ae782d2..7353933 100644
---
From: Steven Whitehouse [EMAIL PROTECTED]
Just like ext3 we now have three sets of address space operations
to cover the cases of writeback, ordered and journalled data
writes. This means that the individual operations can now become
less complicated as we are able to remove some of the tests for
From: Wendy Cheng [EMAIL PROTECTED]
Fix a race condition where multiple glock demote requests are sent to
a node back-to-back. This patch does a check inside handle_callback()
to see whether a demote request is in progress. If true, it sets a flag
to make sure run_queue() will loop again to
Hi,
Here is the current GFS2 patch queue. You'll notice that this time
there are no DLM patches in this list. That is because the DLM team
are setting up their own git tree and this future DLM patches will
be sent directly by them rather than via the GFS2 tree.
Most of this set of patches is
On Mon, Jan 21, 2008 at 04:33:41PM +0900, Paul Mundt wrote:
On Sun, Jan 20, 2008 at 09:09:03PM +0100, Sam Ravnborg wrote:
diff --git a/include/asm-generic/vmlinux.lds.h
b/include/asm-generic/vmlinux.lds.h
index ded7ca2..e0a56fb 100644
--- a/include/asm-generic/vmlinux.lds.h
+++
On Fri, Jan 18, 2008 at 04:20:40PM +0900, Tejun Heo wrote:
aha152x.c and fdomain are built twice - once for the isa driver and
once for the PCMCIA one. Through #ifdefs, the compiled codes are
slightly different; thus, global symbols need to be given different
names depending on which flavor
On Thu, Jan 17, 2008 at 04:11:11PM -0800, Roland Dreier wrote:
- Neteffect nes driver. It's not terribly clean code but since
it's a new driver that is completely self-contained, I plan on
merging it and letting cleanups happen upstream.
New code should be better quality than old code,
From: Steven Whitehouse [EMAIL PROTECTED]
This cleans up the mmap() code path for GFS2 by implementing the
page_mkwrite function for GFS2. We are thus able to use the
generic filemap_fault function for our -fault() implementation.
This now means that shared writable mappings will be much more
From: Steven Whitehouse [EMAIL PROTECTED]
The i_cache was designed to keep references to the indirect blocks
used during block mapping so that they didn't have to be looked
up continually. The idea failed because there are too many places
where the i_cache needs to be freed, and this has in the
From: Steven Whitehouse [EMAIL PROTECTED]
Removes a field that is not used.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/incore.h b/fs/gfs2/incore.h
index 5662ff9..e53da7d 100644
--- a/fs/gfs2/incore.h
+++ b/fs/gfs2/incore.h
@@ -274,7 +274,6 @@ struct gfs2_inode {
From: Steven Whitehouse [EMAIL PROTECTED]
This adds a function gfs2_is_writeback() along the lines of the
existing gfs2_is_jdata() in order to clean up the code and make
the various tests for the inode mode more obvious. It also fixes
the PageChecked() logic where we were resetting the flag too
From: Steven Whitehouse [EMAIL PROTECTED]
As requested by Christoph, this patch cleans up GFS2's internal
read function so that it no longer uses the do_generic_mapping_read
function. This function is obsolete and GFS2 is the last user of it.
As a side effect the internal read code gets smaller
From: Steven Whitehouse [EMAIL PROTECTED]
This patch splits gfs2_writepage into separate functions for each of
the three cases: writeback, ordered and journalled. As a result
it becomes a lot easier to see what each one is doing. The common
code is moved into gfs2_writepage_common.
This fixes a
From: Steven Whitehouse [EMAIL PROTECTED]
This patch resolves a lock ordering issue where we had been getting
a transaction lock in the wrong order with respect to the page lock.
By using writepages rather than just writepage, it is then possible
to start a transaction before locking the page,
From: Steven Whitehouse [EMAIL PROTECTED]
This is an addendum to the new AOPs work which moves the point
at which we take the page lock so that we don't get it until
the last possible moment. This resolves a conflict between
starting transactions and the page lock.
Signed-off-by: Steven
From: Steven Whitehouse [EMAIL PROTECTED]
These haven't been used for some time, remove them.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/incore.h b/fs/gfs2/incore.h
index 82dfe9b..f7a50fe 100644
--- a/fs/gfs2/incore.h
+++ b/fs/gfs2/incore.h
@@ -412,9 +412,6 @@
From: Steven Whitehouse [EMAIL PROTECTED]
This call to reclaim glocks is not needed, and in particular we don't want it
in the fast path for locking glocks. The limit was entirely arbitrary anyway
and we can't expect users to adjust things like this, the remaining code will
do the right thing on
From: Steven Whitehouse [EMAIL PROTECTED]
Previously we were doing (write data, wait for data, write metadata, wait
for metadata). After this patch we so (write metadata, write data, wait for
data, wait for metadata) which should be more efficient.
Also I noticed that the drop_bh and xmote_bh
From: Steven Whitehouse [EMAIL PROTECTED]
The HIF_MUTEX and HIF_PROMOTE flags were set on the glock holders
depending upon which of the two waiters lists they were going to
be queued upon. They were then tested when the holders were taken
off the lists to ensure that the right type of holder was
From: David Teigland [EMAIL PROTECTED]
Use wait_event_interruptible() in the lock_dlm thread instead
of an open coded equivalent, and include a kthread_should_stop()
check in the wait test so we don't miss a kthread_stop().
Signed-off-by: David Teigland [EMAIL PROTECTED]
Signed-off-by: Steven
From: Steven Whitehouse [EMAIL PROTECTED]
The only reason for adding glocks to the journal was to keep track
of which locks required a log flush prior to release. We add a
flag to the glock to allow this check to be made in a simpler way.
This reduces the size of a glock (by 12 bytes on i386, 24
From: Steven Whitehouse [EMAIL PROTECTED]
This patch changes the counter which keeps track of the free
blocks in the journal to an atomic_t in preparation for the
following patch which will update the log reservation code.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git
From: Steven Whitehouse [EMAIL PROTECTED]
This means that we can mark gfs2_ail1_empty static and prepares
the way for further changes.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/daemon.c b/fs/gfs2/daemon.c
index 3731ab0..e519919 100644
--- a/fs/gfs2/daemon.c
+++
From: David Teigland [EMAIL PROTECTED]
Print error with log_error() to be consistent with others.
Signed-off-by: David Teigland [EMAIL PROTECTED]
Signed-off-by: Fabio M. Di Nitto [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/locking/dlm/mount.c
From: Fabio Massimo Di Nitto [EMAIL PROTECTED]
The issue is indeed UP vs SMP and it is totally random.
spin_is_locked() is a bad assertion because there is no correct answer on UP.
on UP spin_is_locked() has to return either one value or another, always.
This means that in my setup I am lucky
From: Steven Whitehouse [EMAIL PROTECTED]
This patch intriduces two new log thresholds:
o thresh1 is the point at which we wake up gfs2_logd due to the pinned
block count. It is initialised at mount time to 2/5ths of the size
of the journal. Currently it does not change during the course
From: Fabio Massimo Di Nitto [EMAIL PROTECTED]
Hi Steven,
Steven Whitehouse wrote:
Hi,
Now in the -nmw git tree. Thanks,
Steve.
On Wed, 2007-11-21 at 11:54 -0600, Ryan O'Hara wrote:
this patch introduces a bunch of build warnings by leaving around
struct inode *inode = ip-i_inode;
The
From: Fabio M. Di Nitto [EMAIL PROTECTED]
Signed-off-by: Fabio M. Di Nitto [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/eaops.c b/fs/gfs2/eaops.c
index 14fbd95..f114ba2 100644
--- a/fs/gfs2/eaops.c
+++ b/fs/gfs2/eaops.c
@@ -56,21 +56,6 @@ unsigned int
From: Wendy Cheng [EMAIL PROTECTED]
GFS2 supports two modes of locking - lock_nolock for single node filesystem
and lock_dlm for cluster mode locking. The gfs2 lock methods are removed from
file operation table for lock_nolock protocol. This would allow VFS to handle
posix lock and flock logics
From: Abhijith Das [EMAIL PROTECTED]
A certain scenario in the rename code path triggers a kernel BUG()
because it accidentally does recursive locking The first lock is
requested to unlink an already existing inode (replacing a file) and the
second lock is requested when the destination directory
From: Steven Whitehouse [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/ops_file.c b/fs/gfs2/ops_file.c
index db76ac1..2569c13 100644
--- a/fs/gfs2/ops_file.c
+++ b/fs/gfs2/ops_file.c
@@ -700,7 +700,6 @@ static void do_unflock(struct file *file, struct
From: David Teigland [EMAIL PROTECTED]
The fl_owner is that of lockd when posix locks arrive from nfs
clients, so it can't be used to distinguish between lock holders.
Use fl_pid as owner instead; it's the pid of the process on the
nfs client.
Signed-off-by: David Teigland [EMAIL PROTECTED]
From: Bob Peterson [EMAIL PROTECTED]
This patch is just a cleanup. Function gfs2_get_block() just calls
function gfs2_block_map reversing the last two parameters. By
reversing the parameters, gfs2_block_map() may be called directly
and function gfs2_get_block may be eliminated altogether.
Since
From: Steven Whitehouse [EMAIL PROTECTED]
An inequality was the wrong way around causing gfs2_logd to wake
up too often. This fixes it.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/log.c b/fs/gfs2/log.c
index 7f9ab89..9bece94 100644
--- a/fs/gfs2/log.c
+++
From: Bob Peterson [EMAIL PROTECTED]
This patch saves a little time when gfs2 writes to the journals by
keeping a mapping between logical and physical blocks on disk.
That's better than constantly looking up indirect pointers in
buffers, when the journals are several levels of indirection
(which
From: Bob Peterson [EMAIL PROTECTED]
This just eliminates an unused variable from the quota code.
Not likely to be a time saver.
Signed-off-by: Bob Peterson [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/quota.c b/fs/gfs2/quota.c
index 8b4c20c..60cc50f
From: Bob Peterson [EMAIL PROTECTED]
This patch eliminates the unneeded sd_statfs_mutex mutex but preserves
the ordering as discussed.
Signed-off-by: Bob Peterson [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/incore.h b/fs/gfs2/incore.h
index
From: Bob Peterson [EMAIL PROTECTED]
This is a small correction to my previously posted patch1.
It just changes a divide to a shift. It's faster and doesn't
introduce odd dependencies on 32-bit compiles.
Signed-off-by: Bob Peterson [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL
From: Steven Whitehouse [EMAIL PROTECTED]
The go_drop_th function is never called or referenced.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/incore.h b/fs/gfs2/incore.h
index 9a83429..c85f4fd 100644
--- a/fs/gfs2/incore.h
+++ b/fs/gfs2/incore.h
@@ -131,7 +131,6 @@
From: Steven Whitehouse [EMAIL PROTECTED]
To improve performance on NUMA, we use the VM's standard page
migration for writeback and ordered pages. Probably we could
also do the same for journaled data, but that would need a
careful audit of the code, so will be the subject of a later
patch.
From: Bob Peterson [EMAIL PROTECTED]
Here is a patch for the latest upstream GFS2 code:
The journal extent map needs to be initialized sooner than it
currently is. Otherwise failed mount attempts (e.g. not enough
journals, etc.) may panic trying to access the uninitialized list.
Signed-off-by:
From: Steven Whitehouse [EMAIL PROTECTED]
This patch fixes a couple of problems which affected the execution of files
on GFS2. The first is that there was a corner case where inodes were not
always uptodate at the point at which permissions checks were being carried
out, this was resulting in
From: Steven Whitehouse [EMAIL PROTECTED]
Although the values were all being calculated correctly, there was a
race in the assert due to the way it was using atomic variables. This
changes the value we assert on so that we get the same effect by testing
a different variable. This prevents the
From: Steven Whitehouse [EMAIL PROTECTED]
It is possible to reduce the size of GFS2 inodes by taking the i_alloc
structure out of the gfs2_inode. This patch allocates the i_alloc
structure whenever its needed, and frees it afterward. This decreases
the amount of low memory we use at the expense
From: Steven Whitehouse [EMAIL PROTECTED]
A missing offset in the calculation.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/log.c b/fs/gfs2/log.c
index 0833e27..40c51bf 100644
--- a/fs/gfs2/log.c
+++ b/fs/gfs2/log.c
@@ -336,7 +336,7 @@ static u64 log_bmap(struct
From: Bob Peterson [EMAIL PROTECTED]
This patch removes a vestigial variable i_spin from the gfs2_inode
structure. This not only saves us memory (30 of these in memory
for the oom test) it also saves us time because we don't have to
spend time initializing it (i.e. slightly better
From: Bob Peterson [EMAIL PROTECTED]
This is a small I/O performance enhancement to gfs2. (Actually, it is a rework
of
an earlier version I got wrong). The idea here is to check if the write extends
past the last block in the file. If so, the function can save itself a lot of
time and trouble
From: Steven Whitehouse [EMAIL PROTECTED]
The comparison was being made against the wrong quantity.
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/bmap.c b/fs/gfs2/bmap.c
index 4356cc2..e4effc4 100644
--- a/fs/gfs2/bmap.c
+++ b/fs/gfs2/bmap.c
@@ -1222,10 +1222,10 @@ int
From: Bob Peterson [EMAIL PROTECTED]
This patch fixes a minor typo. Surprisingly, it still compiled.
Signed-off-by: Bob Peterson [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/meta_io.c b/fs/gfs2/meta_io.c
index bc28bc6..99c7959 100644
---
From: Steven Whitehouse [EMAIL PROTECTED]
There was a bug in the truncation/invalidation race path for
-page_mkwrite for gfs2. It ought to return 0 so that the effect is the
same as if the page was truncated at any of the other points at which
the page_lock is dropped. This will result in the
From: Bob Peterson [EMAIL PROTECTED]
I spotted this bug while I was digging around. Looks like it could cause
a lockup in some rare error condition.
Signed-off-by: Bob Peterson [EMAIL PROTECTED]
Signed-off-by: Steven Whitehouse [EMAIL PROTECTED]
diff --git a/fs/gfs2/inode.c b/fs/gfs2/inode.c
From: Abhijith Das [EMAIL PROTECTED]
This patch allows gfs2 to perform journal recovery even if it is mounted
read-only. Strictly speaking, a read-only mount should not be writing to
the filesystem, but we do this only to perform journal recovery. A
read-only mount will fail if we don't recover
Greg KH [EMAIL PROTECTED] 19.01.08 02:28
On Fri, Jan 11, 2008 at 01:57:27AM -0700, Jan Beulich wrote:
The drivers picked just serve as examples (which I routinely build and
hence am able to easily verify), i.e. as before he patch doesn't change
all instances where 'const' could have been
On Sun, Jan 20, 2008 at 11:06:02PM +0100, Tomasz Chmielewski wrote:
Aren't you forgetting about CPUfreq governors? Which mean: use the
maximum CPU frequency when the system is busy, throttle down (or lower
voltage) when the system is idle.
So yes, throttling will save the battery.
Sam Ravnborg [EMAIL PROTECTED] writes:
On Mon, Jan 21, 2008 at 04:33:41PM +0900, Paul Mundt wrote:
so the ## is being taken directly rather than acting as a concatenation.
Strange...
I can reproduce with gcc 3.4.5 here - will fix.
The ## operator does not work with -traditional.
Andreas.
On Mon, Jan 21, 2008 at 11:29:52AM +0100, Andreas Schwab wrote:
Sam Ravnborg [EMAIL PROTECTED] writes:
On Mon, Jan 21, 2008 at 04:33:41PM +0900, Paul Mundt wrote:
so the ## is being taken directly rather than acting as a concatenation.
Strange...
I can reproduce with gcc 3.4.5 here -
On Mon, Jan 21, 2008 at 11:45:06AM +0100, Sam Ravnborg wrote:
On Mon, Jan 21, 2008 at 11:29:52AM +0100, Andreas Schwab wrote:
Sam Ravnborg [EMAIL PROTECTED] writes:
On Mon, Jan 21, 2008 at 04:33:41PM +0900, Paul Mundt wrote:
so the ## is being taken directly rather than acting as a
On Mon, Jan 21, 2008 at 11:47:45AM +0100, Sam Ravnborg wrote:
On Mon, Jan 21, 2008 at 11:45:06AM +0100, Sam Ravnborg wrote:
On Mon, Jan 21, 2008 at 11:29:52AM +0100, Andreas Schwab wrote:
Sam Ravnborg [EMAIL PROTECTED] writes:
On Mon, Jan 21, 2008 at 04:33:41PM +0900, Paul Mundt
From: Dave Young [EMAIL PROTECTED]
Date: Mon, 21 Jan 2008 12:54:01 +0800
Add people missed in cc-list.
Thanks Dave for your continued efforts on Bluetooth bugs like this.
Marcel, are you going to review/ACK/integrate/push-upstream/whatever
any of these Bluetooth patches?
It hasn't been
On Monday 21 January 2008 20:08:25 Denis Cheng wrote:
the original code use KOBJ_NAME_LEN for built-in module name length,
that's defined to 20 in linux/kobject.h, but this is not enough appearntly,
many module names are longer than this;
#define KOBJ_NAME_LEN 20
Thanks,
From: YOSHIFUJI Hideaki / 吉藤英明 [EMAIL PROTECTED]
Date: Sun, 20 Jan 2008 00:30:19 +0900 (JST)
In article [EMAIL PROTECTED] (at Sat, 19 Jan 2008 14:44:13 +0100 (CET)),
Jan Engelhardt [EMAIL PROTECTED] says:
From 84bccef295aa9754ee662191e32ba1d64edce2ba Mon Sep 17 00:00:00 2001
From: Jan
On Wed, 16 Jan 2008, Steven Rostedt wrote:
On Wed, 16 Jan 2008, Steven Rostedt wrote:
We modified mcount now, and it is derived from an objdump of glibc. So
this is most definitely a derived work from glibc. But glibc is licensed
as LGPL, which IIRC allows for non GPL to link to it.
I
On Monday 21 January 2008 09:17:30 Rusty Russell wrote:
On Monday 21 January 2008 00:00:52 Tejun Heo wrote:
What should be do are
* Check that the threadfn's argument fits into void *.
For everything but timer, you'll get a warning if the data isn't assignable
to a void *, so you get a
config option to add the git branch name to the automatically generated
version string.
If the current git branch name is not master then add the name to the
LOCALVERSION_AUTO version string.
The format will then be -name-g
Signed-off-by: Richard Kennedy [EMAIL PROTECTED]
---
Makefile
On Mon, Jan 21, 2008 at 07:52:57PM +0900, Paul Mundt wrote:
On Mon, Jan 21, 2008 at 11:47:45AM +0100, Sam Ravnborg wrote:
On Mon, Jan 21, 2008 at 11:45:06AM +0100, Sam Ravnborg wrote:
On Mon, Jan 21, 2008 at 11:29:52AM +0100, Andreas Schwab wrote:
Sam Ravnborg [EMAIL PROTECTED] writes:
Hi David.
Both patches looks ok, thanks a lot.
Andrew, please apply.
Acked-by: Evgeniy Polyakov [EMAIL PROTECTED]
--
Evgeniy Polyakov
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Fri, 2008-01-18 at 17:17 -0800, Linda Walsh wrote:
On my x86_64 machine, I got the following message
in log (kern = 2.6.23.14)
Jan 16 04:08:38 Astara kernel: BUG: MAX_LOCK_DEPTH too low!
Jan 16 04:08:38 Astara kernel: turning off the locking correctness
validator.
Have no idea what
moxa.c changes to MOXA_GET_CONF ioctl breaks moxaload (userspace
application for firmware download to MOXA Intellio CPU boards).
Attached (and included inline below) is a patch to solve a problem
introduced by changes to struct moxa_board_conf in drivers/char/moxa.c.
AFAICS from the changelogs,
Rusty Russell wrote:
On Monday 21 January 2008 09:17:30 Rusty Russell wrote:
On Monday 21 January 2008 00:00:52 Tejun Heo wrote:
What should be do are
* Check that the threadfn's argument fits into void *.
For everything but timer, you'll get a warning if the data isn't assignable
to a void
Thanks Joe for the answer! I will find another work around for my problem, then!
greetings, Rafael Sisto.
On Jan 21, 2008 5:21 AM, Joe [EMAIL PROTECTED] wrote:
Hi Rafael.
Probably you haven't got any answers yet because you should NEVER EVER
(i repeat: NEVER EVER, not even in college
On Mon, Jan 21, 2008 at 02:13:52PM +0900, Tejun Heo wrote:
In a nutshell, printk_header() lets you do the following atomically
(against other messages).
code:
printk(KERN_INFO ata1.00: , line0\nline1\nline2\n);
output:
6ata1.00: line0
6 line1
6 line2
I think
On Thu, Jan 17, 2008 at 08:32:52PM +0100, Andrea Arcangeli wrote:
To make this work we still need notification from the VM about memory
pressure [..]
Ok I thought some more at the aging issue of the hot kvm pages (to
prevent the guest-OS very-hot working set to be swapped out). So I now
hooked
Am Montag, 21. Januar 2008 schrieb Hans-Peter Jansen:
Hi,
after installation of 2.6.24-rc8 on a local server, the syslog gets
spammed with lockd: cannot monitor some client
grep 'lockd: cannot monitor' /var/log/messages | wc -l
136026
in 20 minutes! I restarted the offending client (with
On Mon, 21 Jan 2008, Esben Nielsen wrote:
Please, tell what in the license forbids me to make a global replacement
EXPORT_SYMBOL_GPL - EXPORT_SYMBOL and distribute the result?
If you want to distribute that code, the authors of that said code
may be able to challenge you in saying that you
On Mon, 2008-01-21 at 00:03 +0100, Hans-Peter Jansen wrote:
Hi,
after installation of 2.6.24-rc8 on a local server, the syslog gets spammed
with lockd: cannot monitor some client
grep 'lockd: cannot monitor' /var/log/messages | wc -l
136026
in 20 minutes! I restarted the offending
I would like to Thank everybody for the quick answers!!
I also want to apologise all the unnecessary noise done in the mailing
list, maybe it wasn't the right place to post (I must say it was worth
the posting). I got some nice ideas and advices...
Lastly, I would like to answer some questions,
Matthew Wilcox wrote:
On Mon, Jan 21, 2008 at 02:13:52PM +0900, Tejun Heo wrote:
In a nutshell, printk_header() lets you do the following atomically
(against other messages).
code:
printk(KERN_INFO ata1.00: , line0\nline1\nline2\n);
output:
6ata1.00: line0
6 line1
6
transmission failure as timeouts. Of course, if we're ticking the timer
while the command is not in flight, that's a bug. If there are cases
where 30 secs isn't enough, can you please point me to those reports?
I have been, in bugzilla - the raid failure example where old IDE
eventually
Alan Cox wrote:
transmission failure as timeouts. Of course, if we're ticking the timer
while the command is not in flight, that's a bug. If there are cases
where 30 secs isn't enough, can you please point me to those reports?
I have been, in bugzilla - the raid failure example where old
David Miller writes:
Yes, this semaphore thing is highly problematic. In the most crucial
areas where network driver consistency matters the most for ease of
understanding and debugging, the Intel drivers choose to be different
:-(
The way the napi_disable() logic breaks out from
From: Robert Olsson [EMAIL PROTECTED]
Date: Mon, 21 Jan 2008 14:27:13 +0100
Yes it works. e1000 tested for ~3 hours with high very high load and
interface up/down every 5:th sec. Without the patch the irq's gets
disabled within a couple of seconds
A resolute way of handling the
while IDE thinks that IRQ might be lost and complete the command if the
TF status register says so.
For PATA at least that makes a lot of sense. It would probably make the
Promise driver a lot more stable too.
It could be that the particular device doesn't raise IRQ on certain
error
1 - 100 of 876 matches
Mail list logo
