Re: Segmentation faults
no.. i know i have plenty of available space. i am just going to unmount the partition (unfortunately its /home) asap, and run e2fsck on it. however, i am still very much interested in what caused this, and if it could be replicated. because this could be a possible root hole in ext2, although how i would find out more about exploiting this i dont know. all i know is that a segfault is probably exploitable. Thanks all for the help though :) // Ian Shaughnessy // [EMAIL PROTECTED] On Thu, 20 Apr 2000, Andy Bradford wrote: > Thus said Ian Shaughnessy on Thu, 20 Apr 2000 10:24:00 PDT: > > > One of my users has been signed up to a number of mailing lists, and he is > > now unable to access his Maildir/cur or Maildir/new directories. I as > > root can not touch them either.. ls reports a segmentation fault. Du does > > as well, and rm -rf also. Basically this is a pretty big problem, as I > > have no access to his directories with any standard binary tools. my > > question is, what the heck is happening here, and why would an extremely > > large load of messages completely kill my binary tools? I doubt he has > > over a few thousand messages, which granted is alot, but I would assume > > qmail is able to handle that. Has qmail gone and written something funny > > This doesn't really sound like a qmail problem at all. It sounds more > like you have run out of space on your root partition (which is > commonly where /home is left). This is a bad thing because when you > run out of space there, things can get funky. However, if ls and a few > other binarys are segfaulting then maybe you should consider the fact > that you may have been hacked. At any rate, see if you can run df and > possibly free (maybe you're out of memory to boot). > > Andy > -- > +== Andy == TiK: garbaglio ==+ > |Linux is about freedom of choice| > +== http://www.xmission.com/~bradipo/ ===+ > > >
Re: Segmentation faults
On Thu, Apr 20, 2000 at 12:51:56PM -0600, Andy Bradford wrote: > Thus said Ian Shaughnessy on Thu, 20 Apr 2000 10:24:00 PDT: > > > One of my users has been signed up to a number of mailing lists, and he is > > now unable to access his Maildir/cur or Maildir/new directories. I as > > root can not touch them either.. ls reports a segmentation fault. Du does > > as well, and rm -rf also. Basically this is a pretty big problem, as I > > have no access to his directories with any standard binary tools. my > > question is, what the heck is happening here, and why would an extremely > > large load of messages completely kill my binary tools? I doubt he has > > over a few thousand messages, which granted is alot, but I would assume > > qmail is able to handle that. Has qmail gone and written something funny > > This doesn't really sound like a qmail problem at all. It sounds more > like you have run out of space on your root partition (which is > commonly where /home is left). This is a bad thing because when you > run out of space there, things can get funky. However, if ls and a few > other binarys are segfaulting then maybe you should consider the fact > that you may have been hacked. At any rate, see if you can run df and > possibly free (maybe you're out of memory to boot). I've also seen this happen if a process hangs. I think waiting on IO is what ps says. That might apply to mail. -- Christopher F. Miller, Publisher [EMAIL PROTECTED] MaineStreet Communications, Inc 208 Portland Road, Gray, ME 04039 1.207.657.5078 http://www.maine.com/ Database publishing, e-commerce, office/internet integration, Debian linux.
Re: Segmentation faults
Thus said Ian Shaughnessy on Thu, 20 Apr 2000 10:24:00 PDT: > One of my users has been signed up to a number of mailing lists, and he is > now unable to access his Maildir/cur or Maildir/new directories. I as > root can not touch them either.. ls reports a segmentation fault. Du does > as well, and rm -rf also. Basically this is a pretty big problem, as I > have no access to his directories with any standard binary tools. my > question is, what the heck is happening here, and why would an extremely > large load of messages completely kill my binary tools? I doubt he has > over a few thousand messages, which granted is alot, but I would assume > qmail is able to handle that. Has qmail gone and written something funny This doesn't really sound like a qmail problem at all. It sounds more like you have run out of space on your root partition (which is commonly where /home is left). This is a bad thing because when you run out of space there, things can get funky. However, if ls and a few other binarys are segfaulting then maybe you should consider the fact that you may have been hacked. At any rate, see if you can run df and possibly free (maybe you're out of memory to boot). Andy -- +== Andy == TiK: garbaglio ==+ |Linux is about freedom of choice| +== http://www.xmission.com/~bradipo/ ===+ PGP signature
Re: Segmentation faults
Ian Shaughnessy <[EMAIL PROTECTED]> wrote: > > ...ls reports a segmentation fault. Du does as well, and rm -rf also... There you go, blaming qmail again! :) In answer, the problem you describe is (as far as I know) unheard of with qmail. And qmail does _nothing_ to directories except through the side effects of open(), link(), unlink() and rename(). > You have all of the information i can give you... Not quite: What OS, what filesystem, local or NFS? That's all I can think of...now here's my speculation: Did some tool create a file with a humongous name? On my Linux box, all of the programs you mentioned catch the error "ENAMETOOLONG" and exit with an intelligible message. Are you using NFS? Are two systems disagreeing about what ``too long'' is? The number of files should not be a problem--at least not to ls, which you indicated segfaults. Len. -- Frugal Tip #17: Visit the Ford Foundation while disguised as a large, charitable organization.
Segmentation faults
One of my users has been signed up to a number of mailing lists, and he is now unable to access his Maildir/cur or Maildir/new directories. I as root can not touch them either.. ls reports a segmentation fault. Du does as well, and rm -rf also. Basically this is a pretty big problem, as I have no access to his directories with any standard binary tools. my question is, what the heck is happening here, and why would an extremely large load of messages completely kill my binary tools? I doubt he has over a few thousand messages, which granted is alot, but I would assume qmail is able to handle that. Has qmail gone and written something funny into the directory inode? You have all of the information i can give you.. like I said I cannot determine anything about what else is going on. Any ideas? // Ian Shaughnessy // [EMAIL PROTECTED]