[PATCH] Re: setrlimit and RLIM_INFINITY causing fsck failure, 2.4.18

From: Peter Hartley (pdh@utter.chaos.org.uk)
Date: Wed Mar 20 2002 - 05:12:16 EST

Next message: Martin Dalecki: "Re: Promise 20265 IDE chip gets detected in wrong order 2.4.x"
Previous message: Vamsi Krishna S .: "Re: [PATCH] multithreaded coredumps for elf exeecutables"
In reply to: Alan Cox: "Re: setrlimit and RLIM_INFINITY causing fsck failure, 2.4.18"
Next in thread: Theodore Tso: "Re: setrlimit and RLIM_INFINITY causing fsck failure, 2.4.18"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

AC wrote:
> Test it and see 8)

OK, did do. Patch attached. The occurrence in filemap.c was the one killing
fsck, but I went looking for other occurrences of SIGXFS and made sure they
did the right thing too.

This doesn't address any other wonkiness of rlimit, it just stops it
applying to block devices.

Peter

application/octet-stream attachment: sigxfs-vs-blkdev.patch

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Martin Dalecki: "Re: Promise 20265 IDE chip gets detected in wrong order 2.4.x"
Previous message: Vamsi Krishna S .: "Re: [PATCH] multithreaded coredumps for elf exeecutables"
In reply to: Alan Cox: "Re: setrlimit and RLIM_INFINITY causing fsck failure, 2.4.18"
Next in thread: Theodore Tso: "Re: setrlimit and RLIM_INFINITY causing fsck failure, 2.4.18"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Mar 23 2002 - 22:00:20 EST