public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Jens Axboe <axboe@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, Robert Love <rml@tech9.net>,
	Thomas Molina <tmolina@cox.net>,
	linux-kernel@vger.kernel.org, andre@linux-ide.org
Subject: Re: 2.5 Problem Status Report
Date: Wed, 11 Sep 2002 15:16:02 +0400	[thread overview]
Message-ID: <20020911151602.A830@namesys.com> (raw)
In-Reply-To: <20020911105807.GF1089@suse.de>

Hello!

On Wed, Sep 11, 2002 at 12:58:07PM +0200, Jens Axboe wrote:

> > > > ok I see the bug. it's due to the imbalanced nature of ide_map_buffer()
> > > > vs ide_unmap_buffer(). i'll cook up a fix right away.
> > > Does this make it work?
> > No. It fails exactly like without the patch.
> Hmm, ok I'll try and reproduce it here then.

> > > -	bio_kunmap_irq(buffer, flags);
> > > +	if (rq->bio)
> > > +		bio_kunmap_irq(buffer, flags);
> > >  }
> > >  
> > Perhaps you forgot to make sure rq->bio is zeroed on unmapping/freeing?
> rq->bio must not be zeroed or free'd or anything like that. ok I see

Hm? So this branch is always executed? Why to check for it then?
(I mean content of rq->bio, not the place where it points to).

> what happens now. does this patch work for you? just back out the other
> patch first (well you don't have to, but might as well).

Ok, with other patch it still fails in the same way.
I have not backed out other patch so I tested with both patches perent.

Bye,
    Oleg

  parent reply	other threads:[~2002-09-11 11:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11  2:00 2.5 Problem Status Report Thomas Molina
2002-09-11  2:29 ` William Lee Irwin III
2002-09-11 18:33   ` Thomas Molina
2002-09-11 20:23     ` William Lee Irwin III
2002-09-11  4:00 ` Robert Love
2002-09-11  7:07   ` Oleg Drokin
2002-09-11  7:26     ` Ingo Molnar
2002-09-11  7:28       ` Oleg Drokin
2002-09-11  7:38         ` Ingo Molnar
2002-09-11  8:05           ` Oleg Drokin
2002-09-11 10:25             ` Jens Axboe
2002-09-11 10:29               ` Jens Axboe
2002-09-11 10:47                 ` Oleg Drokin
2002-09-11 10:58                   ` Jens Axboe
2002-09-11 11:07                     ` Jens Axboe
2002-09-11 11:16                     ` Oleg Drokin [this message]
2002-09-11 11:17                       ` Jens Axboe
2002-09-11 11:49                         ` Jens Axboe
2002-09-11 12:10                           ` Oleg Drokin
2002-09-11 15:38                             ` Oleg Drokin
2002-09-11 15:46                               ` Ingo Molnar
2002-09-11 15:52                                 ` Ingo Molnar
2002-09-11 17:49                                 ` Oleg Drokin
2002-09-11  8:07     ` Thomas Molina
2002-09-11  8:12       ` Oleg Drokin
2002-09-11  9:18       ` Adrian Bunk
2002-09-11  7:12   ` Ingo Molnar
2002-09-11  8:04 ` Axel Siebenwirth
2002-09-11  9:21 ` Clemens Schwaighofer
  -- strict thread matches above, loose matches on Subject: below --
2002-08-25 11:21 Thomas Molina
2002-08-26 16:42 ` Greg KH
2002-08-26 21:32   ` Thomas Molina
2002-08-02  2:39 2.5 Problem Status report Thomas Molina

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=20020911151602.A830@namesys.com \
    --to=green@namesys.com \
    --cc=andre@linux-ide.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rml@tech9.net \
    --cc=tmolina@cox.net \
    /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