linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12551] end_request: I/O error, dev cciss/c0d0, sector 87435720
Date: Tue, 27 Jan 2009 08:51:36 -0800 (PST)	[thread overview]
Message-ID: <20090127165136.C510F108040@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12551-13602@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=12551


mike.miller@hp.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|fs_ext4@kernel-bugs.osdl.org|mike.miller@hp.com
             Status|NEW                         |ASSIGNED




------- Comment #3 from mike.miller@hp.com  2009-01-27 08:51 -------
cciss does not support write barriers at this time. Seems that someone in the
community requested updated specs so they might implement the support, but I
can't find that particular mail.
I'll have to look at how other drivers implement write barriers.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the assignee for the bug, or are watching the assignee.

      parent reply	other threads:[~2009-01-27 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 14:51 [Bug 12551] New: end_request: I/O error, dev cciss/c0d0, sector 87435720 bugme-daemon
2009-01-27 14:52 ` [Bug 12551] " bugme-daemon
2009-01-27 15:42 ` bugme-daemon
2009-01-27 16:51 ` bugme-daemon [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=20090127165136.C510F108040@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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).