public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	"Antonino A. Daplas" <adaplas@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Lockups while unpacking huge tarballs (was Re: 2.6.15-$SHA1: VT <-> X sometimes odd)
Date: Thu, 12 Jan 2006 21:14:32 +0100	[thread overview]
Message-ID: <20060112201431.GE3945@suse.de> (raw)
In-Reply-To: <20060112202341.GA7913@mipter.zuzino.mipt.ru>

On Thu, Jan 12 2006, Alexey Dobriyan wrote:
> On Thu, Jan 12, 2006 at 11:23:54AM -0800, Linus Torvalds wrote:
> > On Thu, 12 Jan 2006, Alexey Dobriyan wrote:
> > > Now it's vim saving 5k proggie while X tarball was unpacking on reiserfs.
> > > :wq and vim freezes. Switching to another virtual "desktops" works and
> > > everything in general works except vim. But switching to VT and back
> > > sends system to hell.
> >
> > This may be fixed by the current -git tree:
> >
> > 	commit 1bc691d3, Tejun Heo <htejun@gmail.com>:
> >
> > 	[PATCH] fix queue stalling while barrier sequencing
> 
> It isn't. My HEAD is 9f5974c8734d83d4ab7096ed98136a82f41210d6 and I see
> this patch in git log output.
> 
> > or if that isn't it, and you have an IDE drive, can you try if the
> > appended trivial patch makes a difference?
> 
> > --- a/drivers/ide/ide-io.c
> > +++ b/drivers/ide/ide-io.c
> > @@ -101,7 +101,7 @@ int __ide_end_request(ide_drive_t *drive
> >  	 * for those
> >  	 */
> >  	nbytes = nr_sectors << 9;
> > -	if (!rq->errors && rq_all_done(rq, nbytes)) {
> > +	if (0 && !rq->errors && rq_all_done(rq, nbytes)) {
> >  		rq->data_len = nbytes;
> >  		blkdev_dequeue_request(rq);
> >  		HWGROUP(drive)->rq = NULL;
> 
> With this one-liner two X tarballs and one Firefox tarballs were
> successfully unpacked while I was hitting :w.
> 
> Without it just one X tarball doesn't pass. It's even reproducable.

Alright thanks for retesting, current git should work for you (once it
mirrors out from master).

-- 
Jens Axboe


      reply	other threads:[~2006-01-12 20:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 16:23 2.6.15-$SHA1: VT <-> X sometimes odd Alexey Dobriyan
2006-01-11 11:50 ` Antonino A. Daplas
2006-01-11 15:38   ` Alexey Dobriyan
2006-01-12 19:28     ` Alexey Dobriyan
2006-01-12 19:23       ` Linus Torvalds
2006-01-12 20:04         ` Linus Torvalds
2006-01-12 20:08           ` Jens Axboe
2006-01-12 20:23         ` Lockups while unpacking huge tarballs (was Re: 2.6.15-$SHA1: VT <-> X sometimes odd) Alexey Dobriyan
2006-01-12 20:14           ` 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=20060112201431.GE3945@suse.de \
    --to=axboe@suse.de \
    --cc=adaplas@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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