mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luca Tettamanti <kronos.it@gmail.com>
To: Shirish Pargaonkar <shirishpargaonkar@gmail.com>
Cc: Jeff Layton <jlayton@redhat.com>,
	linux-kernel@vger.kernel.org, linux-cifs-client@lists.samba.org,
	Steve French <smfrench@gmail.com>
Subject: Re: [linux-cifs-client] Re: [2.6.30-rc6] cifs_close: NULL pointer  dereference
Date: Sun, 17 May 2009 19:10:00 +0200	[thread overview]
Message-ID: <68676e00905171010r73036097x913629a2db20034d@mail.gmail.com> (raw)
In-Reply-To: <4a4634330905170740m180f451dg9e16a3886f2af298@mail.gmail.com>

On Sun, May 17, 2009 at 4:40 PM, Shirish Pargaonkar
<shirishpargaonkar@gmail.com> wrote:
> On Sat, May 16, 2009 at 9:13 PM, Jeff Layton <jlayton@redhat.com> wrote:
>> On Sat, 16 May 2009 22:55:58 +0200
>> Luca Tettamanti <kronos.it@gmail.com> wrote:
>>
>>> On Sat, May 16, 2009 at 06:28:13PM +0200, Luca Tettamanti wrote:
>>> > Hello,
>>> > I just hit a NULL pointer dereference in cifs_close while accessing a file on a
>>> > remote Samba shared directory.
>>> [...]
>>> > BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
>>> > IP: [<ffffffffa05f105c>] cifs_close+0x1c1/0x2e8 [cifs]
[...]
> Does this happen inspite of the patch 90e4ee5d311d4e0729daa676b1d7f754265b5874

Yes, I was running 2.6.30-rc6, which contains that commit.

Luca

      parent reply	other threads:[~2009-05-17 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-16 16:28 Luca Tettamanti
2009-05-16 20:55 ` Luca Tettamanti
2009-05-17  2:13   ` [linux-cifs-client] " Jeff Layton
2009-05-17  2:16     ` Jeff Layton
2009-05-17  6:24     ` Steve French
2009-05-17 14:40     ` Shirish Pargaonkar
2009-05-17 14:58       ` Jeff Layton
2009-05-17 17:10       ` Luca Tettamanti [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=68676e00905171010r73036097x913629a2db20034d@mail.gmail.com \
    --to=kronos.it@gmail.com \
    --cc=jlayton@redhat.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shirishpargaonkar@gmail.com \
    --cc=smfrench@gmail.com \
    /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

all inboxes | Powered by JetHome®