[lkml]   [2000]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: lowlatency-2.2.14-B1 + 2.2.14aa7 fixes crash, but...
On Tue, 22 Feb 2000, Ingo Molnar wrote:

>[..] "likely to be a bug in
>the lowlatency patch, but we simply do not know for sure, yet.". [..]

Correct. What I meant is that it's not a bug in the 2.2.14aa7.gz patch. It
may be as well a 2.2.14 official bug of course (but more likely to be
another race in the lowlatency patch).

BTW, I just found another lowlatency patch bug:

+ /*
+ * Tough one to time-limit ...
+ */
entry = entry->next;
- if (!CAN_UNUSE(INODE(tmp)))
+ if (!CAN_UNUSE(INODE(tmp))) {
+ if (current->need_resched) {
+ INODE(tmp)->i_count++;
+ spin_unlock(&inode_lock);
+ schedule();
+ spin_lock(&inode_lock);
+ INODE(tmp)->i_count--;
+ }
+ }

i_count-- won't release the inode correctly (think if the inode got
deleted under the schedule).

Drop the above changes and try again.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:56    [W:0.146 / U:0.368 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site