From: "Kotian, Deepak" <Deepak.Kotian@patni.com>
To: <linux-kernel@vger.kernel.org>
Subject: Pseudo Driver hangs :b_elv_sequence ?SUSE 8.0 SP3
Date: Fri, 24 Dec 2004 17:57:07 +0530 [thread overview]
Message-ID: <374639AB1012AA4C840022842AA95BC203C70201@ruby.patni.com> (raw)
Hi,
I saw a response from you on b_elv_sequence over here.
http://www.uwsg.iu.edu/hypermail/linux/kernel/0301.3/0472.html
I have observed a similar problem in 2.4.21-138 kernel which comes along
with SUSE 8.0 SP3.
This is mainly for SUSE. I presume, SUSE folks are active on this forum and would respond immediately.Please excuse others, sorry.
In Our pseudo block driver a Defect occurs only when read is done from urandom device &
write to raw device. It basically hangs in kiobuf module.
We are using the buffer_head structure.
We have found by trial and error and looking the source at of raid and md devices that if b_elv_sequence parameter is set to zero, it is OK and our driver does not have a problem.
On looking at the site,we found that you are aware of it. Could you please elaborate.
Question:
Please let us know your views on the b_elv_sequence and reason to set it to zero.
We need to justify whether our fix is correct.
Also, this is not there SLES 9.0 with kernel 2.6 as buffer head concept is gone.
But is the functionality mapped of this flag mapped somewhere in 2.6 or it is not
needed. Anyone here is aware of it.
P.S.
I have posted on SUSE support, not sure when I get response after internal
processing. As it is very urgent for me. I am posting it here as well.
Thanks and Regards
Deepak
next reply other threads:[~2004-12-24 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 12:27 Kotian, Deepak [this message]
2004-12-24 14:05 Kotian, Deepak
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=374639AB1012AA4C840022842AA95BC203C70201@ruby.patni.com \
--to=deepak.kotian@patni.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
all inboxes | Powered by JetHome®