linux-toradex.git/drivers/block/nbd.c, branch v2.6.32.33

const: make block_device_operations const

2009-09-22T14:17:25+00:00

Signed-off-by: Alexey Dobriyan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

block: implement and enforce request peek/start/fetch

2009-05-11T07:52:18+00:00

Till now block layer allowed two separate modes of request execution.
A request is always acquired from the request queue via
elv_next_request().  After that, drivers are free to either dequeue it
or process it without dequeueing.  Dequeue allows elv_next_request()
to return the next request so that multiple requests can be in flight.

Executing requests without dequeueing has its merits mostly in
allowing drivers for simpler devices which can't do sg to deal with
segments only without considering request boundary.  However, the
benefit this brings is dubious and declining while the cost of the API
ambiguity is increasing.  Segment based drivers are usually for very
old or limited devices and as converting to dequeueing model isn't
difficult, it doesn't justify the API overhead it puts on block layer
and its more modern users.

Previous patches converted all block low level drivers to dequeueing
model.  This patch completes the API transition by...

* renaming elv_next_request() to blk_peek_request()

* renaming blkdev_dequeue_request() to blk_start_request()

* adding blk_fetch_request() which is combination of peek and start

* disallowing completion of queued (not started) requests

* applying new API to all LLDs

Renamings are for consistency and to break out of tree code so that
it's apparent that out of tree drivers need updating.

[ Impact: block request issue API cleanup, no functional change ]

Signed-off-by: Tejun Heo 
Cc: Rusty Russell 
Cc: James Bottomley 
Cc: Mike Miller 
Cc: unsik Kim 
Cc: Paul Clements 
Cc: Tim Waugh 
Cc: Geert Uytterhoeven 
Cc: David S. Miller 
Cc: Laurent Vivier 
Cc: Jeff Garzik 
Cc: Jeremy Fitzhardinge 
Cc: Grant Likely 
Cc: Adrian McMenamin 
Cc: Stephen Rothwell 
Cc: Bartlomiej Zolnierkiewicz 
Cc: Borislav Petkov 
Cc: Sergei Shtylyov 
Cc: Alex Dubov 
Cc: Pierre Ossman 
Cc: David Woodhouse 
Cc: Markus Lidel 
Cc: Stefan Weinhuber 
Cc: Martin Schwidefsky 
Cc: Pete Zaitcev 
Cc: FUJITA Tomonori 
Signed-off-by: Jens Axboe

block: blk_rq_[cur_]_{sectors|bytes}() usage cleanup

2009-05-11T07:50:55+00:00

With the previous changes, the followings are now guaranteed for all
requests in any valid state.

* blk_rq_sectors() == blk_rq_bytes() >> 9
* blk_rq_cur_sectors() == blk_rq_cur_bytes() >> 9

Clean up accessor usages.  Notable changes are

* nbd,i2o_block: end_all used instead of explicit byte count
* scsi_lib: unnecessary conditional on request type removed

[ Impact: cleanup ]

Signed-off-by: Tejun Heo 
Cc: Paul Clements 
Cc: Pete Zaitcev 
Cc: Alex Dubov 
Cc: Markus Lidel 
Cc: David Woodhouse 
Cc: James Bottomley 
Cc: Boaz Harrosh 
Signed-off-by: Jens Axboe

block: convert to pos and nr_sectors accessors

2009-05-11T07:50:54+00:00

With recent cleanups, there is no place where low level driver
directly manipulates request fields.  This means that the 'hard'
request fields always equal the !hard fields.  Convert all
rq->sectors, nr_sectors and current_nr_sectors references to
accessors.

While at it, drop superflous blk_rq_pos() < 0 test in swim.c.

[ Impact: use pos and nr_sectors accessors ]

Signed-off-by: Tejun Heo 
Acked-by: Geert Uytterhoeven 
Tested-by: Grant Likely 
Acked-by: Grant Likely 
Tested-by: Adrian McMenamin 
Acked-by: Adrian McMenamin 
Acked-by: Mike Miller 
Cc: James Bottomley 
Cc: Bartlomiej Zolnierkiewicz 
Cc: Borislav Petkov 
Cc: Sergei Shtylyov 
Cc: Eric Moore 
Cc: Alan Stern 
Cc: FUJITA Tomonori 
Cc: Pete Zaitcev 
Cc: Stephen Rothwell 
Cc: Paul Clements 
Cc: Tim Waugh 
Cc: Jeff Garzik 
Cc: Jeremy Fitzhardinge 
Cc: Alex Dubov 
Cc: David Woodhouse 
Cc: Martin Schwidefsky 
Cc: Dario Ballabio 
Cc: David S. Miller 
Cc: Rusty Russell 
Cc: unsik Kim 
Cc: Laurent Vivier 
Signed-off-by: Jens Axboe

nbd: don't clear rq->sector and nr_sectors unnecessarily

2009-05-11T07:50:53+00:00

There's no reason to clear rq->sector and nr_sectors after calling
blk_rq_init().  They're guaranteed to be clear.  Drop unnecessary
clearing.

[ Impact: cleanup ]

Signed-off-by: Tejun Heo 
Cc: Paul Clements 
Signed-off-by: Jens Axboe

nbd: trivial cleanups

2009-04-03T02:05:02+00:00

Trivial cleanups for nbd: only the return -EIO one really changes code,
and I've verified all the callers (plus 0 == success, 1 == error
convention is really ugly).

Signed-off-by: Pavel Machek 
Acked-by: Paul Clements 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

nbd: add locking to nbd_ioctl

2009-04-03T02:05:02+00:00

The code was written to rely on big kernel lock to protect it from races.
It mostly works when interface is not abused.

So this uses tx_lock to protect data structures from concurrent use
between ioctl and worker threads.

Next step will be moving from ioctl to unlocked_ioctl.

[akpm@linux-foundation.org: coding-style fixes]
[akpm@linux-foundation.org: add missing return]
Signed-off-by: Pavel Machek 
Acked-by: Paul Clements 
Cc: Jens Axboe 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

nbd: fix I/O hang on disconnected nbds

2009-02-11T22:25:37+00:00

Fix a problem that causes I/O to a disconnected (or partially initialized)
nbd device to hang indefinitely.  To reproduce:

# ioctl NBD_SET_SIZE_BLOCKS /dev/nbd23 514048
# dd if=/dev/nbd23 of=/dev/null bs=4096 count=1

...hangs...

This can also occur when an nbd device loses its nbd-client/server
connection.  Although we clear the queue of any outstanding I/Os after the
client/server connection fails, any additional I/Os that get queued later
will hang.

This bug may also be the problem reported in this bug report:
http://bugzilla.kernel.org/show_bug.cgi?id=12277

Testing would need to be performed to determine if the two issues are the
same.

This problem was introduced by the new request handling thread code ("NBD:
allow nbd to be used locally", 3/2008), which entered into mainline around
2.6.25.

The fix, which is fairly simple, is to restore the check for lo->sock
being NULL in do_nbd_request.  This causes I/O to an uninitialized nbd to
immediately fail with an I/O error, as it did prior to the introduction of
this bug.

Signed-off-by: Paul Clements 
Reported-by: Jon Nelson 
Acked-by: Pavel Machek 
Cc: 		[2.6.26.x, 2.6.27.x, 2.6.28.x]
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

nbd: do not allow two clients at the same time

2009-01-16T00:39:38+00:00

Two nbd-clients at same time are bad idea, and cause WARN_ON from nbd in
2.6.28-rc7 from sysfs_add_one.  This simply prevents that from happening.

To reproduce:

 cat /dev/zero | head -c 10000000 > /tmp/delme.fstest.fs
 nbd-server 9100 -l /anyone.can.connect > /tmp/delme.fstest.fs &
 sleep 1
 nbd-client localhost 9100 /dev/nd0 &
 nbd-client localhost 9100 /dev/nd0 &

Signed-off-by: Pavel Machek 
Acked-by: Paul Clements 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

nbd: tell the block layer that it is not a rotational device

2008-12-29T07:29:50+00:00

Then we can get rid of that manual elevator type fiddling.

Signed-off-by: Jens Axboe