From: <gregkh@linuxfoundation.org>
To: gregkh@linuxfoundation.org, andersen@codepoet.org,
christian.koenig@amd.com, nicolai.haehnle@amd.com
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "Revert "drm/radeon: hold reference to fences in radeon_sa_bo_new"" has been added to the 3.10-stable tree
Date: Mon, 07 Mar 2016 14:58:41 -0800 [thread overview]
Message-ID: <1457391521218108@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
Revert "drm/radeon: hold reference to fences in radeon_sa_bo_new"
to the 3.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
revert-drm-radeon-hold-reference-to-fences-in-radeon_sa_bo_new.patch
and it can be found in the queue-3.10 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From foo@baz Mon Mar 7 14:56:11 PST 2016
Date: Mon, 07 Mar 2016 14:56:11 -0800
To: Greg KH <gregkh@linuxfoundation.org>
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Revert "drm/radeon: hold reference to fences in radeon_sa_bo_new"
This reverts commit 8d5e1e5af0c667545c202e8f4051f77aa3bf31b7 which was
commit f6ff4f67cdf8455d0a4226eeeaf5af17c37d05eb upstream.
It breaks working hardware, a backported version might be provided at
some unknown time in the future.
Reported-by: Erik Andersen <andersen@codepoet.org>
Acked-by: Christian König <christian.koenig@amd.com>
Cc: Nicolai Hähnle <nicolai.haehnle@amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/gpu/drm/radeon/radeon_sa.c | 5 -----
1 file changed, 5 deletions(-)
--- a/drivers/gpu/drm/radeon/radeon_sa.c
+++ b/drivers/gpu/drm/radeon/radeon_sa.c
@@ -349,13 +349,8 @@ int radeon_sa_bo_new(struct radeon_devic
/* see if we can skip over some allocations */
} while (radeon_sa_bo_next_hole(sa_manager, fences, tries));
- for (i = 0; i < RADEON_NUM_RINGS; ++i)
- radeon_fence_ref(fences[i]);
-
spin_unlock(&sa_manager->wq.lock);
r = radeon_fence_wait_any(rdev, fences, false);
- for (i = 0; i < RADEON_NUM_RINGS; ++i)
- radeon_fence_unref(&fences[i]);
spin_lock(&sa_manager->wq.lock);
/* if we have nothing to wait for block */
if (r == -ENOENT && block) {
Patches currently in stable-queue which might be from gregkh@linuxfoundation.org are
queue-3.10/alsa-hdspm-fix-zero-division.patch
queue-3.10/x86-entry-compat-add-missing-clac-to-entry_int80_32.patch
queue-3.10/pm-sleep-x86-fix-crash-on-graph-trace-through-x86-suspend.patch
queue-3.10/ubi-fix-out-of-bounds-write-in-volume-update-code.patch
queue-3.10/cifs-fix-smb2-interim-response-processing-for-read-requests.patch
queue-3.10/alsa-ctl-fix-ioctls-for-x32-abi.patch
queue-3.10/alsa-hdspm-fix-wrong-boolean-ctl-value-accesses.patch
queue-3.10/revert-jffs2-fix-lock-acquisition-order-bug-in-jffs2_write_begin.patch
queue-3.10/usb-cp210x-add-id-for-parrot-nmea-gps-flight-recorder.patch
queue-3.10/alsa-hdsp-fix-wrong-boolean-ctl-value-accesses.patch
queue-3.10/locks-fix-unlock-when-fcntl_setlk-races-with-a-close.patch
queue-3.10/libata-align-ata_device-s-id-on-a-cacheline.patch
queue-3.10/usb-serial-option-add-support-for-quectel-uc20.patch
queue-3.10/alsa-seq-oss-don-t-drain-at-closing-a-client.patch
queue-3.10/usb-serial-option-add-support-for-telit-le922-pid-0x1045.patch
queue-3.10/alsa-timer-fix-ioctls-for-x32-abi.patch
queue-3.10/alsa-timer-fix-broken-compat-timer-user-status-ioctl.patch
queue-3.10/edac-mc_sysfs-fix-freeing-bus-name.patch
queue-3.10/libata-fix-hdio_get_32bit-ioctl.patch
queue-3.10/alsa-rawmidi-fix-ioctls-x32-abi.patch
queue-3.10/drm-ast-fix-incorrect-register-check-for-dram-width.patch
queue-3.10/jffs2-fix-page-lock-f-sem-deadlock.patch
queue-3.10/fix-directory-hardlinks-from-deleted-directories.patch
queue-3.10/revert-drm-radeon-hold-reference-to-fences-in-radeon_sa_bo_new.patch
reply other threads:[~2016-03-07 22:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1457391521218108@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andersen@codepoet.org \
--cc=christian.koenig@amd.com \
--cc=nicolai.haehnle@amd.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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.