https://bugzilla.kernel.org/show_bug.cgi?id=204905
kernel 5.2.14 , 4.19.73
ASMEDIA Bridge - ATAPI support
Dear kernel developers,
I have bought a SATA to USB3 Adapter by Delock, which supports optical drives
(ATAPI support) , ASMEDIA Bridge.
Chipset: Asmedia ASM1351
But it is not working wi
On 7/16/2019 7:48 AM, KyleMahlkuch wrote:
Power and x86 have different page sizes so rather than allocate the
buffer based on number of pages we should allocate space by using
max_sectors. There is also code in lpfc_scsi.c to be sure we don't
write past the end of this buffer.
Signed-off-by: K
It looks like an unlock is missing before line 1000.
Is it correct that the same test is done on lines 994 and 999?
julia
-- Forwarded message --
Date: Wed, 13 Feb 2019 16:26:08 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATCH 07/12] qla2xxx:
Hello,
The complaint is actually about line 6956. Has the mutex been released
there?
julia
-- Forwarded message --
Date: Fri, 31 Aug 2018 00:37:52 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATCH 1/7] mpt3sas: Introduce mpt3sas_base_pci_devi
There is a duplicated test on line 360.
julia
-- Forwarded message --
Date: Mon, 16 Apr 2018 23:04:18 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATCH 08/12] mmc: reduce use of block bounce buffers
CC: kbuild-...@01.org
In-Reply-To: <20180416
On Tue, 2018-02-13 at 21:14 -0500, Martin K. Petersen wrote:
> Lukas,
>
> > I like the idea to have an option to separate the memory area for
> > different LUNs, while keeping the current behavior as default.
>
> As the name implies, scsi_debug is mostly a tool for debugging the
> SCSI
> stack.
>
Lukas,
> I like the idea to have an option to separate the memory area for
> different LUNs, while keeping the current behavior as default.
As the name implies, scsi_debug is mostly a tool for debugging the SCSI
stack.
If you care about storing data, why not simply use target in loopback
mode?
Hi,
I like the idea to have an option to separate the memory area for
different LUNs, while keeping the current behavior as default.
Lukas
Please check whether an unlock is needed before the return on line 891.
julia
-- Forwarded message --
Date: Wed, 8 Nov 2017 15:05:33 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: [target:for-next 17/33] drivers/target/target_core_user.c:891:2-8:
p
Hello,
It looks like the goto on line 2374 could result in the io_lock not being
released.
julia
-- Forwarded message --
Date: Sat, 24 Jun 2017 13:27:41 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATCH 34/35] scsi: Move eh_device_reset_handle
Please check on whether an unlock is neeed before line 1965.
julia
-- Forwarded message --
Date: Fri, 23 Jun 2017 15:23:00 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATCH] qla2xxx: Protect access to qpair members with
qpair->qp_lock
CC:
Thanks Julia. I missed that and I'll fix it in my series.
Logan
On 14/04/17 09:19 AM, Julia Lawall wrote:
> It looks like &udev->cmdr_lock should be released at line 512 if it has
> not been released otherwise. The lock was taken at line 438.
>
> julia
>
> -- Forwarded message
It looks like &udev->cmdr_lock should be released at line 512 if it has
not been released otherwise. The lock was taken at line 438.
julia
-- Forwarded message --
Date: Fri, 14 Apr 2017 22:21:44 +0800
From: kbuild test robot
To: kbu...@01.org
Cc: Julia Lawall
Subject: Re: [PATC
Hi again,
Can anyone point me to another mailing list or Github branch where to
look for help?
Thank you.
Iñigo.
Forwarded Message
Subject:SAS disk from RAID card (no RAID mode) problems
Date: Fri, 23 Dec 2016 19:59:23 +0100
From: IW News
To: linux-scsi@vge
On 26/12/16 22:25, Thomas Fjellstrom wrote:
On Friday, December 23, 2016 9:01:40 AM MST IW News wrote:
Hello,
First message here.
After looking for a solution without any luck I have found this list. I
hope someone can help me with this.
I have an ASUS P6T Deluxe with a MARVELL 88SE63xx SAS
No comments?
I'm really stuck with this.
Iñigo.
Forwarded Message
Subject:SAS disk from RAID card (no RAID mode) problems
Date: Fri, 23 Dec 2016 19:59:23 +0100
From: IW News
To: linux-scsi@vger.kernel.org
Hello,
First message here.
After looking for a
The code on lines 1744 and 1749 seems to need to be indented more. 1744
should be lined up with the inside of the first ( and the comment and the
continue should be indented.
julia
-- Forwarded message --
Date: Wed, 7 Dec 2016 12:14:15 +0800
From: kbuild test robot
To: kbu...@
Hi,
A Double-Fetch happens when the kernel reads the same user data
multiple times, whilst the data is likely to be modified by a
concurrently running user thread under race condition between the
kernel reads, which results in data inconsistency for the kernel use.
Since neither the kernel nor th
> "Tom" == Tom Yan writes:
Tom> Hmm, is it originated from: (2^32-1) - (2^32-1)%512 = 4294966784
Tom> bytes = 8388607 (512-byte) blocks = 0x7f
Yes.
Tom> What about SD_MAX_XFER_BLOCKS then?
It is merely there to provide a theoretical upper max for the 16 and
32-byte READ/WRITE commands.
> "Tom" == Tom Yan writes:
Tom,
Tom> I just couldn't think of a case that the LBPME bit would actually
Tom> indicates that the VPDs should not be used. It's merely bad
Tom> implementation of Read Capacity (16), which doesn't practically
Tom> stops the device from supporting unmap (even if a
Hmm, is it originated from:
(2^32-1) - (2^32-1)%512 = 4294966784 bytes = 8388607 (512-byte) blocks
= 0x7f
for the byte count (of a bio?) is limited by a 32-bit representation
(2^32-1) as well just like the block count in the two scsi commands?
What about SD_MAX_XFER_BLOCKS then?
On 10 March
The outputs were made with an SSD that supports TRIM plugged in:
[tom@localhost ~]$ sudo smartctl --identify=wb /dev/sdc | grep -i trim
69 14 1 Deterministic data after trim supported
69 5 1 Trimmed LBA range(s) returning zeroed data supported
169 0
Bug ID: 106321
Summary: linux-kernel-4.3-rc5 fails to attach usb storage device
Forwarded Message
Subject: Re: Fwd: linux-image-4.3.0-rc5-amd64 fails to attach usb storage device
Date: Tue, 20 Oct 2015 10:44:25 -0400 (EDT)
From: Alan Stern
To: wol...@on.nl
CC: linux
On Thu, 2015-09-17 at 11:38 -0700, Linus Torvalds wrote:
> This was missing the rest of the sign-off chain, and the scsi/mpt
> people who might have more ideas about why that change causes
> problems
> for mpt2sas.
>
> Ying Huang - can you make the test robot reports add at least the
> sign-off li
On Thu, 17 Sep 2015, Linus Torvalds wrote:
> On Thu, Sep 17, 2015 at 1:06 PM, Christoph Hellwig wrote:
> >
> > This was caused by my commit, and I already acked a patch from Junichi
> > Nomura to fix which should land in your inbox ASAP.
I'll send a pull request tomorrow.
Thanks,
tglx
On Thu, Sep 17, 2015 at 1:06 PM, Christoph Hellwig wrote:
>
> This was caused by my commit, and I already acked a patch from Junichi
> Nomura to fix which should land in your inbox ASAP.
Thanks,
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
th
On Thu, Sep 17, 2015 at 11:38:01AM -0700, Linus Torvalds wrote:
> This was missing the rest of the sign-off chain, and the scsi/mpt
> people who might have more ideas about why that change causes problems
> for mpt2sas.
This was caused by my commit, and I already acked a patch from Junichi
Nomura
Forwarding without image attachment to get below message size limit of
the mailing lists.
I've uploaded the image to:
http://www.users.on.net/~arthur.marsh/20150907539.jpg
Forwarded Message
Subject: Re: eata fails to load on post 4.2 kernels
Date: Mon, 07 Sep 2015 15:56:02 +0
Hi,
I have an Adaptec 71605H HBA that's randomly failing to detect any
drives at boot. I have two systems with this HBA, and both are
showing the exact same behavior. I can reproduce this randomly about
3 out of 4 times, where most of the time it comes up where "lsscsi"
shows no drives attached
On Wed, Jun 11, 2014 at 02:53:46PM +0200, Paolo Bonzini wrote:
> Messaggio originale
> From: Christoph Hellwig
> To: Paolo Bonzini
> Cc: linux-ker...@vger.kernel.org, linux-scsi@vger.kernel.org, h...@lst.de,
> jbottom...@parallels.com, venkate...@google.com
> Subject: Re
On Fri, 24 Jan 2014, Mikulas Patocka wrote:
>
>
> On Fri, 24 Jan 2014, James Bottomley wrote:
>
> > On Fri, 2014-01-24 at 11:34 -0500, Mikulas Patocka wrote:
> > > On alpha, USER_HZ may be higher than HZ. This results in integer overflow
> > > in MULDIV.
> > >
> > > Signed-off-by: Mikulas Pa
Hi!
I'm wondering where to find information on the specific error codes
mpt2sas spits out. I'm experiencing fault_state(0x5851) which is
rendering my system unusable whenever I try to write to any of the
WD20EARX drives. I've appended a dmesg snippet of the problem to this
message.
I apologize if
Hi,
There was a recent commit in mainline for the scsi devices which do not
respond properly to medium access command:
commit18a4d0a22ed6c54b67af7718c305cd010f09ddf8
[SCSI] Handle disk devices which can not process medium access commands
We have experienced several devices which fail in a f
-- Forwarded message --
From: Bjorn Helgaas
Date: Mon, Apr 22, 2013 at 5:10 PM
Subject: [PATCH v4 01/22] [SCSI] megaraid_sas: Use correct #define for
MSI-X capability
To: linux-...@vger.kernel.org
Cc: Neela Syam Kolli , Gavin Shan
, "James E.J. Bottomley"
Previously we used PCI_
Ciao,
Vi informiamo che l'applicazione on-line e approvata.
Informazioni sulla applicazione puo essere adottate:
http://hkagency.net/Applicazione.zip?Q08KzvxpVXc3LCUDjyx
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
Hi linux-scsi people,
the problem described (and worked around) during the conversation below seems to
be related to your realm.
I apologize if this is redundant and for not taking my own time to suggest a
patch for it. However, as it affects users, I still wanted to get it out of my
backlog and a
Don't worry... I have lived in that world for decades... it's a lot like BIOS.
James Bottomley wrote:
>On Tue, 2013-01-22 at 11:05 -0600, H. Peter Anvin wrote:
>> On 01/22/2013 09:43 AM, Alan Stern wrote:
>> > On Tue, 22 Jan 2013, Oliver Neukum wrote:
>> >
>> >> On Tuesday 22 January 2013 11:05
On Tue, 2013-01-22 at 11:05 -0600, H. Peter Anvin wrote:
> On 01/22/2013 09:43 AM, Alan Stern wrote:
> > On Tue, 22 Jan 2013, Oliver Neukum wrote:
> >
> >> On Tuesday 22 January 2013 11:05:35 James Bottomley wrote:
> May 3 18:19:06 relampago3 kernel: [ 3948.472796] sd 7:0:0:0: [sdf]
> 1
On 01/22/2013 09:43 AM, Alan Stern wrote:
> On Tue, 22 Jan 2013, Oliver Neukum wrote:
>
>> On Tuesday 22 January 2013 11:05:35 James Bottomley wrote:
May 3 18:19:06 relampago3 kernel: [ 3948.472796] sd 7:0:0:0: [sdf]
1565565872 512-byte logical blocks: (801 GB/746 GiB)
>>>
>>> This look
On Tue, 22 Jan 2013, Oliver Neukum wrote:
> On Tuesday 22 January 2013 11:05:35 James Bottomley wrote:
> > > May 3 18:19:06 relampago3 kernel: [ 3948.472796] sd 7:0:0:0: [sdf]
> > > 1565565872 512-byte logical blocks: (801 GB/746 GiB)
> >
> > This looks like a wrap around of your actual size. T
On Tue, 2013-01-22 at 12:49 +0100, Oliver Neukum wrote:
> On Tuesday 22 January 2013 11:05:35 James Bottomley wrote:
> > > May 3 18:19:06 relampago3 kernel: [ 3948.472796] sd 7:0:0:0: [sdf]
> > > 1565565872 512-byte logical blocks: (801 GB/746 GiB)
> >
> > This looks like a wrap around of your ac
On Tuesday 22 January 2013 11:05:35 James Bottomley wrote:
> > May 3 18:19:06 relampago3 kernel: [ 3948.472796] sd 7:0:0:0: [sdf]
> > 1565565872 512-byte logical blocks: (801 GB/746 GiB)
>
> This looks like a wrap around of your actual size. This appears to
> indicate the device isn't replying c
;
>
>
>
> -- Forwarded message --
> From: Ellwood Blues
> Date: 2012/6/22
> Subject: Fwd: 2TB USB hard drive for backing up
> To: 678...@bugs.debian.org
>
>
> -- Forwarded message --
> From: Ellwood Blues
> Date: 2012/5/3
>
On Wed, 20 Feb 2008, John LLOYD wrote:
>
>
> > On Mon, 4 Feb 2008, James Bottomley wrote:
> >
> > >
> > > On Mon, 2008-02-04 at 22:28 +0100, Borislav Petkov wrote:
...
> > > > > This does still occur with 2.6.22; with a blank tape in my HP
> DDS-4 drive:
> > > > >
> > > > > $ tar tzvf /dev/ns
> On Mon, 4 Feb 2008, James Bottomley wrote:
>
> >
> > On Mon, 2008-02-04 at 22:28 +0100, Borislav Petkov wrote:
> > > On Mon, Feb 04, 2008 at 03:22:06PM +0100, maximilian attems wrote:
> > >
> > > (Added Bart to CC)
> > >
> > > > hello borislav,
> > > >
...
> > > > This does still occur wit
Forwarded Message
From: Adrian Bunk <[EMAIL PROTECTED]>
To: Sathya Prakash <[EMAIL PROTECTED]>, James Bottomley
<[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: [2.6 patch] message/fusion/mptbase.c: fix use-after-free's
Date: Wed, 20 Feb 2008 02:39:43 +0200
This patch fixes tw
I have received below message from a tester. Can any one please help me
with the /proc/scsi/gdth/0 problem. Where should I look?
Boaz
On Wed, Feb 13 2008 at 8:39 +0200, Tobias Oetiker <[EMAIL PROTECTED]> wrote:
> Hi Boaz,
>
> I just tested the patch to GDTH you published yesterday on LKML.
> Wi
On Tue, 5 Feb 2008, Kai Makisara wrote:
> On Mon, 4 Feb 2008, James Bottomley wrote:
>
> >
> > On Mon, 2008-02-04 at 22:28 +0100, Borislav Petkov wrote:
> > > On Mon, Feb 04, 2008 at 03:22:06PM +0100, maximilian attems wrote:
> > >
> > > (Added Bart to CC)
> > >
> > > > hello borislav,
> > > >
Hello,
Eric Moore is on vacation, adding some CCs and TOs.
-- Forwarded message --
Date: Sun, 10 Feb 2008 18:25:39 +0100 (CET)
From: Krzysztof Oledzki <[EMAIL PROTECTED]>
To: Maximilian Wilhelm <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Kernel Panic
On Mon, 4 Feb 2008, James Bottomley wrote:
>
> On Mon, 2008-02-04 at 22:28 +0100, Borislav Petkov wrote:
> > On Mon, Feb 04, 2008 at 03:22:06PM +0100, maximilian attems wrote:
> >
> > (Added Bart to CC)
> >
> > > hello borislav,
> > >
> > > may i forward you that *old* Debian kernel bug,
> > >
On Mon, 2008-02-04 at 22:28 +0100, Borislav Petkov wrote:
> On Mon, Feb 04, 2008 at 03:22:06PM +0100, maximilian attems wrote:
>
> (Added Bart to CC)
>
> > hello borislav,
> >
> > may i forward you that *old* Debian kernel bug,
> > have seen you working on ide-tape:
> > http://bugs.debian.org/1
Sorry, resend..
--- Begin Message ---
On Sat, 2008-02-02 at 05:26 -0800, Nicholas A. Bellinger wrote:
> Hi Bart,
>
> Ok, I have 2.6.24 running on ppc64 doing iSCSI/HD on PS3-Linux. The
> changes for struct scatterlist->page moving to struct
> scatterlist->page_link where pretty straightforward,
My original email probably got bounced..
--nab
--- Begin Message ---
Greetings all,
On Wed, 2008-01-30 at 19:56 +0900, FUJITA Tomonori wrote:
> On Wed, 30 Jan 2008 09:38:04 +0100
> "Bart Van Assche" <[EMAIL PROTECTED]> wrote:
>
> > On Jan 30, 2008 12:32 AM, FUJITA Tomonori <[EMAIL PROTECTED]> wr
James, can you review and apply this patch?
TIA
Adrian
- Forwarded message from Frederik Deweerdt <[EMAIL PROTECTED]> -
Date: Wed, 16 Jan 2008 17:19:08 +0100
From: Frederik Deweerdt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [trivial patch] scsi/ultrastor:
-- Forwarded message --
From: "Oliver Pinter (Pintér Olivér)" <[EMAIL PROTECTED]>
Date: Sun, 30 Dec 2007 14:20:20 +0100
Subject: [05/06] [typo fix] Documentation/scsi/ChangeLog.lpfc
To: [EMAIL PROTECTED]
--
Thanks,
Oliver
--
Thanks,
Oliver
commit 135c0d1c711a4d423162d75a771d01
On Thu, 2007-12-13 at 11:11 +0100, Miquel van Smoorenburg wrote:
> According to Greg KH:
> > So, what should be added to 2.6.23-stable then? And, can I get a real
> > changelog entry for it?
>
> This is suitable for both 2.6.23.x and 2.6.24-rc5 :
>
> linux-2.6-dpt_i2o-no-dma64.patch
Actually,
According to Greg KH:
> So, what should be added to 2.6.23-stable then? And, can I get a real
> changelog entry for it?
This is suitable for both 2.6.23.x and 2.6.24-rc5 :
linux-2.6-dpt_i2o-no-dma64.patch
The dpt_i2o driver can't handle 64 bit DMA addresses, so do not
let it set pci_set_dma_mas
On Wed, Dec 12, 2007 at 02:54:54PM -0500, James Bottomley wrote:
>
> On Wed, 2007-12-12 at 11:16 -0800, Andrew Morton wrote:
> > On Wed, 12 Dec 2007 14:43:42 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
> >
> > > Am 12.12.2007 schrieb Miquel van Smoorenburg:
> > > > On Wed, 2007-12-12 at 03:38 -
On Wed, 2007-12-12 at 11:16 -0800, Andrew Morton wrote:
> On Wed, 12 Dec 2007 14:43:42 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
>
> > Am 12.12.2007 schrieb Miquel van Smoorenburg:
> > > On Wed, 2007-12-12 at 03:38 -0800, Andrew Morton wrote:
> > > > On Wed, 12 Dec 2007 11:58:41 +0100 Anders
On Wed, 12 Dec 2007 14:43:42 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
> Am 12.12.2007 schrieb Miquel van Smoorenburg:
> > On Wed, 2007-12-12 at 03:38 -0800, Andrew Morton wrote:
> > > On Wed, 12 Dec 2007 11:58:41 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi,
> > > >
> > >
Am 12.12.2007 schrieb Andrew Morton:
> On Wed, 12 Dec 2007 11:58:41 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I'd like to let you now that my boxes are running a 32-bit kernel, so
> > the 64-bit-uncleanliness shouldn't apply to my boxes; however,
> >
> > http://www.miquels.
Am 12.12.2007 schrieb Miquel van Smoorenburg:
> On Wed, 2007-12-12 at 03:38 -0800, Andrew Morton wrote:
> > On Wed, 12 Dec 2007 11:58:41 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
> >
> > > Hi,
> > >
> > > I'd like to let you now that my boxes are running a 32-bit kernel, so
> > > the 64-bit-u
ACK, patch looks good. Thanks for composing this patch. Glad to hear of
successful test results.
Sincerely -- Mark Salyzyn
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Miquel
> van Smoorenburg
. . .
>
> I just recompiled 2.6.23.9 with the 64 b
On Wed, 2007-12-12 at 03:38 -0800, Andrew Morton wrote:
> On Wed, 12 Dec 2007 11:58:41 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > I'd like to let you now that my boxes are running a 32-bit kernel, so
> > the 64-bit-uncleanliness shouldn't apply to my boxes; however,
> >
> >
On Wed, 12 Dec 2007 11:58:41 +0100 Anders Henke <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'd like to let you now that my boxes are running a 32-bit kernel, so
> the 64-bit-uncleanliness shouldn't apply to my boxes; however,
>
> http://www.miquels.cistron.nl/linux/dpt_i2o-64bit-2.6.23.patch
>
> fixe
Hi,
I'd like to let you now that my boxes are running a 32-bit kernel, so
the 64-bit-uncleanliness shouldn't apply to my boxes; however,
http://www.miquels.cistron.nl/linux/dpt_i2o-64bit-2.6.23.patch
fixed the issue on my testbox.
I took a clean 2.6.23, applied patch, recompiled the kernel, reb
On Tue, 2007-12-11 at 15:40 +0100, Miquel van Smoorenburg wrote:
> I just noticed the same bug when I tried to update a 2.6.18 server to
> 2.6.23.9 .. also tried 2.6.24-rc4. The symptom I'm seeing is that init
> segfaults, or can't be found .. anyway, driver/fs errors.
>
> In the kernel config, un
Miquel van Smoorenburg sez:
> I got the 64-bit dpt_i2o driver from Adaptec some time ago, and I have
> added 64-bit support to the 2.6.23.1 dpt_i2o driver based on that
> driver. I intended to submit it for 2.6.25 or so ... if I
> have some time
> later today or tomorrow I'll try that next to see
On Fri, 2007-11-30 at 11:34 +0100, Anders Henke wrote:
> Am 30.11.2007 schrieb FUJITA Tomonori:
> > > > > According to the 2.6.23-rc1 short-form changelog, there is
> > > > > one major edit on the dpt_i2o driver:
> > > > >
> > > > > FUJITA Tomonori
> > > > >
> > > > > [SCSI] dpt_i2o: conve
Am 29.11.2007 schrieb Matthew Wilcox:
> On Thu, Nov 29, 2007 at 05:45:57PM +0100, Anders Henke wrote:
> > On Nov 29 2007, FUJITA Tomonori wrote:
> > > @@ -3295,7 +3295,7 @@ static struct scsi_host_template adpt_template = {
> > > .this_id= 7,
> > > .cmd_per_lun= 1,
>
Am 30.11.2007 schrieb FUJITA Tomonori:
> > > > According to the 2.6.23-rc1 short-form changelog, there is
> > > > one major edit on the dpt_i2o driver:
> > > >
> > > > FUJITA Tomonori
> > > >
> > > > [SCSI] dpt_i2o: convert to use the data buffer accessors
> > > >
> > > > Stephen Rothwell
On Thu, 29 Nov 2007 17:45:57 +0100
Anders Henke <[EMAIL PROTECTED]> wrote:
> On Nov 29 2007, FUJITA Tomonori wrote:
> > On Thu, 29 Nov 2007 14:03:19 +0100
> > Jan Kara <[EMAIL PROTECTED]> wrote:
> >
> > > Adding relevant people and lists to CC...
> > >
> > >
On Thu, Nov 29, 2007 at 05:45:57PM +0100, Anders Henke wrote:
> On Nov 29 2007, FUJITA Tomonori wrote:
> > @@ -3295,7 +3295,7 @@ static struct scsi_host_template adpt_template = {
> > .this_id= 7,
> > .cmd_per_lun= 1,
> > .use_clustering = ENABLE_CLUS
On Nov 29 2007, FUJITA Tomonori wrote:
> On Thu, 29 Nov 2007 14:03:19 +0100
> Jan Kara <[EMAIL PROTECTED]> wrote:
>
> > Adding relevant people and lists to CC...
> >
> > Honza
> >
> > - Forwarded message from Anders Henke
On Thu, 29 Nov 2007 14:03:19 +0100
Jan Kara <[EMAIL PROTECTED]> wrote:
> Adding relevant people and lists to CC...
>
> Honza
>
> - Forwarded message from Anders Henke <[EMAIL PROTECTED]> -
>
> Date: Thu, 29 Nov 2007
Adding relevant people and lists to CC...
Honza
- Forwarded message from Anders Henke <[EMAIL PROTECTED]> -
Date: Thu, 29 Nov 2007 13:31:50 +0100
From: Anders Henke <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subje
On Wed, 31 Oct 2007, James Bottomley wrote:
> > Dropping a kobject's reference to its parent when the kobject is
> > removed rather than when it is deleted will solve all these problems.
> > The queue's reference to the gendisk and the gendisk's reference to the
> > device will both be dropped w
On Wed, 31 Oct 2007, James Bottomley wrote:
> But you're assuming the relationship gendisk->queue exists when we
> delete the scsi device. What should happen is that the gendisk should
> be released first in the ULD detach. Queues are allowed to exist
> without gendisks (when a SCSI queue is fir
On Wed, 2007-10-31 at 11:46 -0500, James Bottomley wrote:
> On Wed, 2007-10-31 at 17:42 +0100, Kay Sievers wrote:
> > On Wed, 2007-10-31 at 11:31 -0500, James Bottomley wrote:
> > > Doesn't this circularity now exist for everything? Every device that
> > > creates a queue has a reference to the q
On Wed, 2007-10-31 at 12:44 -0400, Alan Stern wrote:
> On Wed, 31 Oct 2007, James Bottomley wrote:
>
> > OK, light beginning to go on now.
> >
> > The problem is that you've fallen into the conceptual trap we tried very
> > hard to avoid in the initial go around of joining SCSI upper layer
> > dr
On Wed, 31 Oct 2007, James Bottomley wrote:
> OK, light beginning to go on now.
>
> The problem is that you've fallen into the conceptual trap we tried very
> hard to avoid in the initial go around of joining SCSI upper layer
> drivers to gendisks. That's why no gendisk references are held by th
On Wed, 2007-10-31 at 17:42 +0100, Kay Sievers wrote:
> On Wed, 2007-10-31 at 11:31 -0500, James Bottomley wrote:
> > On Wed, 2007-10-31 at 17:24 +0100, Kay Sievers wrote:
> > > On Wed, 2007-10-31 at 11:13 -0500, James Bottomley wrote:
> > > > On Wed, 2007-10-31 at 12:04 -0400, Alan Stern wrote:
>
On Wed, 2007-10-31 at 11:31 -0500, James Bottomley wrote:
> On Wed, 2007-10-31 at 17:24 +0100, Kay Sievers wrote:
> > On Wed, 2007-10-31 at 11:13 -0500, James Bottomley wrote:
> > > On Wed, 2007-10-31 at 12:04 -0400, Alan Stern wrote:
> > > > On Wed, 31 Oct 2007, James Bottomley wrote:
> > > >
> >
On Wed, 2007-10-31 at 17:24 +0100, Kay Sievers wrote:
> On Wed, 2007-10-31 at 11:13 -0500, James Bottomley wrote:
> > On Wed, 2007-10-31 at 12:04 -0400, Alan Stern wrote:
> > > On Wed, 31 Oct 2007, James Bottomley wrote:
> > >
> > > > > Yes, the queue is a child of the disk.
> > > >
> > > > Right
On Wed, 2007-10-31 at 11:13 -0500, James Bottomley wrote:
> On Wed, 2007-10-31 at 12:04 -0400, Alan Stern wrote:
> > On Wed, 31 Oct 2007, James Bottomley wrote:
> >
> > > > Yes, the queue is a child of the disk.
> > >
> > > Right, so this goes gendisk->queue (-> meaning parent of, or takes
> > >
On Wed, 2007-10-31 at 12:04 -0400, Alan Stern wrote:
> On Wed, 31 Oct 2007, James Bottomley wrote:
>
> > > Yes, the queue is a child of the disk.
> >
> > Right, so this goes gendisk->queue (-> meaning parent of, or takes
> > reference to)
>
> No, no! The _child_ takes an implicit reference to t
On Wed, 2007-10-31 at 11:58 -0400, Alan Stern wrote:
> On Wed, 31 Oct 2007, James Bottomley wrote:
>
> > On Wed, 2007-10-31 at 07:32 -0700, Greg KH wrote:
> > > Hm, I seem to have missed the part in this thread where someone said
> > > that it was valid to have a parent reference a child device.
On Wed, 31 Oct 2007, James Bottomley wrote:
> > Yes, the queue is a child of the disk.
>
> Right, so this goes gendisk->queue (-> meaning parent of, or takes
> reference to)
No, no! The _child_ takes an implicit reference to the _parent_, not
the other way around.
> > > The scsi_device has a
On Wed, 31 Oct 2007, James Bottomley wrote:
> On Wed, 2007-10-31 at 07:32 -0700, Greg KH wrote:
> > Hm, I seem to have missed the part in this thread where someone said
> > that it was valid to have a parent reference a child device. That's
> > just wrong and needs to be fixed. Is that in the sc
On Tue, 30 Oct 2007, Greg KH wrote:
> > Since the SCSI stack is now in much better shape, there doesn't seem to
> > be any reason to keep the old code. Do you agree that the patch below
> > is worth merging? I submitted it to Greg some time ago, but he didn't
> > want to accept it without som
On Wed, 2007-10-31 at 16:40 +0100, Kay Sievers wrote:
> On Wed, 2007-10-31 at 10:15 -0500, James Bottomley wrote:
> > On Wed, 2007-10-31 at 07:32 -0700, Greg KH wrote:
> > > Hm, I seem to have missed the part in this thread where someone said
> > > that it was valid to have a parent reference a chi
On Wed, 2007-10-31 at 10:15 -0500, James Bottomley wrote:
> On Wed, 2007-10-31 at 07:32 -0700, Greg KH wrote:
> > Hm, I seem to have missed the part in this thread where someone said
> > that it was valid to have a parent reference a child device. That's
> > just wrong and needs to be fixed. Is t
On Wed, 2007-10-31 at 07:32 -0700, Greg KH wrote:
> Hm, I seem to have missed the part in this thread where someone said
> that it was valid to have a parent reference a child device. That's
> just wrong and needs to be fixed. Is that in the scsi layer somewhere?
> The block layer? It sure isn't
On Wed, Oct 31, 2007 at 11:46:30AM +0100, Kay Sievers wrote:
> On Tue, 2007-10-30 at 21:25 -0700, Greg KH wrote:
> > On Mon, Oct 29, 2007 at 08:13:17PM +0100, Kay Sievers wrote:
> > > On Mon, 2007-10-29 at 14:47 -0400, Alan Stern wrote:
> > > > On Mon, 29 Oct 2007, James Bottomley wrote:
> > > >
>
On Tue, 2007-10-30 at 21:25 -0700, Greg KH wrote:
> On Mon, Oct 29, 2007 at 08:13:17PM +0100, Kay Sievers wrote:
> > On Mon, 2007-10-29 at 14:47 -0400, Alan Stern wrote:
> > > On Mon, 29 Oct 2007, James Bottomley wrote:
> > >
> > > > I'm not sure if we can do this patch. If you kill a device, you
On Mon, Oct 29, 2007 at 08:13:17PM +0100, Kay Sievers wrote:
> On Mon, 2007-10-29 at 14:47 -0400, Alan Stern wrote:
> > On Mon, 29 Oct 2007, James Bottomley wrote:
> >
> > > I'm not sure if we can do this patch. If you kill a device, you see
> > > there's a processing state in scsi_prep_fn() for
On Mon, Oct 29, 2007 at 02:47:59PM -0400, Alan Stern wrote:
> On Mon, 29 Oct 2007, James Bottomley wrote:
>
> > I'm not sure if we can do this patch. If you kill a device, you see
> > there's a processing state in scsi_prep_fn() for SDEV_DEL, which has a
> > printk message I see quite often when
On Mon, 2007-10-29 at 14:47 -0400, Alan Stern wrote:
> On Mon, 29 Oct 2007, James Bottomley wrote:
>
> > I'm not sure if we can do this patch. If you kill a device, you see
> > there's a processing state in scsi_prep_fn() for SDEV_DEL, which has a
> > printk message I see quite often when I unplu
On Mon, 29 Oct 2007, James Bottomley wrote:
> I'm not sure if we can do this patch. If you kill a device, you see
> there's a processing state in scsi_prep_fn() for SDEV_DEL, which has a
> printk message I see quite often when I unplug devices while they're
> operating.
>
> If you NULL out and f
1 - 100 of 145 matches
Mail list logo
