- 05 Apr, 2002 11 commits
-
-
Jens Axboe authored
Lets just kill this check -- it usually only catches drivers queueing something in front of a started request on their own (such as shoving a request sense in front of a failed packet command, for instance). So it's either working around this detection in some drivers, or killing it. I vote for the latter, patch attached against 2.5.8-pre1 :-)
-
http://linux-isdn.bkbits.net/linux-2.5.makeLinus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Linus Torvalds authored
-
Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Patrick Mochel authored
-
Patrick Mochel authored
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Patrick Mochel authored
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Patrick Mochel authored
into hera.kernel.org:/home/mochel/BK/linux-2.5
-
- 04 Apr, 2002 29 commits
-
-
Linus Torvalds authored
says it should do - lock out preemption.
-
Linus Torvalds authored
-
Linus Torvalds authored
changes
-
Linus Torvalds authored
-
Robert Love authored
- do not manually set task->state - instead, in preempt_schedule, set a flag in preempt_count that denotes that this task is entering schedule off a kernel preemption. - use this flag in schedule to jump to pick_next_task - in preempt_schedule, upon return from schedule, unset the flag - have entry.S just call preempt_schedule and not duplicate this work, as Linus suggested. I agree. Note this makes debugging easier as we keep a single point of entry for kernel preemptions. The result: we can safely preempt non-TASK_RUNNING tasks. If one is preempted, we can safely survive schedule because we won't handle the special casing of non-TASK_RUNNING at the top of schedule. Thus other tasks can run as desired and our non-TASK_RUNNING task will eventually be rescheduled, in its original state, and complete happily. This is the behavior we have in the 2.4 patches and 2.5 until ~2.5.6-pre. This works. It requires no other changes elsewhere (it actually removes some special-casing Ingo did in the signal code).
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Alexander Viro authored
2.4 variant will go to Marcelo in a couple of minutes. Patch moves IS_DEADDIR() checks into may_delete().
-
Dave Jones authored
More bits from Matt Domsch. Fixes GUID printing, and updates to what's in the IA64 tree. Other cleanups are mentioned in the changelog in the patch.
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Dave Jones authored
Original from: Brian Gerst <bgerst@didntduck.org> Has had a once over by Chris Mason and Al. Seperates reiserfs_sb_info from struct super_block. Brian Gerst
-
Dave Jones authored
Originally by Grant R.Guenther Has had a quick once over by Al, who weeded out one chunk that was unrelated.
-
Dave Jones authored
Originally from Andrew Morton
-
Dave Jones authored
-
Dave Jones authored
Brings QNX4FS back in sync with 2.4
-
Dave Jones authored
Originally from the kernel janitor folks
-
Dave Jones authored
Original from Rene Scharfe This fixes a problem where MSDOS fs's ignore their 'check' mount option.
-
Dave Jones authored
Original fix from Andi Kleen
-
Dave Jones authored
Originally by Anton Altaparmakov. I think Anton is going to submit his rewritten NTFS soon making this null and void, but in the interim, it fixes a known problem with NTFS and large allocations.
-
Dave Jones authored
From the kernel janitor folks
-
Dave Jones authored
From the kernel janitor folks
-