Re: 4096 byte limit to /proc/PID/environ ?

I think this is the wrong approach.

Many of these should probably be converted to seq_file, but in the
particular case of environ, the right approach is to observe the fact
that reading environ is just like reading /proc/PID/mem, except:

 a. the access restrictions are less strict, and
 b. there is a range restriction, which needs to be enforced, and
 c. there is an offset.

Pretty much, take the guts from /proc/PID/mem and generalize it
slightly, and you have the code that can run either /proc/PID/mem or
/proc/PID/environ.

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

---

• References:
  • Re: 4096 byte limit to /proc/PID/environ ?
    • From: James Pearson <[email protected]>

• Prev by Date: Re: Program to convert core file to executable.
• Next by Date: Re: Program to convert core file to executable.
• Previous by thread: Re: 4096 byte limit to /proc/PID/environ ?
• Next by thread: Re: 4096 byte limit to /proc/PID/environ ?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]