From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: matthew@wil.cx, linux-scsi@vger.kernel.org,
fujita.tomonori@lab.ntt.co.jp, gregkh@suse.de,
chrisw@sous-sol.org
Subject: Re: Advansys regression between 2.6.23.8 and 2.6.24.2
Date: Thu, 14 Feb 2008 09:50:58 -0600 [thread overview]
Message-ID: <1203004258.3189.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20080214161024.2a0c0f17@crazy>
On Thu, 2008-02-14 at 16:10 +0100, Thomas Petazzoni wrote:
> I just upgraded my system from 2.6.23.8 to 2.6.24.2, and when loading
> the advansys module, it paniced, with "Kernel BUG at advansys.c:6335".
> The issue is that the overrun buffer is not aligned on 8 bytes.
>
> The patch 7d5d408c77cee95d1380511de46b7a4c8dc2211d [1], by FUJITA
> Tomonori, which has been committed a few days ago, fixes the issue. The
> commit log says that the structure should be 8-byte aligned on 2.6.23
> and 2.6.24, but it doesn't seem to be the case in 2.6.24. I have not
> identified which commit broke the driver, but I confirm that Tomonori's
> patch fixes the problem.
>
> I've added Greg and Chris as Cc: because such a patch should probably
> be included in the next -stable of 2.6.24, but of course Tomonori and
> Matthew are best placed to say what should be done.
Yes, it's already on its way to stable. The process requires the fix to
be committed upstream first. There's an automated script that sends
these commits back to stable once they're upstream (provided they're
tagged correctly).
James
next prev parent reply other threads:[~2008-02-14 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 15:10 Advansys regression between 2.6.23.8 and 2.6.24.2 Thomas Petazzoni
2008-02-14 15:14 ` Thomas Petazzoni
2008-02-14 15:50 ` James Bottomley [this message]
2008-02-26 14:55 ` Thomas Petazzoni
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=1203004258.3189.20.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=chrisw@sous-sol.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=gregkh@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=thomas.petazzoni@free-electrons.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox