linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: stefan.huebner@stud.tu-ilmenau.de
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: Fwd: Maybe a bug in libata-core
Date: Mon, 23 Aug 2010 11:16:21 +0200	[thread overview]
Message-ID: <4C723C65.6080303@kernel.org> (raw)
In-Reply-To: <4C71C645.8050007@stud.tu-ilmenau.de>

On 08/23/2010 02:52 AM, Stefan /*St0fF*/ Hübner wrote:
> Hi Jeff and list,
> 
> maybe this mail was wrong on the linux-scsi list.  So here we go again:
> 
> -------- Original-Nachricht --------
> Betreff: Maybe a bug in libata-core
> Datum: Fri, 20 Aug 2010 23:48:09 +0200
> Von: Stefan Hübner  <stefan.huebner@stud.tu-ilmenau.de>
> Antwort an: stefan.huebner@stud.tu-ilmenau.de
> Organisation: TU-Ilmenau
> An: linux-scsi@vger.kernel.org
> 
>  Hi List!
> 
> After sending a WRITE_DMA_FUA_EXT ATA-command via SG_IO Passthru to a
> harddisk (here: /dev/sdd), my kernel panics.  The is what I find in syslog:

You're sending down data command w/o data.  Panicking probably isn't
the best response here.  Maybe the BUG_ON() should be changed to
WARN_ON_ONCE() + goto sg_err.

Thanks.

-- 
tejun

  reply	other threads:[~2010-08-23  9:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23  0:52 Fwd: Maybe a bug in libata-core Stefan /*St0fF*/ Hübner
2010-08-23  9:16 ` Tejun Heo [this message]
2010-08-23  9:27   ` [PATCH #upstream-fixes] libata: be less of a drama queen on empty data commands Tejun Heo
2010-08-23  9:44   ` Maybe a bug in libata-core Alan Cox
2010-08-23  9:27     ` Tejun Heo
2010-08-23 22:41   ` Stefan /*St0fF*/ Hübner
2010-08-24  7:27     ` Tejun Heo
2010-09-09  5:42       ` Stefan /*St0fF*/ Hübner

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=4C723C65.6080303@kernel.org \
    --to=tj@kernel.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=stefan.huebner@stud.tu-ilmenau.de \
    /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).