email from Martin K. Petersen from 05/18/18 18:26 he
applied this patch to 4.18/scsi-queue.
Link: https://www.spinics.net/lists/target-devel/msg16743.html
HTH
Bodo
url:
https://github.com/0day-ci/linux/commits/Bodo-Stroesser/TCMUser-add-read-length-support/20180526-231412
config: x86_64-ra
mpletion(). Now code is easier to understand.
Signed-off-by: Bodo Stroesser
Acked-by: Mike Christie
---
include/uapi/linux/target_core_user.h |4 ++-
drivers/target/target_core_user.c | 44 +++---
2 files changed, 39 insertions(+), 9 deletions(-)
---
> When a tape drive is exported via LIO using the pscsi module, a read that
> requests more bytes per block than the tape can supply returns an empty
> buffer. This is because the pscsi pass-through target module sees the
> "ILI" illegal length bit set and thinks there is no reason to return
> the
From: Bodo Stroesser
Date: Mon, 2 Dec 2013 18:52:10 +0100
Subject: [PATCH 1/3] st.ko: fix enlarge_buffer
This patch removes a bug in enlarge_buffer() that can make a
read or write fail under special conditions.
After changing TRY_DIRECT_IO to 0 and ST_MAX_SG to 32 in
st_options.h, a program
Hi Kai,
here is a short series of 3 small patches for st.ko
The first one removes a bug in enlarge_buffer() that can make
a read or write fail under special conditions.
The second one removes a small piece of code in enlarge_buffer(),
that AFAICS is not necessary.
If enlarge_buffer() fails, the
From: Bodo Stroesser
Date: Mon, 2 Dec 2013 18:52:10 +0100
Subject: [PATCH 2/3] st.ko: remove unnecessary normalize_buffer
This patch removes an unnecessary call to normalize_buffer()
in enlarge_buffer()
In st_open() always a buffer of one page is allocated.
When the buffer needs to be enlarged
From: Bodo Stroesser
Date: Mon, 2 Dec 2013 18:52:10 +0100
Subject: [PATCH 3/3] st.ko: change enlarge_buffer result
enlarge_buffer() just returns 1 or 0 if it could or could
not allocate the requested buffer.
In case of result 0, the callers always set the error to
EOVERFLOW. I think, this is
On 14.11.2013, at 22.50, Joe Lawrence wrote:
> On Thu, 14 Nov 2013 20:22:40 +0100
> Bodo Stroesser wrote:
>
> > On 14.11.2013, at 20.05, Kai M??kisara (Kolumbus)
> > wrote:
> >
> > >
> > > On 14.11.2013, at 16.48, Bodo Stroesser wrote:
&g
On 14.11.2013, at 20.05, Kai Mäkisara (Kolumbus)
wrote:
>
> On 14.11.2013, at 16.48, Bodo Stroesser wrote:
>
> > Hi,
> >
> > in st_probe(), st.c I stumbled across what I'd call a minor problem.
> >
> > So I'd like to suggest the
Hi,
in st_probe(), st.c I stumbled across what I'd call a minor problem.
So I'd like to suggest the following patch.
Best Regards,
Bodo
P.S.: Please CC me, I'm not on the list.
-----
From: Bodo Stroesser
Date: T
Bodo Stroesser wrote:
Hi,
my dual Xeon machine freezes, if connection between
FC switch and tape drives is broken while writing to tapes.
There is one SCSI target with 16 tape LUNs connected to my
FC controller via FC switch. I can reproduce the problem by
starting "dd if=/dev/zero of=/d
Mike Anderson wrote:
Bodo Stroesser [EMAIL PROTECTED] wrote:
Hi James,
disrupting a working FC connection makes my i386 SMP server
(2.6.12.2) freeze just one or two seconds after this.
I'm normally using lpfc_nodev_tmo = 1. When I change this to the
default value of 35, the system s
Hi James,
disrupting a working FC connection makes my i386 SMP server
(2.6.12.2) freeze just one or two seconds after this.
I'm normally using lpfc_nodev_tmo = 1. When I change this to the
default value of 35, the system stalls about 36 seconds after
disruption. So I guess, the problem is caused
13 matches
Mail list logo
