From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: netfilter is not a filesystem
Date: Thu, 10 Feb 2011 14:11:19 -0800 [thread overview]
Message-ID: <20110210141119.56d789fc.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-28862-10286@https.bugzilla.kernel.org/>
On Thu, 10 Feb 2011 21:55:26 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=28862
>
> Summary: /proc/net/ip_conntrack: no space left on device
> systematically
This is why I'm forever nagging people to not just grab some errno
because its name happens to sound similar to the error you just detected.
Yes, it superficially seems nice and logical for netfilter to use
ENOSPC when it runs out of space. But when that error code propagates
up to the user, they see "no space left on device" and will then run
"df" and wonder what the hell happened to their computer.
The kernel makes this mistake a *lot*. EFBIG in the rtc drivers? Really?
next parent reply other threads:[~2011-02-10 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-28862-10286@https.bugzilla.kernel.org/>
2011-02-10 22:11 ` Andrew Morton [this message]
2011-02-10 22:22 ` netfilter is not a filesystem David Miller
2011-02-11 6:58 ` Richard Cochran
2011-02-14 17:34 ` Patrick McHardy
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=20110210141119.56d789fc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).