linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: stable@kernel.org, Evgeniy <dushistov@mail.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: [STABLE] Fix oops in ufs_fill_super at mount time
Date: Sun, 15 Jan 2006 10:11:17 -0800	[thread overview]
Message-ID: <20060115181117.GM3335@sorel.sous-sol.org> (raw)
In-Reply-To: <20060115120252.GA13135@mipter.zuzino.mipt.ru>

* Alexey Dobriyan (adobriyan@gmail.com) wrote:
> From: Evgeniy <dushistov@mail.ru>
> 
> There's a lack of parenthesis in fs/ufs/utils.h, so instead of the 512th
> byte of buffer, the usb2 pointer will point to the nth structure of type
> ufs_super_block_second.

Thanks Alexey, this one's already queued for the next -stable.
-chris

      reply	other threads:[~2006-01-15 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 12:02 [STABLE] Fix oops in ufs_fill_super at mount time Alexey Dobriyan
2006-01-15 18:11 ` Chris Wright [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=20060115181117.GM3335@sorel.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=adobriyan@gmail.com \
    --cc=dushistov@mail.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).