All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shreenidhi Shedi <yesshedi@gmail.com>
To: Paul Moore <paul@paul-moore.com>
Cc: eparis@redhat.com, linux-kernel@vger.kernel.org,
	linux-audit@redhat.com, Shreenidhi Shedi <sshedi@vmware.com>
Subject: Re: [PATCH 1/2] audit: remove redundant data_len check
Date: Wed, 8 Jun 2022 14:13:21 +0530	[thread overview]
Message-ID: <61db56c0-af8f-6e8f-a4c4-c561f18bd6ac@gmail.com> (raw)
In-Reply-To: <CAHC9VhTpBAeEm6U6-=YW7e0JV-WS3MeOjT4g9S-V4ZM2OboBAw@mail.gmail.com>

On 08/06/22 1:31 am, Paul Moore wrote:
> On Sun, May 15, 2022 at 7:35 PM Paul Moore <paul@paul-moore.com> wrote:
>>
>> On Sun, May 15, 2022 at 3:31 AM Shreenidhi Shedi <yesshedi@gmail.com> wrote:
>>>
>>> data_len is already getting checked if it's less than 2 earlier in this
>>> function.
>>>
>>> Signed-off-by: Shreenidhi Shedi <sshedi@vmware.com>
>>> ---
>>>  kernel/audit.c | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> Thanks, this patch looks okay, but since we are already at v5.18-rc7
>> this patch will have to wait until after the upcoming merge window as
>> it isn't a critical bug fix.
> 
> ... and it's now merged into audit/next, thanks!
> 

You are welcome and Thank you as well.

-- 
Shedi

WARNING: multiple messages have this Message-ID (diff)
From: Shreenidhi Shedi <yesshedi@gmail.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Shreenidhi Shedi <sshedi@vmware.com>,
	linux-audit@redhat.com, linux-kernel@vger.kernel.org,
	eparis@redhat.com
Subject: Re: [PATCH 1/2] audit: remove redundant data_len check
Date: Wed, 8 Jun 2022 14:13:21 +0530	[thread overview]
Message-ID: <61db56c0-af8f-6e8f-a4c4-c561f18bd6ac@gmail.com> (raw)
In-Reply-To: <CAHC9VhTpBAeEm6U6-=YW7e0JV-WS3MeOjT4g9S-V4ZM2OboBAw@mail.gmail.com>

On 08/06/22 1:31 am, Paul Moore wrote:
> On Sun, May 15, 2022 at 7:35 PM Paul Moore <paul@paul-moore.com> wrote:
>>
>> On Sun, May 15, 2022 at 3:31 AM Shreenidhi Shedi <yesshedi@gmail.com> wrote:
>>>
>>> data_len is already getting checked if it's less than 2 earlier in this
>>> function.
>>>
>>> Signed-off-by: Shreenidhi Shedi <sshedi@vmware.com>
>>> ---
>>>  kernel/audit.c | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> Thanks, this patch looks okay, but since we are already at v5.18-rc7
>> this patch will have to wait until after the upcoming merge window as
>> it isn't a critical bug fix.
> 
> ... and it's now merged into audit/next, thanks!
> 

You are welcome and Thank you as well.

-- 
Shedi

--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit


  reply	other threads:[~2022-06-08  9:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15  7:31 [PATCH 1/2] audit: remove redundant data_len check Shreenidhi Shedi
2022-05-15  7:31 ` Shreenidhi Shedi
2022-05-15  7:31 ` [PATCH 2/2] audit: fix most of the checkpatch.pl warnnings & errors Shreenidhi Shedi
2022-05-15  7:31   ` Shreenidhi Shedi
2022-05-15 23:44   ` Paul Moore
2022-05-15 23:44     ` Paul Moore
2022-05-15 23:35 ` [PATCH 1/2] audit: remove redundant data_len check Paul Moore
2022-05-15 23:35   ` Paul Moore
2022-06-07 20:01   ` Paul Moore
2022-06-07 20:01     ` Paul Moore
2022-06-08  8:43     ` Shreenidhi Shedi [this message]
2022-06-08  8:43       ` Shreenidhi Shedi

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=61db56c0-af8f-6e8f-a4c4-c561f18bd6ac@gmail.com \
    --to=yesshedi@gmail.com \
    --cc=eparis@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=sshedi@vmware.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.