From: Marcin Dalecki <dalecki@evision.ag>
To: Jens Axboe <axboe@suse.de>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] 2.5.30 IDE 113
Date: Tue, 06 Aug 2002 12:47:00 +0200 [thread overview]
Message-ID: <3D4FA924.3030601@evision.ag> (raw)
In-Reply-To: 20020806104414.GC1132@suse.de
Uz.ytkownik Jens Axboe napisa?:
> On Tue, Aug 06 2002, Petr Vandrovec wrote:
>
>>>After all ide_raw_taskfile only gets used for REQ_SPECIAL request
>>>types. This does *not* contain normal data request from block IO.
>>>As of master slave issues - well we have the data pre allocated per
>>>device not per channel! If q->request_fn would properly return the
>>>error count instead of void, we could even get rid ot the
>>>checking for rq->errors after finishment... But well that's
>>>entierly different story.
>>
>>For example do_cmd_ioctl() invokes ide_raw_taskfile, without any locking.
>>Two programs, both issuing HDIO_DRIVE_CMD at same time, will compete
>>over one drive->srequest struct: you'll get same drive->srequest structure
>>submitted twice to blk_insert_request (hm, Jens, will this trigger
>>BUG, or will this just damage request list?).
>
>
> Just silently damage request list. We _could_ easily add code to detect
> this, but it's not been a problem in the past so not worth looking for.
>
> AFAICS, Petr is completely right wrt this race.
For the ioctl case yes. But:
1. We already look for blk_queue_empty there.
2. We have just to deal properly with the queue plugging there
to close it up.
3. I will just add spin locking on ide_lock to maintain that no two
ioctl can overlapp at all.
OK?
next prev parent reply other threads:[~2002-08-06 10:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 10:35 [PATCH] 2.5.30 IDE 113 Petr Vandrovec
2002-08-06 10:44 ` Jens Axboe
2002-08-06 10:47 ` Marcin Dalecki [this message]
2002-08-06 11:03 ` Jens Axboe
2002-08-06 11:04 ` Marcin Dalecki
2002-08-06 11:12 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2002-08-06 10:16 Petr Vandrovec
2002-08-06 10:20 ` Marcin Dalecki
2002-08-06 10:42 ` Jens Axboe
2002-08-06 10:43 ` Marcin Dalecki
2002-08-06 10:54 ` Jens Axboe
2002-08-06 10:52 ` Marcin Dalecki
2002-08-06 11:05 ` Jens Axboe
2002-08-06 11:09 ` Marcin Dalecki
2002-08-06 11:17 ` Jens Axboe
2002-08-06 11:57 ` Marcin Dalecki
2002-08-06 9:02 Marcin Dalecki
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=3D4FA924.3030601@evision.ag \
--to=dalecki@evision.ag \
--cc=VANDROVE@vc.cvut.cz \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=torvalds@transmeta.com \
/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