From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, dgilbert@interlog.com,
Johannes Thumshirn <jth@kernel.org>
Subject: Re: [PATCHv4 0/6] sanitize sg
Date: Tue, 11 Apr 2017 20:56:43 -0400 [thread overview]
Message-ID: <yq1shlev3xw.fsf@oracle.com> (raw)
In-Reply-To: <1491550457-78302-1-git-send-email-hare@suse.de> (Hannes Reinecke's message of "Fri, 7 Apr 2017 09:34:11 +0200")
Hannes,
> the infamous syzkaller incovered some more issues in the sg driver.
> This patchset fixes those two issues (and adds a fix for yet another
> potential issue; checking for a NULL dxferp when dxfer_len is not 0).
> It also removes handling of the SET_FORCE_LOW_DMA ioctl, which never
> worked since the initial git checkin. And does some code cleanup by
> removing the private list implementation, using standard lists
> instead.
Applied to 4.12/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-04-12 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 7:34 [PATCHv4 0/6] sanitize sg Hannes Reinecke
2017-04-07 7:34 ` [PATCHv4 1/6] sg: disable SET_FORCE_LOW_DMA Hannes Reinecke
2017-04-07 7:34 ` [PATCHv4 2/6] sg: remove 'save_scat_len' Hannes Reinecke
2017-04-07 7:34 ` [PATCHv4 3/6] sg: protect accesses to 'reserved' page array Hannes Reinecke
2017-04-07 7:34 ` [PATCHv4 4/6] sg: check for valid direction before starting the request Hannes Reinecke
2017-04-07 7:34 ` [PATCHv4 5/6] sg: use standard lists for sg_requests Hannes Reinecke
2017-04-07 7:34 ` [PATCHv4 6/6] sg: close race condition in sg_remove_sfp_usercontext() Hannes Reinecke
2017-04-12 0:56 ` Martin K. Petersen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq1shlev3xw.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=jth@kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.