From: Akemi Yagi <amyagi@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel panic in cifs_revalidate
Date: Thu, 21 Dec 2006 11:32:58 -0800 [thread overview]
Message-ID: <pan.2006.12.21.19.32.54.182348@gmail.com> (raw)
In-Reply-To: pan.2006.11.21.14.58.30.968552@gmail.com
On Tue, 21 Nov 2006 06:58:38 -0800, Akemi Yagi wrote:
> On Tue, 21 Nov 2006 00:24:40 -0800, Chakri n wrote:
>
>> Hi,
>>
>> I am seeing a kernel panic in cifs module. It seems to be a result of
>> invalid inode entry in dentry for the file it is trying to validate.
>>
>> The inode->i_ino is set zero and inode->i_mapping is set to NULL in
>> the inode pointer in the dentry (0xdf8ea200) structure. I went through
>> the cifs code and could not find any valid case that could trigger
>> this situation. Is there any case which can lead to this situation?
>>
>
> I have been getting kernel oops caused by cifs mount starting with kernel
> 2.6.18. I filed a bug report to RedHat bugzilla at:
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211672
>
A patch for this cifs problem has been posted on the Bugzilla (see the
link above).
Akemi
prev parent reply other threads:[~2006-12-21 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 8:24 Kernel panic in cifs_revalidate Chakri n
2006-11-21 14:58 ` Akemi Yagi
2006-12-21 19:32 ` Akemi Yagi [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=pan.2006.12.21.19.32.54.182348@gmail.com \
--to=amyagi@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox