From: Kalle Valo <kvalo@codeaurora.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, Theodore Ts'o <tytso@mit.edu>,
Jan Kara <jack@suse.cz>, Eric Biggers <ebiggers@google.com>,
Andreas Dilger <adilger@dilger.ca>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: Regression in next with ext4 oops
Date: Wed, 05 Oct 2016 12:51:52 +0300 [thread overview]
Message-ID: <8737kbp1hj.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20161004203404.cxx767awxo7ti4v7@atomide.com> (Tony Lindgren's message of "Tue, 4 Oct 2016 13:34:04 -0700")
Tony Lindgren <tony@atomide.com> writes:
> * Kalle Valo <kvalo@codeaurora.org> [161004 12:42]:
>> Tony Lindgren <tony@atomide.com> writes:
>>
>> > And the patch below seems to fix the issue as the driver is now
>> > using devm_kzalloc. Will do some more testing and then will post
>> > a proper patch. The same issue might be there for SPI glue also.
>>
>> This was already posted and you even acked it :)
>>
>> wlcore: sdio: drop kfree for memory allocated with devm_kzalloc
>>
>> https://patchwork.kernel.org/patch/9353985/
>
> Heh well now we know :) Can you please apply it as it fixes a memory
> corruption issue?
Yeah, I'll apply it to wireless-drivers.git soon.
> The SPI glue does not have this same issue.
Good to know, thanks for checking.
--
Kalle Valo
next prev parent reply other threads:[~2016-10-05 9:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 23:30 Regression in next with ext4 oops Tony Lindgren
2016-10-04 9:00 ` Jan Kara
2016-10-04 14:02 ` Theodore Ts'o
2016-10-04 14:44 ` Tony Lindgren
2016-10-04 14:59 ` Al Viro
2016-10-04 19:07 ` Theodore Ts'o
2016-10-04 19:19 ` Tony Lindgren
2016-10-04 19:16 ` Tony Lindgren
2016-10-04 19:29 ` Tony Lindgren
2016-10-04 19:41 ` Kalle Valo
2016-10-04 20:34 ` Tony Lindgren
2016-10-05 9:51 ` Kalle Valo [this message]
2016-10-04 14:18 ` Tony Lindgren
2016-10-04 14:56 ` Al Viro
2016-10-05 5:44 ` Jan Kara
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=8737kbp1hj.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=adilger@dilger.ca \
--cc=ebiggers@google.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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