Skip to content

writable limits

Jiri Slaby linux-fsdevel linux-ia64 linux-mm linux-rdma linux-s390 linuxppc-dev lkml sparclinux 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v3 Latest0 of 27 patches 1 replyIn review

Patches in v3 No applies recorded yet

None of the 27 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [PATCH v3 00/27] writable limits

Hi,

I broke the threading to not mess up with the long thread.

In this version I got rid of the rlim access_only ugliness.

There are two things:
1)
<quote from=Ingo>
A prominent example would be the stack limit - we base address layout decisions on it. Check arch/x86/mm/mmap.c. RLIM_INFINITY has a special meaning plus we also set mmap_base() based on the rlim. </quote>
Should there be some special handling of that? In standard setrlimit there is none.

2)
<quote from=Oleg>
Hmm. you are right. Do you know why acct_file_reopen() does

	if (old_acct)
		do_acct_process();

???
</quote>
As I expressed myself before, I don't know why it is there (it doesn't make sense to me either). But I took a look at when it was added. From the very first merge of acct.c (2.1.68pre1) it was just in (name == NULL) path (turning acct off). Then in 2.1.126 it was switched to account on every accounting file change.

I fear if we changed this, something would break.

thanks,

Signature · 1 line
js