[GIT,PULL] Smack patches for v5.4
mbox series

Message ID d2418da0-056b-2e6f-ae40-acdfa842e341@schaufler-ca.com
State New
Headers show
Series
  • [GIT,PULL] Smack patches for v5.4
Related show

Pull-request

https://github.com/cschaufler/smack-next.git smack-for-5.4

Message

Casey Schaufler Sept. 23, 2019, 5:24 p.m. UTC
Hello Linus

I have four patches for v5.4. Nothing is major. All but one are in
response to mechanically detected potential issues. The remaining
patch cleans up kernel-doc notations.

This is my first direct pull request. I think I have followed process
correctly, but if not I will attend to my error as required.

The following changes since commit 0ecfebd2b52404ae0c54a878c872bb93363ada36:

  Linux 5.2 (2019-07-07 15:41:56 -0700)

are available in the Git repository at:

  https://github.com/cschaufler/smack-next.git smack-for-5.4

for you to fetch changes up to e5bfad3d7acc5702f32aafeb388362994f4d7bd0:

  smack: use GFP_NOFS while holding inode_smack::smk_lock (2019-09-04 09:37:07 -0700)

----------------------------------------------------------------
Eric Biggers (1):
      smack: use GFP_NOFS while holding inode_smack::smk_lock

Jann Horn (1):
      Smack: Don't ignore other bprm->unsafe flags if LSM_UNSAFE_PTRACE is set

Jia-Ju Bai (1):
      security: smack: Fix possible null-pointer dereferences in smack_socket_sock_rcv_skb()

luanshi (1):
      smack: fix some kernel-doc notations

 security/smack/smack_access.c |  6 +++---
 security/smack/smack_lsm.c    | 40 ++++++++++++++++++++--------------------
 2 files changed, 23 insertions(+), 23 deletions(-)

Comments

Linus Torvalds Sept. 23, 2019, 7:17 p.m. UTC | #1
On Mon, Sep 23, 2019 at 10:24 AM Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> This is my first direct pull request. I think I have followed process
> correctly, but if not I will attend to my error as required.

The contents look fine.

However, it's from an open hosting site - github. Which is fine, I
take pull requests from github all the time.  But I require that they
be sent using a signed tag, so that I can verify that yes, it's really
from you.

And no, I don't do pgp email, even t hough I see that there's a
signature on your email itself.

git uses pgp too, but unlike pgp email signatures, the git support for
pgp signing is useful and user-friendly and just _works_, rather than
the complete and useless disaster that is pgp email [1].

So please make it a signed tag with "git tag -s" and ask me to pull
that tag instead.

                        Linus

[1] https://www.vice.com/en_us/article/vvbw9a/even-the-inventor-of-pgp-doesnt-use-pgp
pr-tracker-bot@kernel.org Sept. 24, 2019, 1:25 a.m. UTC | #2
The pull request you sent on Mon, 23 Sep 2019 10:24:21 -0700:

> https://github.com/cschaufler/smack-next.git smack-for-5.4

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e94f8ccde4710f9a3e51dd3bc6134c96e33f29b3

Thank you!