Message ID | ab8e6cbb-c46d-41bd-0a0d-43530ee37386@canonical.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [GIT,PULL] apparmor updates for 5.5 | expand |
On Tue, Dec 3, 2019 at 12:33 PM John Johansen <john.johansen@canonical.com> wrote: > > + Bug fixes > - fix sparse warning for type-casting of current->real_cred That fix is wrong. Yes, it removes the warning. It's still wrong. The proper way to remove the warning is to use the proper accessor to read the current real_cred. And that will point out that the cred needs to be 'const'. IOW, it should do const struct cred *cred = current_real_cred(); instead. I have done the pull without doing that change, but this is a REALLY IMPORTANT issue! Don't just "fix warnings". The warnings had a reason, you need to _think_ about them. This is doubly true in code that claims to be about "security". Seriously. apparmor can't just be a "let's do random things and hope for the best". Linus
The pull request you sent on Tue, 3 Dec 2019 12:33:43 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor tags/apparmor-pr-2019-12-03
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/79e178a57dae819ae724065b47c25720494cc9f2
Thank you!