> Hello.
>
> On 03/06/2017 05:20 PM, Elena Reshetova wrote:
>
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situa
> On 03/06/2017 03:21 PM, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situations.
>
> The
> "Mauricio" == Mauricio Faria de Oliveira
> writes:
Mauricio,
Mauricio> Please flag this patch for stable.
Mauricio> This patch resolves a serious problem on IBM Power systems at
Mauricio> least.
Both patches are already upstream so I can't tag them for stable. Either
you or James sh
On Mon, Mar 06, 2017 at 04:20:58PM +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
Hi Elena,
On Mon, Mar 06, 2017 at 04:20:59PM +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> sit
Hi Elena,
On Mon, Mar 06, 2017 at 04:21:00PM +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> sit
> Was the invalid LUN in the LUN0 position. Inquiry of LUN0 support (when LUN0
> is not populated)
> was added only recently to address host side issue.
How does HyperV expect device scanning to happen for a not populated LUN?
REPORT SUPPORTED LUNS but nothing else on LUN 0? Maybe a TEST UNIT R
On 3/7/2017 10:52 AM, Reshetova, Elena wrote:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshet
2017-03-07 1:54 GMT+01:00 V :
> Hi,
>
> I am reaching out regarding a SCSI error handler issue, which we see
> in our lab systems.
>
> Environment: Ubuntu 4.4.0-31-generic
>
> Issue: Write IOs are getting stuck in our system randomly. All drives
> seen with the issue are all SATA drives.
> Root cau
Hi Martin,
On 03/07/2017 12:35 AM, Martin K. Petersen wrote:
Mauricio> Please flag this patch for stable.
Both patches are already upstream so I can't tag them for stable. Either
you or James should mail sta...@vger.kernel.org and request for the
patches to be queued up.
Right, sorry; I mis
Martin,
On 03/07/2017 02:24 AM, Benjamin Herrenschmidt wrote:
On Mon, 2017-03-06 at 22:46 -0500, Martin K. Petersen wrote:
I don't recall a consensus being reached on this patch.
What would be the opposition ? Without it kexec breaks. With it, it
works ...
That is the argument I'd present
> -Original Message-
> From: Christoph Hellwig [mailto:h...@lst.de]
> Sent: Monday, March 6, 2017 9:06 PM
> To: KY Srinivasan
> Cc: Stephen Hemminger ; James
> Bottomley ; Hannes Reinecke
> ; Christoph Hellwig ; James Bottomley
> ; Jens Axboe ; Linus Torvalds
> ; Martin K. Petersen
> ; D
On Mon 06-03-17 09:25:42, James Bottomley wrote:
> On Mon, 2017-03-06 at 17:13 +0100, Jan Kara wrote:
> > On Mon 06-03-17 07:44:55, James Bottomley wrote:
...
> > > > Sure. The call trace is:
> > > >
> > > > [ 41.919244] [ cut here ]
> > > > [ 41.919263] WARNING: CPU: 4
> Hi Elena,
>
> On Mon, Mar 06, 2017 at 04:20:59PM +0200, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-a
> Hi Elena,
>
> On Mon, Mar 06, 2017 at 04:21:00PM +0200, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-af
> -Original Message-
> From: Hannes Reinecke [mailto:h...@suse.de]
> Sent: Thursday, February 23, 2017 4:55 AM
> To: Martin K. Petersen
> Cc: Christoph Hellwig ; James Bottomley
> ; linux-scsi@vger.kernel.org;
> Hannes Reinecke ; Don Brace
> ; Hannes Reinecke
> Subject: [PATCHv2] hpsa: ex
Hello stable kernel maintainers,
On 03/07/2017 12:35 AM, Martin K. Petersen wrote:
Mauricio> Please flag this patch for stable.
Mauricio> This patch resolves a serious problem on IBM Power systems at
Mauricio> least.
Both patches are already upstream so I can't tag them for stable. Either
you
On 03/07/2017 04:05 PM, Don Brace wrote:
>> -Original Message-
>> From: Hannes Reinecke [mailto:h...@suse.de]
>> Sent: Thursday, February 23, 2017 4:55 AM
>> To: Martin K. Petersen
>> Cc: Christoph Hellwig ; James Bottomley
>> ; linux-scsi@vger.kernel.org;
>> Hannes Reinecke ; Don Brace
>>
Base on the last email i sent to you, I wish to bring to your notice
that i am still waiting patiently for your response. Mrs. Anna
Johnson.
On Tue 07-03-17 08:10:29, James Bottomley wrote:
> On Tue, 2017-03-07 at 15:41 +0100, Jan Kara wrote:
> > On Mon 06-03-17 09:25:42, James Bottomley wrote:
> > > On Mon, 2017-03-06 at 17:13 +0100, Jan Kara wrote:
> > > > On Mon 06-03-17 07:44:55, James Bottomley wrote:
> > ...
> > > > > > Sure. The
On Tue, 2017-03-07 at 15:41 +0100, Jan Kara wrote:
> On Mon 06-03-17 09:25:42, James Bottomley wrote:
> > On Mon, 2017-03-06 at 17:13 +0100, Jan Kara wrote:
> > > On Mon 06-03-17 07:44:55, James Bottomley wrote:
> ...
> > > > > Sure. The call trace is:
> > > > >
> > > > > [ 41.919244] --
On Mon, Mar 06, 2017 at 04:20:55PM +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
L
On Mon, Mar 06, 2017 at 04:20:57PM +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
From: James Smart
Reviewing the result of what was just added for Kconfig, we made
a poor choice. It worked well for full kernel builds, but not so
much for how it would be deployed on a distro.
Here's the final result:
- lpfc will compile in NVME initiator and/or NVME target support
based on
Hyper-V host emulation of SCSI for virtual DVD device reports SCSI
version 0 (UNKNOWN) but is still capable of supporting REPORTLUN.
Without this patch, a GEN2 Linux guest on Hyper-V will not boot 4.11
successfully with virtual DVD ROM device. What happens is that the
SCSI scan process falls back
On Tue, Mar 07, 2017 at 10:44:51AM -0300, Mauricio Faria de Oliveira wrote:
> Hello stable kernel maintainers,
>
> On 03/07/2017 12:35 AM, Martin K. Petersen wrote:
> > Mauricio> Please flag this patch for stable.
> >
> > Mauricio> This patch resolves a serious problem on IBM Power systems at
> >
> -Original Message-
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Tuesday, March 7, 2017 9:16 AM
> To: KY Srinivasan ; Haiyang Zhang
> ; Long Li ;
> martin.peter...@oracle.com; h...@lst.de; h...@suse.de
> Cc: linux-scsi@vger.kernel.org; linux-ker...@vger.kernel.or
> +#if defined(CONFIG_NVME_FC)
> +#define CONFIG_LPFC_NVME_INITIATOR
> +#endif
> +
> +#if defined(CONFIG_NVME_TARGET_FC)
> +#define CONFIG_LPFC_NVME_TARGET
> +#endif
The CONFIG_* namespace is reserved for Kconfig defined symbols.
Also I think the above is wrong if the nvme fc core code is built
m
On Tue, Mar 7, 2017 at 3:58 AM, Jack Wang wrote:
> 2017-03-07 1:54 GMT+01:00 V :
>> Hi,
>>
>> I am reaching out regarding a SCSI error handler issue, which we see
>> in our lab systems.
>>
>> Environment: Ubuntu 4.4.0-31-generic
>>
>> Issue: Write IOs are getting stuck in our system randomly. All
> -Original Message-
> From: Hannes Reinecke [mailto:h...@suse.com]
> Sent: Tuesday, March 07, 2017 9:25 AM
> To: Don Brace ; Hannes Reinecke
> ; Martin K. Petersen
> Cc: Christoph Hellwig ; James Bottomley
> ; linux-scsi@vger.kernel.org
> Subject: Re: [PATCHv2] hpsa: expose enclosures
>
On 3/7/2017 1:23 PM, Christoph Hellwig wrote:
+#if defined(CONFIG_NVME_FC)
+#define CONFIG_LPFC_NVME_INITIATOR
+#endif
+
+#if defined(CONFIG_NVME_TARGET_FC)
+#define CONFIG_LPFC_NVME_TARGET
+#endif
The CONFIG_* namespace is reserved for Kconfig defined symbols.
Also I think the above is wrong
Thanks Stephen,
this looks good to me:
Reviewed-by: Christoph Hellwig
> "Mauricio" == Mauricio Faria de Oliveira
> writes:
Mauricio> I think I should have included this in the tested-by tag
Mauricio> email, for documentation/evidence: no regression observed in
Mauricio> system shutdown path.
Applied to 4.11/scsi-fixes.
--
Martin K. Petersen Oracle
> "Stephen" == Stephen Hemminger writes:
Stephen,
Stephen> Hyper-V host emulation of SCSI for virtual DVD device reports
Stephen> SCSI version 0 (UNKNOWN) but is still capable of supporting
Stephen> REPORTLUN.
Stephen> Without this patch, a GEN2 Linux guest on Hyper-V will not boot
Stephen>
> "Greg" == Greg KH writes:
Greg,
>> Can this commit be included on stable v4.4+ , please? (in Linus tree)
>>
>> 8ea73db486cda442f0671f4bc9c03a76be398a28 "scsi: lpfc: Correct WQ
>> creation for pagesize"
Greg> I need an ack from a scsi maintainer that this is an ok thing to
Greg> do before
On Mon, 2017-03-06 at 00:43 +, Bart Van Assche wrote:
> On Fri, 2017-02-24 at 13:37 -0800, Himanshu Madhani wrote:
> > Please consider this series for inclusion in target-pending.
>
> Hello Himanshu,
>
> I applied this patch series on top of kernel v4.11-rc1 and installed it on
> a test syste
Hi Elena,
On Mon, 2017-03-06 at 16:21 +0200, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations
37 matches
Mail list logo