From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: mc 4.8.19: segfaults while searching for contents
Date: Tue, 03 Oct 2017 08:50:21 +0200 [thread overview]
Message-ID: <821fb18a-1394-ea3d-933d-72c8ec2ee2d3@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
Hi,
Suddenly 'mc 4.8.19' starts throwing segfaults each time I search for contents in multiple files, e.g. in a directory structure like '/usr/local/bin'. Searching in SINGLE files or in a directory which contains only *.sh-files is ok):
...
07:42:32 kernel: mc[17515]: segfault at a39349a0 ip a2fbdf81 sp b0f41af4 error 4 in libpcre.so.1.2.9[a2f94000+44000]
07:42:32 kernel: grsec: From 192.168.100.1: Segmentation fault occurred at a39349a0 in /usr/bin/m c[mc:17515] uid/euid:0/0 gid/egid:0/0, parent /bin/bash[bash:16795] uid/euid:0/0 gid/egid:0/0
07:42:32 kernel: grsec: From 192.168.100.1: denied resource overstep by requesting 4096 for RLIMIT_CORE against limit 0 for /usr/bin/mc[mc:17515] uid/euid:0/0 gid/egid:0/0, parent /bin/bash[bash:16795] uid/euid:0/0 gid/egid:0/0
...
The same happens on a fresh test installation.
Right now I'm thinking about using 'paxctl' on '/usr/bin/mc', but I'm not really sure...:
1. If this would be a solution
2. Which options to use - and
3. On which parts ('/usr/bin/mc'?) exactly.
I'm testing with:
...
paxctl -cm /usr/bin/mc
...
But had no luck until now.
Anybody got a hint or experiencing the same?
Best,
Matthias
next reply other threads:[~2017-10-03 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 6:50 Matthias Fischer [this message]
2017-10-03 7:24 ` Matthias Fischer
2017-10-04 15:41 ` Michael Tremer
2017-10-04 16:34 ` Matthias Fischer
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=821fb18a-1394-ea3d-933d-72c8ec2ee2d3@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/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