Hi,
On Wed, Jan 16, 2008 at 04:33:12PM +0900, KOSAKI Motohiro wrote:
> Hi Clifford,
>
> > +static inline char *task_rlim(struct task_struct *p, char *buffer)
> > +{
> > + unsigned long flags;
> > + struct rlimit rlim[RLIM_NLIMITS];
> > + int i;
> > +
> > + rcu_read_lock();
> > + if (
Hi Clifford,
> +static inline char *task_rlim(struct task_struct *p, char *buffer)
> +{
> + unsigned long flags;
> + struct rlimit rlim[RLIM_NLIMITS];
> + int i;
> +
> + rcu_read_lock();
> + if (lock_task_sighand(p, &flags)) {
> + for (i=0; i +
Hi,
On Tue, Jan 15, 2008 at 02:36:59PM -0600, [EMAIL PROTECTED] wrote:
> > + rcu_read_lock();
> > + if (lock_task_sighand(p, &flags)) {
> > + for (i=0; i > + rlim[i] = p->signal->rlim[i];
>
> I'm confused - where do you unlock_task_sighand()?
oh fsck! thanks for t
Quoting Clifford Wolf ([EMAIL PROTECTED]):
> Hi,
>
> because I needed it already twice in two different projects this week: the
> following patch adds rlim (ulimits) output to /proc//status.
>
> Please let me know if there is another (already existing) way of accessing
> this information easy (i.
Hi,
because I needed it already twice in two different projects this week: the
following patch adds rlim (ulimits) output to /proc//status.
Please let me know if there is another (already existing) way of accessing
this information easy (i.e. connecting with gdb to the process in question
and 'in
5 matches
Mail list logo