From: Kalle Valo <kvalo@codeaurora.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
Christian Lamparter <chunkeey@gmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
b43-dev@lists.infradead.org, Nicolai Stange <nicstange@gmail.com>,
Ben Greear <greearb@candelatech.com>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: [PATCH 2/4] carl9170: fix debugfs crashes
Date: Sun, 18 Sep 2016 10:54:18 +0300 [thread overview]
Message-ID: <87d1k17idx.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160917214539.GA28379@kroah.com> (Greg KH's message of "Sat, 17 Sep 2016 23:45:39 +0200")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Sat, Sep 17, 2016 at 09:43:02PM +0200, Christian Lamparter wrote:
>> Ben Greear reported:
>> > I see lots of instability as soon as I load up the carl9710 NIC.
>> > My application is going to be poking at it's debugfs files...
>> >
>> > BUG: KASAN: slab-out-of-bounds in carl9170_debugfs_read+0xd5/0x2a0
>> > [carl9170] at addr ffff8801bc1208b0
>> > Read of size 8 by task btserver/5888
>> > =======================================================================
>> > BUG kmalloc-256 (Tainted: G W ): kasan: bad access detected
>> > -----------------------------------------------------------------------
>> >
>> > INFO: Allocated in seq_open+0x50/0x100 age=2690 cpu=2 pid=772
>> >...
>>
>> This breakage was caused by the introduction of intermediate
>> fops in debugfs by commit 9fd4dcece43a
>> ("debugfs: prevent access to possibly dead file_operations at file open")
>
> Because of this, these should all be backported to 4.7-stable, and
> 4.8-stable, right?
Via which tree should these go, Greg's or mine?
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
Christian Lamparter <chunkeey@gmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
b43-dev@lists.infradead.org, Nicolai Stange <nicstange@gmail.com>,
Ben Greear <greearb@candelatech.com>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH 2/4] carl9170: fix debugfs crashes
Date: Sun, 18 Sep 2016 10:54:18 +0300 [thread overview]
Message-ID: <87d1k17idx.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160917214539.GA28379@kroah.com> (Greg KH's message of "Sat, 17 Sep 2016 23:45:39 +0200")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Sat, Sep 17, 2016 at 09:43:02PM +0200, Christian Lamparter wrote:
>> Ben Greear reported:
>> > I see lots of instability as soon as I load up the carl9710 NIC.
>> > My application is going to be poking at it's debugfs files...
>> >
>> > BUG: KASAN: slab-out-of-bounds in carl9170_debugfs_read+0xd5/0x2a0
>> > [carl9170] at addr ffff8801bc1208b0
>> > Read of size 8 by task btserver/5888
>> > =======================================================================
>> > BUG kmalloc-256 (Tainted: G W ): kasan: bad access detected
>> > -----------------------------------------------------------------------
>> >
>> > INFO: Allocated in seq_open+0x50/0x100 age=2690 cpu=2 pid=772
>> >...
>>
>> This breakage was caused by the introduction of intermediate
>> fops in debugfs by commit 9fd4dcece43a
>> ("debugfs: prevent access to possibly dead file_operations at file open")
>
> Because of this, these should all be backported to 4.7-stable, and
> 4.8-stable, right?
Via which tree should these go, Greg's or mine?
--
Kalle Valo
next prev parent reply other threads:[~2016-09-18 7:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 19:43 [PATCH 1/4] debugfs: introduce a public file_operations accessor Christian Lamparter
2016-09-17 19:43 ` [PATCH 2/4] carl9170: fix debugfs crashes Christian Lamparter
2016-09-17 21:45 ` Greg KH
2016-09-17 21:45 ` Greg KH
2016-09-18 7:54 ` Kalle Valo [this message]
2016-09-18 7:54 ` Kalle Valo
2016-09-18 10:14 ` Greg KH
2016-09-18 10:14 ` Greg KH
2016-09-18 12:49 ` Christian Lamparter
2016-09-18 12:49 ` Christian Lamparter
2016-09-18 16:44 ` Greg KH
2016-09-18 16:44 ` Greg KH
2016-09-19 20:12 ` Christian Lamparter
2016-09-19 20:12 ` Christian Lamparter
2016-09-20 6:50 ` Greg KH
2016-09-20 6:50 ` Greg KH
2016-09-18 16:57 ` Kalle Valo
2016-09-18 16:57 ` Kalle Valo
2016-09-21 10:13 ` Greg KH
2016-09-21 10:13 ` Greg KH
2016-09-21 16:29 ` Christian Lamparter
2016-09-21 16:29 ` Christian Lamparter
2016-09-21 16:49 ` [PATCH v2] " Christian Lamparter
2016-09-17 19:43 ` [PATCH 3/4] b43: fix debugfs crash Christian Lamparter
2016-09-17 19:43 ` Christian Lamparter
2016-09-17 19:43 ` [PATCH 4/4] b43legacy: " Christian Lamparter
2016-09-17 19:43 ` Christian Lamparter
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=87d1k17idx.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=chunkeey@gmail.com \
--cc=chunkeey@googlemail.com \
--cc=greearb@candelatech.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nicstange@gmail.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.