- 18 Mar, 2003 1 commit
-
-
Christoph Hellwig authored
allowing 2.4/2.5 to be slightly more in sync. SGI Modid: 2.5.x-xfs:slinx:141841a
-
- 17 Mar, 2003 39 commits
-
-
Nathan Scott authored
a no-longer-correct-comment, fix up symlink error path code, several minor changes to help keep this code more in sync with 2.4. SGI Modid: 2.5.x-xfs:slinx:141838a
-
Nathan Scott authored
SGI Modid: 2.5.x-xfs:slinx:141837a
-
Eric Sandeen authored
which are most likely due to a simple user error. SGI Modid: 2.5.x-xfs:slinx:141751a
-
Dean Roehrich authored
SGI Modid: 2.5.x-xfs:slinx:141360a
-
Christoph Hellwig authored
SGI Modid: 2.5.x-xfs:slinx:141237a
-
Stephen Lord authored
processing code. As files get larger, these code paths have the potential to hog the cpu for long periods of time. Just cap the unmapped page case, and the unwritten one is supposed to be stopping at the end of the extent anyway. SGI Modid: 2.5.x-xfs:slinx:141609a
-
Nathan Scott authored
SGI Modid: 2.5.x-xfs:slinx:141508a
-
Nathan Scott authored
SGI Modid: 2.5.x-xfs:slinx:141507a
-
Eric Sandeen authored
the extents code on 64-bit machines SGI Modid: 2.5.x-xfs:slinx:141495a
-
Nathan Scott authored
related to read/write locking the behavior change. SGI Modid: 2.5.x-xfs:slinx:141401a
-
Eric Sandeen authored
SGI Modid: 2.5.x-xfs:slinx:141200a
-
Eric Sandeen authored
SGI Modid: 2.5.x-xfs:slinx:140981a
-
Glen Overby authored
the inode. The inode could have changed since before the lock. SGI Modid: 2.5.x-xfs:slinx:137931a
-
Glen Overby authored
SGI Modid: 2.5.x-xfs:slinx:136543a
-
Glen Overby authored
SGI Modid: 2.5.x-xfs:slinx:139574a
-
Eric Sandeen authored
SGI Modid: 2.5.x-xfs:slinx:140918a
-
Glen Overby authored
SGI Modid: 2.5.x-xfs:slinx:136459a
-
Geoffrey Wehrman authored
SGI Modid: 2.5.x-xfs:slinx:135993a
-
Glen Overby authored
SGI Modid: 2.5.x-xfs:slinx:133509a
-
Charles Fumuso authored
when there is a real problem. SGI Modid: 2.5.x-xfs:slinx:138531a
-
Eric Sandeen authored
SGI Modid: 2.5.x-xfs:slinx:140972a
-
Glen Overby authored
SGI Modid: 2.5.x-xfs:slinx:136445a
-
Christoph Hellwig authored
SGI Modid: 2.5.x-xfs:slinx:140841a
-
Stephen Lord authored
SGI Modid: 2.5.x-xfs:slinx:140714a
-
Stephen Lord authored
SGI Modid: 2.5.x-xfs:slinx:140700a
-
Christoph Hellwig authored
SGI Modid: 2.5.x-xfs:slinx:140576a
-
Dean Roehrich authored
SGI Modid: 2.5.x-xfs:slinx:140501a
-
Stephen Lord authored
SGI Modid: 2.5.x-xfs:slinx:140376a
-
Stephen Lord authored
and in the out of mem case, panic in the sleep case, not the non-sleep case. SGI Modid: 2.5.x-xfs:slinx:140364a
-
Stephen Lord authored
SGI Modid: 2.5.x-xfs:slinx:140254a
-
Stephen Lord authored
confuse user space. This limits the maximum amount of names in a directory on linux to 2Gbytes, which should not be a problem. SGI Modid: 2.5.x-xfs:slinx:135044a
-
Stephen Lord authored
fields after a create/remove etc. Make sure we pass in all the flags for the status fields we want. NBLOCKS was missing and working by accident. SGI Modid: 2.5.x-xfs:slinx:134817a
-
Stephen Lord authored
the filldir fixup at the linvfs layer. This is the V2 directory component, the V1 code still needs fixing up. We now return the same directory offsets as Irix does. SGI Modid: 2.5.x-xfs:slinx:134646a
-
Stephen Lord authored
SGI Modid: 2.5.x-xfs:slinx:134509a
-
Stephen Lord authored
do not add one. SGI Modid: 2.5.x-xfs:slinx:134299a
-
Stephen Lord authored
SGI Modid: 2.5.x-xfs:slinx:134770a
-
Roland McGrath authored
This is a fix made almost a month ago, during the flurry of signal changes. I didn't realize until today that this hadn't made it into 2.5. Sorry about the delay. This fix is necessary to avoid sometimes wedging in uninterruptible sleep when doing a multithreaded core dump triggered by a process signal (kill) rather than a trap. You can reproduce the problem by running your favorite multithreaded program (NPTL) and then using "kill -SEGV" on it. It will often wedge. The actual fix could be just a two line diff: + if (current->signal->group_exit) + goto dequeue; after the group_exit_task check. That is the fix that has been used in Ingo's backport for weeks and tested heavily (well, as heavily as core dumping ever gets tested, but it's been in our production systems). But I broke the hair out into a separate function. The patch below has the same effect as the two-liner, and no other difference. I have tested 2.5.64 with this patch and it works for me, though I haven't beat on it. The way the wedge happens is that for a core-dump signal group_send_sig_info does a group stop of other threads before the one thread handles the fatal signal. If the fatal thread gets into do_coredump and coredump_wait first, then other threads see the group stop and suspend with SIGKILL pending. All other fatal cases clear group_stop_count, so this is the only way this ever happens. Checking group_exit fixes it. I didn't make do_coredump clear group_stop_count because doing it with the appropriate ordering and locking doesn't fit the organization that code.
-
Andries E. Brouwer authored
Mounting a non-affs filesystem as affs crashes the kernel. The reason is the sbi = kmalloc(sizeof(struct affs_sb_info), GFP_KERNEL); memset(sbi, 0, sizeof(*AFFS_SB)); where the second sizeof is 1, so that sbi is not zeroed at all. Also, avoid a warning for printk of sector_t in amigaffs.h.
-
Jens Axboe authored
-