When tls data skb is pending for Tx and tls alert comes , It
is wrongly overwrite the record type of tls data to tls alert
record type. fix the issue correcting it.
v1->v2:
- Correct submission tree.
- Add fixes tag.
Fixes: 6919a8264a32 ("Crypto/chtls: add/delete TLS header in driver&
When tls data skb is pending for Tx and tls alert comes , It
is wrongly overwrite the record type of tls data to tls alert
record type. fix the issue correcting it.
Signed-off-by: Vinay Kumar Yadav
---
drivers/crypto/chelsio/chtls/chtls_io.c | 7 ---
1 file changed, 4 insertions(+), 3
From: Ido Schimmel
In a similar fashion to software drops, extend drop monitor to send
netlink events when packets are dropped by the underlying hardware.
The main difference is that instead of encoding the program counter (PC)
from which kfree_skb() was called in the netlink message, we encode
From: Ido Schimmel
In summary alert mode a notification is sent with a list of recent drop
reasons and a count of how many packets were dropped due to this reason.
To avoid expensive operations in the context in which packets are
dropped, each CPU holds an array whose number of entries is the
From: Ido Schimmel
In a similar fashion to software drops, extend drop monitor to send
netlink events when packets are dropped by the underlying hardware.
The main difference is that instead of encoding the program counter (PC)
from which kfree_skb() was called in the netlink message, we encode
From: Ido Schimmel
In summary alert mode a notification is sent with a list of recent drop
reasons and a count of how many packets were dropped due to this reason.
To avoid expensive operations in the context in which packets are
dropped, each CPU holds an array whose number of entries is the
From: Ido Schimmel
So far drop monitor supported only one alert mode in which a summary of
locations in which packets were recently dropped was sent to user space.
This alert mode is sufficient in order to understand that packets were
dropped, but lacks information to perform a more detailed
From: Ido Schimmel
The next patch is going to add another alert mode in which the dropped
packet is notified to user space, instead of only a summary of recent
drops.
Abstract the differences between the modes by adding alert mode
operations. The operations are selected based on the currently
From: Ido Schimmel
So far drop monitor supported only one alert mode in which a summary of
locations in which packets were recently dropped was sent to user space.
This alert mode is sufficient in order to understand that packets were
dropped, but lacks information to perform a more detailed
From: Ido Schimmel
The next patch is going to add another alert mode in which the dropped
packet is notified to user space, instead of only a summary of recent
drops.
Abstract the differences between the modes by adding alert mode
operations. The operations are selected based on the currently
gt;+{
> >+struct netlink_ext_ack *extack = info->extack;
> >+enum net_dm_alert_mode alert_mode;
> >+int rc;
> >+
> >+if (!info->attrs[NET_DM_ATTR_ALERT_MODE])
> >+return 0;
> >+
> >+rc = net_dm_alert_mode_g
Mon, Jul 22, 2019 at 08:31:32PM CEST, ido...@idosch.org wrote:
>From: Ido Schimmel
>
>So far drop monitor supported only one alert mode in which a summary of
>locations in which packets were recently dropped was sent to user space.
>
>This alert mode is sufficient in order
On Tue, Jul 23, 2019 at 11:14:31AM -0400, Neil Horman wrote:
> On Tue, Jul 23, 2019 at 05:16:25PM +0300, Ido Schimmel wrote:
> > On Tue, Jul 23, 2019 at 08:43:40AM -0400, Neil Horman wrote:
> > > On Mon, Jul 22, 2019 at 09:31:32PM +0300, Ido Schimmel wrote:
> > > > +static void net_dm_packet_work(s
On Tue, Jul 23, 2019 at 05:16:25PM +0300, Ido Schimmel wrote:
> On Tue, Jul 23, 2019 at 08:43:40AM -0400, Neil Horman wrote:
> > On Mon, Jul 22, 2019 at 09:31:32PM +0300, Ido Schimmel wrote:
> > > +static void net_dm_packet_work(struct work_struct *work)
> > > +{
> > > + struct per_cpu_dm_data *dat
On Tue, Jul 23, 2019 at 08:43:40AM -0400, Neil Horman wrote:
> On Mon, Jul 22, 2019 at 09:31:32PM +0300, Ido Schimmel wrote:
> > +static void net_dm_packet_work(struct work_struct *work)
> > +{
> > + struct per_cpu_dm_data *data;
> > + struct sk_buff_head list;
> > + struct sk_buff *skb;
> >
On Mon, Jul 22, 2019 at 09:31:32PM +0300, Ido Schimmel wrote:
> From: Ido Schimmel
>
> So far drop monitor supported only one alert mode in which a summary of
> locations in which packets were recently dropped was sent to user space.
>
> This alert mode is sufficient in order
From: Ido Schimmel
So far drop monitor supported only one alert mode in which a summary of
locations in which packets were recently dropped was sent to user space.
This alert mode is sufficient in order to understand that packets were
dropped, but lacks information to perform a more detailed
From: Matt Turner
I personally spent a long time trying to decypher why my CPU would not
reach deeper C-states. Let's just tell the next user what's going on.
Signed-off-by: Matt Turner
Acked-by: Shannon Nelson
Tested-by: Aaron Brown
Signed-off-by: Jeff Kirsher
---
drivers/net/ethernet/inte
MICROSOFT WARNING MESSAGE ALERT
Lots of your messages are currently suspended because your E-mail box account
needs to be verify<https://info253027.wixsite.com/info11> now. Do verify now
inother to receive your pending messages without no delay.
©2018 Microsoft Outlook Inc.
Recently, we have detect some unusual activity on your account and as a result,
all email users are urged to update their email account within 24 hours of
receiving this e-mail, please click the link http://beam.to/5617 to confirm
that your email account is up to date with the institution requir
From: Ido Schimmel
In case local sockets have the IP_ROUTER_ALERT socket option set, then
they expect to get packets with the Router Alert option.
Trap such packets, so that the kernel could inspect them and potentially
send them to interested sockets.
Signed-off-by: Ido Schimmel
Signed-off
Please be advised that we will be performing a scheduled email maintenance
within the next 24hrs, during this maintenance you will be require to
update your email account via link http://www.beam.to/9687
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.co
Please be advised that we will be performing a scheduled email maintenance
within the next 24hrs, during this maintenance you will be require to
update your email account via link http://www.beam.to/9687
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.co
Recently, we have detect some unusual activity on your account and as a result,
all email users are urged to update their email account within 24 hours of
receiving this e-mail, please click the link http://beam.to/1469 to confirm
that your email account is up to date with the institution requir
Dear Webmail User,
Due to excess abandoned Webmail Account, Our Webmaster has decided to
refresh the database and to delete inactive accounts to create space
for fresh users. To verify your Webmail Account, you must reply to
this email immediately and provide the information below correctly:
Emai
Recently, we have detect some unusual activity on your account and as a
result, all email users are urged to update their email account within 24 hours
of receiving this e-mail, Please CLICK to confirm that your email account is
up to date with the institution requirement.
---
This email has be
ease?
Having looked a bit further, it appears that the sk_bound_dev_if check
isn't being performed in the general IPv6 raw socket reception case
either. (See __raw_v6_lookup() vs __raw_v4_lookup().)
TCP/UDP sockets look like they take care of interface binding
correctly.
I'll try
In article <[EMAIL PROTECTED]> (at Thu, 21 Jul 2005 21:44:43 +0100), Andrew
McDonald <[EMAIL PROTECTED]> says:
> I guess the fix would be a matter of changing:
>
> if (sk && ra->sel == sel) {
>
> to:
>
> if (sk && ra->sel == sel &&
> (!sk->sk_bound_dev_if ||
> sk->sk_bound_dev_if == s
Hi,
I've noticed a difference between the IPv4 and IPv6 router alert
handling, which I think constitutes a bug.
For IPv4, you can bind a socket to an interface. If you use the
IP_ROUTER_ALERT sockopt then packets with router alert options are only
delivered to raw sockets bound to the inc
29 matches
Mail list logo
