From: Anders Blomdell <anders.blomdell@control.lth.se>
To: linux-kernel@vger.kernel.org
Subject: Stray nulls when reading from AF_UNIX sockets
Date: Thu, 06 Sep 2007 17:48:07 +0200 [thread overview]
Message-ID: <46E02137.8030600@control.lth.se> (raw)
Hi,
With recent kernels (2.6.22.x), we are experiencing that random null characters
are read by our mySQL server (i.e. the number of bytes read by the server is
larger than the number of bytes written). I'm currently investigating the
problem (that occurs every 1-35 hours on a loaded system). A current suspect is
the following code in net/unix/af_unix.c:
static int unix_stream_recvmsg(struct kiocb *iocb, struct socket *sock,
struct msghdr *msg, size_t size,
int flags)
{
...
return copied ? : err;
}
Shouldn't this read:
return copied ? copied : err;
Or am I missing something?
Please CC me personally.
Regards
Anders Blomdell
--
Anders Blomdell Email: anders.blomdell@control.lth.se
Department of Automatic Control
Lund University Phone: +46 46 222 4625
P.O. Box 118 Fax: +46 46 138118
SE-221 00 Lund, Sweden
next reply other threads:[~2007-09-06 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 15:48 Anders Blomdell [this message]
2007-09-06 16:09 ` Stray nulls when reading from AF_UNIX sockets Randy Dunlap
2007-09-06 19:23 ` David Miller
2007-09-07 11:52 ` Jan Engelhardt
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=46E02137.8030600@control.lth.se \
--to=anders.blomdell@control.lth.se \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.