From: David Miller <davem@davemloft.net>
To: cebbert@redhat.com
Cc: croulder@gmail.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Kernel BUG: NULL pointer dereference , reference to sys_recvmsg
Date: Thu, 10 May 2007 14:21:38 -0700 (PDT) [thread overview]
Message-ID: <20070510.142138.54188362.davem@davemloft.net> (raw)
In-Reply-To: <464389A2.6080606@redhat.com>
From: Chuck Ebbert <cebbert@redhat.com>
Date: Thu, 10 May 2007 17:07:46 -0400
> Here in sys_recvmsg() line 1911:
>
> ==> if (sock->file->f_flags & O_NONBLOCK)
> flags |= MSG_DONTWAIT;
> err = sock_recvmsg(sock, &msg_sys, total_len, flags);
>
> sock == -1, apparently because that's what sockfd_lookup_light()
> returned earlier in the function. (It doesn't check err, just
> that the returned sock is nonzero.)
sockfd_lookup_light() returns NULL in all cases where 'err'
is set non-zero.
I suspect file->private_data has been corrupted somehow.
prev parent reply other threads:[~2007-05-10 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <547a31ab0705100712w740e8fbuece5013d05a449b9@mail.gmail.com>
2007-05-10 21:07 ` Kernel BUG: NULL pointer dereference , reference to sys_recvmsg Chuck Ebbert
2007-05-10 21:21 ` David Miller [this message]
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=20070510.142138.54188362.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cebbert@redhat.com \
--cc=croulder@gmail.com \
--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).