mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Seiderer <Peter.Seiderer@ciselant.de>
To: linux-kernel@vger.kernel.org
Cc: Ville Herva <vherva@niksula.hut.fi>
Subject: Re: What is the difference between 'login: root' and 'su -' ?
Date: Thu, 8 Nov 2001 11:14:21 +0100	[thread overview]
Message-ID: <20011108111421.A612@zodiak.ecademix.com> (raw)
In-Reply-To: <20011107184710.A1410@zodiak.ecademix.com> <20011107224824.G26218@niksula.cs.hut.fi> <20011107234025.A602@zodiak.ecademix.com> <20011108081006.S1504@niksula.cs.hut.fi> <20011108094637.B615@zodiak.ecademix.com> <20011108104634.T1504@niksula.cs.hut.fi> <20011108100014.A704@zodiak.ecademix.com> <20011108111330.U1504@niksula.cs.hut.fi>
In-Reply-To: <20011108111330.U1504@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Thu, Nov 08, 2001 at 11:13:30AM +0200

Hello,
the SIGXFSZ signal is produced in the file mm/filemap.c (linx-2.4.14) in
line 2771:

2769:	if (limit != RLIM_INFINITY) {
2770:		if (pos >= limit) {
2771:			send_sig(SIGXFSZ, current, 0);
2772:			goto out;
2773:		}

The valus at this point are
limit:         0x7fffffff
RLIM_INFINITY: 0xffffffff
pos:           0x80004000

where limit comes from:
unsigned long	limit = current->rlim[RLIMIT_FSIZE].rlim_cur;

but I did not yet detected the point(s) where
current->rlim[RLIMIT_FSIZE].rlim_cur
is(are) set/changed.
Peter

On Thu, Nov 08, 2001 at 11:13:30AM +0200, Ville Herva wrote:
> On Thu, Nov 08, 2001 at 10:00:14AM +0100, you [Peter Seiderer] claimed:
> > Hello,
> > first thank you for your effort.
> > 
> > Did the diff: nearly no difference till the failure point (only pid, time
> > etc.). Peter
> 
> And there really are no resource limits nor quota?
> 
> At this point you'll propably have to dig into glibc / kernel source and try
> to find out what might cause that...
> 
> 
> -- v --
> 

  parent reply	other threads:[~2001-11-08 10:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 17:47 Peter Seiderer
     [not found] ` <20011107224824.G26218@niksula.cs.hut.fi>
2001-11-07 22:40   ` Peter Seiderer
     [not found]     ` <20011108081006.S1504@niksula.cs.hut.fi>
2001-11-08  8:46       ` Peter Seiderer
     [not found]         ` <20011108104634.T1504@niksula.cs.hut.fi>
2001-11-08  9:00           ` Peter Seiderer
     [not found]             ` <20011108111330.U1504@niksula.cs.hut.fi>
2001-11-08 10:14               ` Peter Seiderer [this message]
2001-11-08 14:20                 ` [patch] " Peter Seiderer
2001-11-08  7:31 ` Vitezslav Samel
2001-11-08 15:38 ` Tobias Diedrich
2001-11-08 18:35   ` Peter Seiderer
2001-11-08 14:34 PVotruba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011108111421.A612@zodiak.ecademix.com \
    --to=peter.seiderer@ciselant.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vherva@niksula.hut.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®