All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 15001] megaraid_sas fills dmesg with megasas: Failed to copy out to user sense data
Date: Wed, 3 Feb 2010 13:41:48 GMT	[thread overview]
Message-ID: <201002031341.o13DfmY0000507@demeter.kernel.org> (raw)
In-Reply-To: <bug-15001-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=15001





--- Comment #5 from Tomas Henzl <thenzl@redhat.com>  2010-02-03 13:41:44 ---
Created an attachment (id=24890)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=24890)
patch to handle compat apps

The issue is probably caused by a 32bit application in a 64bit os. The 'open
manage' here uses a 32bit pointer and the driver after the 'SCSI: megaraid_sas:
fix 64 bit sense pointer truncation' works with it as if it was a 64bit
pointer.
The attached patch handles the situation on my test box.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-02-03 13:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 12:42 [Bug 15001] New: megaraid_sas fills dmesg with megasas: Failed to copy out to user sense data bugzilla-daemon
2010-01-08 16:21 ` [Bug 15001] " bugzilla-daemon
2010-01-11 11:04 ` bugzilla-daemon
2010-01-11 11:12 ` bugzilla-daemon
2010-01-15 12:09 ` bugzilla-daemon
2010-02-03 13:41 ` bugzilla-daemon [this message]
2010-02-04 11:00 ` bugzilla-daemon
2010-02-04 13:22 ` bugzilla-daemon
2010-02-04 14:29 ` bugzilla-daemon
2010-02-04 15:36 ` bugzilla-daemon
2010-02-05  7:34 ` bugzilla-daemon
2010-02-05 14:16 ` bugzilla-daemon
2010-02-05 14:51 ` bugzilla-daemon
2010-02-11 13:31 ` bugzilla-daemon

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=201002031341.o13DfmY0000507@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.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.