On Fri, Jan 31, 2014 at 03:20:17AM -0500, Mikulas Patocka wrote:
So if you think you can support 16TiB devices and leave pgoff_t 32-bit,
send a patch that does it.
Until you make it, you should apply the patch that I sent, that prevents
kernel lockups or data corruption when the user uses
From: Roland Dreier rol...@purestorage.com
Commit fbfe858fea2a (target_core_spc: Include target device
descriptor in VPD page 83) added a new length variable, but (due to a
cut and paste mistake?) just checks scsi_name_len against 256 twice.
Fix this to check scsi_target_len for overflow too.
This patch fixed following warnings on make htmldocs.
Warning(/drivers/scsi/scsi_transport_srp.c:819):
No description found for parameter 'rport'
Signed-off-by: Masanari Iida standby2...@gmail.com
---
drivers/scsi/scsi_transport_srp.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/2/2014 5:42 AM, Hannes Reinecke wrote:
This is due to the strictly sequential design udev has. Essentially udev
spawns a worker for every device which gets created (= udev receives a
uevent for).
The part I fail to see in this
On 02/03/14 15:34, Masanari Iida wrote:
This patch fixed following warnings on make htmldocs.
Warning(/drivers/scsi/scsi_transport_srp.c:819):
No description found for parameter 'rport'
Signed-off-by: Masanari Iida standby2...@gmail.com
---
drivers/scsi/scsi_transport_srp.c | 2 ++
1
On Fri, 31 Jan 2014 20:49:39 -0600
Matthew Thode prometheanf...@gentoo.org wrote:
I decided to pull a drive while it was in use out of laziness (it was
open via luks, but not in actual use). Got a fun trace as a result.
Just thought you'd like to know :D
Hi Matthew,
The first trace looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/03/2014 03:50 PM, Jeremy Linton wrote:
On 2/2/2014 5:42 AM, Hannes Reinecke wrote:
This is due to the strictly sequential design udev has.
Essentially udev spawns a worker for every device which gets
created (= udev receives a uevent for).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/3/2014 9:06 AM, Hannes Reinecke wrote:
That's due to udev. Udev is getting events for each device it should create
a device node for. So for 'st' it'll get a series of events for 'stX', and
another series of events for 'nstX'. Udev will treat
Acked-by: Brian King brk...@linux.vnet.ibm.com
--
Brian King
Power Linux I/O
IBM Linux Technology Center
--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Acked-by: Brian King brk...@linux.vnet.ibm.com
--
Brian King
Power Linux I/O
IBM Linux Technology Center
--
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Mon, 2014-02-03 at 00:35 -0800, Roland Dreier wrote:
From: Roland Dreier rol...@purestorage.com
Commit fbfe858fea2a (target_core_spc: Include target device
descriptor in VPD page 83) added a new length variable, but (due to a
cut and paste mistake?) just checks scsi_name_len against 256
driver-core now supports synchrnous self-deletion of attributes and
the asynchrnous removal mechanism is scheduled for removal. Use it
instead of device_schedule_callback(). This makes delete behave
synchronously.
Signed-off-by: Tejun Heo t...@kernel.org
Cc: James E.J. Bottomley
On Mon, 3 Feb 2014, Christoph Hellwig wrote:
On Fri, Jan 31, 2014 at 03:20:17AM -0500, Mikulas Patocka wrote:
So if you think you can support 16TiB devices and leave pgoff_t 32-bit,
send a patch that does it.
Until you make it, you should apply the patch that I sent, that prevents
On Mon, Feb 3, 2014 at 4:08 PM, Jeremy Linton jlin...@tributary.com wrote:
On 2/3/2014 9:06 AM, Hannes Reinecke wrote:
That's due to udev. Udev is getting events for each device it should create
a device node for. So for 'st' it'll get a series of events for 'stX', and
another series of
On Mon, 2014-02-03 at 21:51 +0100, Kay Sievers wrote:
On Mon, Feb 3, 2014 at 4:08 PM, Jeremy Linton jlin...@tributary.com wrote:
On 2/3/2014 9:06 AM, Hannes Reinecke wrote:
That's due to udev. Udev is getting events for each device it should create
a device node for. So for 'st' it'll get
On 14-02-03 10:08 AM, Jeremy Linton wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/3/2014 9:06 AM, Hannes Reinecke wrote:
That's due to udev. Udev is getting events for each device it should create
a device node for. So for 'st' it'll get a series of events for 'stX', and
another
On Mon, Feb 3, 2014 at 10:16 PM, Douglas Gilbert dgilb...@interlog.com wrote:
On 14-02-03 10:08 AM, Jeremy Linton wrote:
So whats wrong with the simple solution? You throw the ones for st
away, and
create the st handles from the nst worker.
Doesn't seem to be any good solutions to
On 2/3/2014 2:51 PM, Kay Sievers wrote:
This is not simple and not going to happen. Sibling devices in /sys cannot
have a relationship in udev, there are only parent/child dependencies.
Ok.. so if we can't ignore all the spare device nodes in a given /sys
entry
for a given device. Why
From: Roland Dreier rol...@purestorage.com
The CMD_T_FAILED flag is set used in one place to record the result of a
trivial test, and it is only tested once, few lines later. We might as
well make the code simpler and easier to read by directly doing the test
of success where we want to use it.
On Mon, Feb 3, 2014 at 10:58 PM, Jeremy Linton jlin...@tributary.com wrote:
On 2/3/2014 2:51 PM, Kay Sievers wrote:
This is not simple and not going to happen. Sibling devices in /sys cannot
have a relationship in udev, there are only parent/child dependencies.
Ok.. so if we can't
David == David Milburn dmilb...@redhat.com writes:
David When enabling DIX T10-DIF-TYPE1-IP protection you can hit the
David bip_vec full condition which fails to attach the integrity
David metadata and returns 0 back to bio_integrity_prep()
Looks like Kent accidentally broke this when he
Doug == Douglas Gilbert dgilb...@interlog.com writes:
Doug The parts of this patch that I understand look fine. Perhaps
Doug Martin should ack it, if he sees fit.
Just had another look at the updated pieces. Patch series looks good to
me.
Reviewed-by: Martin K. Petersen
22 matches
Mail list logo
