From: Eric Sandeen <sandeen@sandeen.net>
To: aelder@sgi.com
Cc: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>,
Dan Rosenberg <drosenberg@vsecurity.com>,
Eugene Teo <eugeneteo@kernel.org>,
xfs@oss.sgi.com
Subject: Re: [PATCH, V3 (sort of)] xfs: zero proper structure size for geometry calls
Date: Tue, 01 Mar 2011 12:18:57 -0600 [thread overview]
Message-ID: <4D6D3891.5060908@sandeen.net> (raw)
In-Reply-To: <1299001800.2381.10.camel@doink>
On 3/1/11 11:50 AM, Alex Elder wrote:
> I'm sorry to muddy the waters with this. But I think the
> proposed patch fixes the wrong problem. Having xfs_fs_geometry()
> zero its argument is fine--it defines an interface and honors
> it. The real problem lies in xfs_ioc_fsgeometry_v1(), which
> violates that interface by passing the address of an object
> that's not the right size. So below is an alternative to
> Eric's solution which just fixes this one caller instead.
>
> Eric has already told me this makes more sense. It would
> be nice if Jeffrey would re-test this fix, and Dan would
> sign off on it as well.
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
thanks,
-Eric
> -Alex
>
> Commit 493f3358cb289ccf716c5a14fa5bb52ab75943e5 added this call to
> xfs_fs_geometry() in order to avoid passing kernel stack data back
> to user space:
>
> + memset(geo, 0, sizeof(*geo));
>
> Unfortunately, one of the callers of that function passes the
> address of a smaller data type, cast to fit the type that
> xfs_fs_geometry() requires. As a result, this can happen:
>
> Kernel panic - not syncing: stack-protector: Kernel stack is corrupted
> in: f87aca93
>
> Pid: 262, comm: xfs_fsr Not tainted 2.6.38-rc6-493f3358cb2+ #1
> Call Trace:
>
> [<c12991ac>] ? panic+0x50/0x150
> [<c102ed71>] ? __stack_chk_fail+0x10/0x18
> [<f87aca93>] ? xfs_ioc_fsgeometry_v1+0x56/0x5d [xfs]
>
>
> Fix this by fixing that one caller to pass the right type and then
> copy out the subset it is interested in.
>
> Note: This patch is an alternative to one originally proposed by
> Eric Sandeen.
>
> Reported-by: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
> Signed-off-by: Alex Elder <aelder@sgi.com>
>
> ---
> fs/xfs/linux-2.6/xfs_ioctl.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> Index: b/fs/xfs/linux-2.6/xfs_ioctl.c
> ===================================================================
> --- a/fs/xfs/linux-2.6/xfs_ioctl.c
> +++ b/fs/xfs/linux-2.6/xfs_ioctl.c
> @@ -695,14 +695,19 @@ xfs_ioc_fsgeometry_v1(
> xfs_mount_t *mp,
> void __user *arg)
> {
> - xfs_fsop_geom_v1_t fsgeo;
> + xfs_fsop_geom_t fsgeo;
> int error;
>
> - error = xfs_fs_geometry(mp, (xfs_fsop_geom_t *)&fsgeo, 3);
> + error = xfs_fs_geometry(mp, &fsgeo, 3);
> if (error)
> return -error;
>
> - if (copy_to_user(arg, &fsgeo, sizeof(fsgeo)))
> + /*
> + * Caller should have passed an argument of type
> + * xfs_fsop_geom_v1_t. This is a proper subset of the
> + * xfs_fsop_geom_t that xfs_fs_geometry() fills in.
> + */
> + if (copy_to_user(arg, &fsgeo, sizeof (xfs_fsop_geom_v1_t)))
> return -XFS_ERROR(EFAULT);
> return 0;
> }
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-03-01 18:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 22:58 kernel panic - stack-protector: kernel stack is corrupted in: f87aca93 Jeffrey Hundstad
2011-03-01 0:00 ` Eric Sandeen
2011-03-01 1:03 ` Jeffrey Hundstad
2011-03-01 1:32 ` Eric Sandeen
2011-03-01 2:57 ` Dave Chinner
2011-03-01 1:37 ` [PATCH] xfs: zero proper structure size for geometry calls Eric Sandeen
2011-03-01 2:59 ` Dave Chinner
2011-03-01 3:01 ` Eric Sandeen
2011-03-01 6:59 ` [PATCH V2] " Eric Sandeen
2011-03-01 12:55 ` Dan Rosenberg
2011-03-01 15:36 ` Jeffrey Hundstad
2011-03-01 15:49 ` Eric Sandeen
2011-03-01 17:50 ` [PATCH, V3 (sort of)] " Alex Elder
2011-03-01 18:18 ` Eric Sandeen [this message]
2011-03-01 21:40 ` Jeffrey Hundstad
2011-03-02 0:02 ` Dave Chinner
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=4D6D3891.5060908@sandeen.net \
--to=sandeen@sandeen.net \
--cc=aelder@sgi.com \
--cc=drosenberg@vsecurity.com \
--cc=eugeneteo@kernel.org \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=xfs@oss.sgi.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