public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Attempt to get eject failures back to ioctl(CDROMEJECT)
Date: Thu, 15 Nov 2007 12:35:21 +0100	[thread overview]
Message-ID: <20071115113521.GB5035@kernel.dk> (raw)
In-Reply-To: <200711152232.02522.rusty@rustcorp.com.au>

On Thu, Nov 15 2007, Rusty Russell wrote:
> On Thursday 15 November 2007 19:47:05 Jens Axboe wrote:
> > On Thu, Nov 15 2007, Rusty Russell wrote:
> > > If blk_rq_map_sg returns more than was allocated, it's a bug, and
> > > something's already been overwritten.  BUG_ON() is probably the right
> > > thing here.
> >
> > It really just means that it mapped more segments than the block layer
> > said it would. Usually that wont overwrite memory here since scsi rounds
> > up on allocating the sg list, but it indeed can. Similar code has been
> > in scsi_lib.c for ages, I'd suggest covering that in the same patch.
> 
> Good point.  I assume that you've not seen these printks in recent memory?

I have not, they usually show up if we have bugs in the merge accounting
logic in the block layer (the merge functions and blk_rq_map_sg() not
agreeing). It's been ages since that was an issue, so I'm fine with the
bug.

> This covers both cases:
> 
> Subject: [PATCH] scsi: BUG_ON() impossible condition.

You can add my

Acked-by: Jens Axboe <jens.axboe@oracle.com>

when you pass it through James, it should go in that way.

-- 
Jens Axboe


      reply	other threads:[~2007-11-15 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  6:39 [PATCH] Attempt to get eject failures back to ioctl(CDROMEJECT) Rusty Russell
2007-11-14 12:39 ` Jens Axboe
2007-11-15  2:35   ` Rusty Russell
2007-11-15  8:47     ` Jens Axboe
2007-11-15 11:32       ` Rusty Russell
2007-11-15 11:35         ` Jens Axboe [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=20071115113521.GB5035@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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