From: Dave Chinner <david@fromorbit.com>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: BUG: KASAN: use-after-free in xfs_iflush_cluster+0x9d7/0xaf0
Date: Wed, 6 Jan 2016 07:58:11 +1100 [thread overview]
Message-ID: <20160105205811.GA21461@dastard> (raw)
In-Reply-To: <20160105163055.GA18111@glen>
On Tue, Jan 05, 2016 at 05:30:55PM +0100, Andrea Gelmini wrote:
> On Mon, Jan 04, 2016 at 07:47:58AM +1100, Dave Chinner wrote:
> > > I'm recompiling, to try it again.
> > > Maybe, in the meanwhile, you can do something with my files. You can find 'em here:
> > > http://mail.gelma.net/xfs_kasan
> >
> > Any update on this problem, Andrea?
>
> Here we are!
> Reproduced right now.
>
> So, just to avoid confusion:
> a) it's a vanilla kernel 4.4.0-rc8
> b) plus some btrfs patches
> c) plus some dri/intel/i915 patches
> d) at the same URL above you can find git_files.txt.gz, where you have each commit I
> applied above vanilla kernel (anyway, nothing related to vfs/xfs of course)
> e) at the same URL you find the kernel binaries I used
> f) to catch it, I had to copy a few gigs of files on my /home partition (xfs over Luks)
>
> Anyway, here what you asked me for:
>
> (gdb) l *(xfs_iflush_cluster+0xb73/0xc10)
> 0xffffffff8184c550 is in xfs_iflush_cluster (fs/xfs/xfs_inode.c:3182).
> 3177
> 3178 STATIC int
> 3179 xfs_iflush_cluster(
> 3180 xfs_inode_t *ip,
> 3181 xfs_buf_t *bp)
> 3182 {
> 3183 xfs_mount_t *mp = ip->i_mount;
> 3184 struct xfs_perag *pag;
> 3185 unsigned long first_index, mask;
> 3186 unsigned long inodes_per_cluster;
> (gdb)
Ok, so that tells us nothing about where the problem lies - the
function call is out of the preamble code that kasan instrumentation
adds to the function. I'll have a further think about this...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Andrea Gelmini <andrea.gelmini@gelma.net>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: BUG: KASAN: use-after-free in xfs_iflush_cluster+0x9d7/0xaf0
Date: Wed, 6 Jan 2016 07:58:11 +1100 [thread overview]
Message-ID: <20160105205811.GA21461@dastard> (raw)
In-Reply-To: <20160105163055.GA18111@glen>
On Tue, Jan 05, 2016 at 05:30:55PM +0100, Andrea Gelmini wrote:
> On Mon, Jan 04, 2016 at 07:47:58AM +1100, Dave Chinner wrote:
> > > I'm recompiling, to try it again.
> > > Maybe, in the meanwhile, you can do something with my files. You can find 'em here:
> > > http://mail.gelma.net/xfs_kasan
> >
> > Any update on this problem, Andrea?
>
> Here we are!
> Reproduced right now.
>
> So, just to avoid confusion:
> a) it's a vanilla kernel 4.4.0-rc8
> b) plus some btrfs patches
> c) plus some dri/intel/i915 patches
> d) at the same URL above you can find git_files.txt.gz, where you have each commit I
> applied above vanilla kernel (anyway, nothing related to vfs/xfs of course)
> e) at the same URL you find the kernel binaries I used
> f) to catch it, I had to copy a few gigs of files on my /home partition (xfs over Luks)
>
> Anyway, here what you asked me for:
>
> (gdb) l *(xfs_iflush_cluster+0xb73/0xc10)
> 0xffffffff8184c550 is in xfs_iflush_cluster (fs/xfs/xfs_inode.c:3182).
> 3177
> 3178 STATIC int
> 3179 xfs_iflush_cluster(
> 3180 xfs_inode_t *ip,
> 3181 xfs_buf_t *bp)
> 3182 {
> 3183 xfs_mount_t *mp = ip->i_mount;
> 3184 struct xfs_perag *pag;
> 3185 unsigned long first_index, mask;
> 3186 unsigned long inodes_per_cluster;
> (gdb)
Ok, so that tells us nothing about where the problem lies - the
function call is out of the preamble code that kasan instrumentation
adds to the function. I'll have a further think about this...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-01-05 20:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 18:00 BUG: KASAN: use-after-free in xfs_iflush_cluster+0x9d7/0xaf0 Andrea Gelmini
2015-12-14 18:00 ` Andrea Gelmini
2015-12-14 19:54 ` Dave Chinner
2015-12-14 19:54 ` Dave Chinner
2015-12-14 20:15 ` Andrea Gelmini
2015-12-14 20:15 ` Andrea Gelmini
2015-12-14 21:22 ` Dave Chinner
2015-12-14 21:22 ` Dave Chinner
2015-12-15 9:11 ` Andrea Gelmini
2015-12-15 9:11 ` Andrea Gelmini
2016-01-03 20:47 ` Dave Chinner
2016-01-03 20:47 ` Dave Chinner
2016-01-04 14:12 ` Andrea Gelmini
2016-01-04 14:12 ` Andrea Gelmini
2016-01-05 16:30 ` Andrea Gelmini
2016-01-05 16:30 ` Andrea Gelmini
2016-01-05 20:58 ` Dave Chinner [this message]
2016-01-05 20:58 ` 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=20160105205811.GA21461@dastard \
--to=david@fromorbit.com \
--cc=andrea.gelmini@gelma.net \
--cc=linux-kernel@vger.kernel.org \
--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 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.